# history Published articles for history. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot 10-year anniversary and history DevFeed: [Libreboot 10-year anniversary and history]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [Open Source](), [Operating system](), [Hardware](), [UEFI](), [x86](), [Linux](), [boot](), [releases]() Tags: [anniversary](), [article](), [bios](), [canoeboot](), [coreboot](), [cpu](), [firmware](), [free-software](), [hardware](), [history](), [libre](), [libreboot](), [open-source](), [opensource](), [uefi](), [x86]() ### AI overview This article marks Libreboot's 10-year anniversary and recounts the project's history from the author's perspective. It describes Libreboot as free, open-source boot firmware based on coreboot for selected Intel, AMD, x86, and ARM systems, and discusses its goals and development context. ### Source excerpt Article: Libreboot 10-year anniversary and history Web link: https://libreboot.org/news/10.html ## Firefox 156 Available With Its Built-In PDF Viewer Starting Up To 45% Faster DevFeed: [Firefox 156 Available With Its Built-In PDF Viewer Starting Up To 45% Faster]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-14T15:09:09Z Content type: news Language: en Sources: [Phoronix]() Topics: [Firefox](), [pdf](), [Mozilla](), [Linux](), [Nvidia]() Tags: [cpu](), [desktop-linux](), [firefox](), [history](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [memory](), [mozilla](), [nvidia](), [open-source-graphics](), [pdf](), [performance](), [phoronix](), [phoronix-test-suite](), [release](), [ubuntu-benchmarks](), [ubuntu-hardware](), [update](), [vulkan]() ### AI overview Firefox 156 is available with a built-in PDF viewer that starts up up to 45% faster. The release also improves memory and CPU usage when displaying large scaled-down JPEG images and includes several fixes. Vulkan Video decoding for newer NVIDIA GPUs remains limited to nightly builds. ### Source excerpt Mozilla today published their Firefox 156.0 release binaries ahead of the official Tuesday announcement... ## What algorithm did Windows XP use to choose your initial user picture? DevFeed: [What algorithm did Windows XP use to choose your initial user picture?]() Original publisher: [Read original article]() Author: Raymond Chen Published: 2026-09-09T14:00:00Z Content type: article Language: en Sources: [Raymond Chen]() Topics: [Algorithm](), [Randomizer](), [Windows](), [Filesystems]() Tags: [algorithm](), [files](), [history](), [old-new-thing](), [random](), [recursion](), [windows]() ### AI overview The article explains that Windows XP selected an initial user picture randomly from the Default Pictures directory using the current time as the random seed. It describes a one-pass reservoir-sampling algorithm, including its efficiency and behavior when files change during selection, with a 100-picture safety limit. ### Source excerpt It's random, really. The post What algorithm did Windows XP use to choose your initial user picture? appeared first on The Old New Thing. ## Java's age is its AI superpower DevFeed: [Java's age is its AI superpower]() Original publisher: [Read original article]() Author: Ryan Donovan Published: 2026-09-09T04:45:00Z Content type: opinion Language: en Sources: [Stack Overflow Blog]() Topics: [coding](), [Training AI Models]() Tags: [agent](), [agentic](), [ai](), [buiilding-software](), [coding](), [data](), [ecosystem](), [history](), [ibm](), [java](), [podcast](), [se-stackoverflow](), [se-tech](), [sponsored](), [training]() ### AI overview A podcast episode argues that Java's longevity, training-data footprint, libraries, and agentic tooling make it a strong fit for coding agents. ### Source excerpt Ryan welcomes Markus Eisele to the program to talk about why your coding agent should be writing Java. ## Fragments: September 8 DevFeed: [Fragments: September 8]() Original publisher: [Read original article]() Author: Martin Fowler (martin@martinfowler.com) Published: 2026-09-08T15:22:00Z Content type: article Language: en Sources: [Martin Fowler]() Topics: [Artificial Intelligence](), [Automation](), [hugging face](), [OpenAI](), [dashboards](), [incident](), [Code]() Tags: [ai](), [ai-agents](), [ai-automation](), [article](), [automation](), [cost](), [dashboards](), [errors](), [history](), [how-to](), [hugging-face](), [incident](), [math](), [openai](), [verification]() ### AI overview The article discusses how AI reduces the cost of generating outputs more rapidly than the cost of verifying them. It argues that AI automation should be applied cautiously when effectiveness is difficult to measure, because incomplete metrics can produce short-term gains while creating hidden technical debt, correlated errors, and weakened human capability. It emphasizes preserving a history of decisions and judgment, and uses the OpenAI-Hugging Face incident to illustrate the consequences of optimizing agent capability without scoring relevant safety outcomes. ### Source excerpt Christian Catalini says we're in a situation where we are vastly reducing the cost of generating things, but not the cost of verifying them:. This explains why the first major AI products appeared in chat, image generation, and code assistance. Not because these were the hardest human problems, but because their outputs were relatively easy to inspect. A user can judge the tone of a message, look at an image, or run a test on a piece of code. [...] The old automation boundary was routine versus non-routine work. The new boundary is increasingly measurable versus non-measurable work. The issue is then over how well you can measure something. In our profession, we know there's a big difference between how many lines of code we write and how productive we are, and we've seen a regular failure to understand how to measure productivity. Too much of what makes work effective is subject to either slow feedback loops or assessments that require subtle judgment. The danger is that people use lots AI automation while using incomplete measurements of its effectiveness, leading to short-term dashboards going up, but disaster in longer time-scales. He refers to these illusory short-term gains as counterfeit utility. Scale this across companies and institutions and the result is a Hollow Economy: extraordinary measured activity sitting on top of weakening human capability, hidden technical debt, correlated errors, and outcomes that nobody can confidently stand behind. Another highlight in the article was his advice to "build a history of decisions, not a gallery of outputs". The point is that with AI we can all build really impressive things, but our value lies in the judgment that we've formed. It reminds me of how math problems were marked at school. We weren't just marked on getting the final answer, we were also marked based on our reasoning process. He uses the OpenAI-Hugging Face incident as an illustration of this gap between generation and verification. He criticizes those ## A sample use of the winstart.bat file in Windows 95 DevFeed: [A sample use of the winstart.bat file in Windows 95]() Original publisher: [Read original article]() Author: Raymond Chen Published: 2026-09-08T14:00:00Z Content type: article Language: en Sources: [Raymond Chen]() Topics: [Windows](), [Batch file]() Tags: [architecture](), [display](), [driver](), [drivers](), [graphics](), [history](), [multitasking](), [old-new-thing](), [post](), [windows]() ### AI overview The article explains a sample use of winstart.bat in Windows 95: starting the TIGA Communications Driver so 16-bit Windows can use high-resolution graphics modes. It notes that MS-DOS programs could not use TIGA modes and that multitasking TIGA graphics across Windows and MS-DOS sessions was unsupported. ### Source excerpt For a driver that needs high resolution mode only in Windows. The post A sample use of the winstart.bat file in Windows 95 appeared first on The Old New Thing. ## Configure Bash History: HISTSIZE, Timestamps, Sync, and Search Shortcuts DevFeed: [Configure Bash History: HISTSIZE, Timestamps, Sync, and Search Shortcuts]() Original publisher: [Read original article]() Author: Hayden James Published: 2026-09-03T18:31:24Z Content type: tutorial Language: en Sources: [Hayden James]() Topics: [Bash](), [Scripting, bash](), [Command-line interface]() Tags: [bash](), [blog](), [command-line](), [commands](), [history](), [how-to](), [linux](), [security](), [server](), [sysadmins]() ### AI overview A tutorial on configuring Bash command history, including history size, timestamps, synchronization across terminals, search shortcuts, and excluding commands from history. ### Source excerpt Bash history does a lot more than scroll up. Learn how to configure HISTSIZE, timestamps, multi-terminal sync, and search shortcuts to get real productivity gains at the command line. Continue reading... ## The Daily Heller: Paolo Garretto Was My Pen Pal, Reprised DevFeed: [The Daily Heller: Paolo Garretto Was My Pen Pal, Reprised]() Original publisher: [Read original article]() Author: Steven Heller Published: 2026-09-02T11:00:00Z Content type: article Language: en Sources: [PRINT Magazine]() Topics: [Simulation and Design]() Tags: [design](), [design-culture](), [history](), [illustration-design](), [print-homepage-rotation](), [the-daily-heller]() ### AI overview A personal recollection of correspondence with Italian caricaturist and designer Paolo Garretto, whose work portrayed prominent figures and reflected his distinctive art deco style. ### Source excerpt Revisiting one of Steven Heller's favorite stories about a legend of Italian design ... The post The Daily Heller: Paolo Garretto Was My Pen Pal, Reprised appeared first on PRINT Magazine. ## Four things you can build with Appwrite VectorsDB DevFeed: [Four things you can build with Appwrite VectorsDB]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-02T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [AI search](), [Databases]() Tags: [ai](), [cache](), [database](), [databases](), [embedding](), [history](), [search](), [vector-search]() ### AI overview This tutorial explains how Appwrite VectorsDB uses vector embeddings to find documents by meaning rather than exact keywords. It demonstrates help-article search, filtered search, recommendations from user history, and an answer cache, including a 256-number vector approach used in the examples. ### Source excerpt Appwrite VectorsDB finds documents by meaning, not by words. This post builds four features with it: a help article search, a filtered search, a recommendation from user history, and an answer cache. ## The good ol' days of building Java DevFeed: [The good ol' days of building Java]() Original publisher: [Read original article]() Published: 2026-09-01T07:40:00Z Content type: article Language: en Sources: [Stack Overflow Blog]() Topics: [Programming](), [cross-platform]() Tags: [building](), [cross-platform](), [history](), [java](), [podcast](), [se-stackoverflow](), [se-tech](), [windows](), [youtube]() ### AI overview An interview about the early development of Java, including its cross-platform ABI, competition with Windows NT, and the initial role of applets. ### Source excerpt Ryan sits down with Tim Lindholm, an early contributor to the Java language at Sun Microsystems, to chat about what it was like building one of the most popular programming languages ever at its inception, why it was strategically important for the Java team to create a cross-platform ABI to compete with Windows NT, and how applets were initially just an interesting demo. ## Before NTP there were Time and Daytime DevFeed: [Before NTP there were Time and Daytime]() Original publisher: [Read original article]() Author: jeff@jeffgeerling.com (Jeff Geerling) Published: 2026-08-30T22:09:00Z Content type: article Language: en Sources: [Jeff Geerling]() Topics: [networking](), [Protocol (disambiguation)](), [Unix]() Tags: [apple](), [bug](), [daytime](), [history](), [network](), [ntp](), [rfc-867](), [rfc-868](), [server](), [time]() ### AI overview The article examines the pre-NTP Time and Daytime protocols, RFC 868 and RFC 867, and explains how they provided simple network-based time retrieval. It describes the protocols' low overhead and limitations, including one-second resolution, lack of network-delay measurement, and the 2036 32-bit rollover bug. ### Source excerpt In building an NTP time demo on old Macs for VCF Midwest, I came across RFC 867 and RFC 868, for the 'Daytime' and 'Time' Protocols, respectively. My first exposure to any form of network time was when I upgraded from a used PowerBook 180c to my first 'new' computer, a Power Mac G3, in 2000. With the introduction of Mac OS 8.5, Apple added a 'Network Time Server' option in the Date & Time Control Panel. ## The lingering legacy of 'reserved' ports DevFeed: [The lingering legacy of 'reserved' ports]() Original publisher: [Read original article]() Author: George Michaelson Published: 2026-08-27T23:29:48Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Protocol (disambiguation)](), [Network](), [Process](), [Operating system](), [Unix](), [ssh](), [Firewall](), [Internet]() Tags: [dns](), [firewall](), [history](), [internet](), [network](), [ntp](), [opinion](), [process](), [processes](), [ssh](), [systems](), [tech-matters]() ### AI overview An exploration of why reserved TCP and UDP ports persist, tracing conventions such as ports 22, 53, 80, and 443 to early Internet services on multi-user systems. It explains the relationship between ports, protocol-specific daemons, operating-system administration, and modern firewall and service-discovery practices. ### Source excerpt Modern service discovery mechanisms increasingly allow services to run on arbitrary ports, yet DNS may remain the one protocol that cannot fully escape its dependency on the long-established convention of port 53. ## The history of Postgres sharding DevFeed: [The history of Postgres sharding]() Original publisher: [Read original article]() Author: Josh Brown Published: 2026-08-24T00:00:00Z Content type: article Language: en Sources: [Blog -- PlanetScale]() Topics: [Databases](), [Database](), [vitess](), [Tooling](), [LAMP]() Tags: [complexity](), [database](), [databases](), [engineering](), [history](), [mysql](), [neki](), [postgres](), [scale](), [servers](), [vitess]() ### AI overview The article traces the history of database sharding, focusing on why Postgres took longer than MySQL to develop mature sharding solutions. It discusses the origins of the term "shard," the role of MySQL's ecosystem and tools such as Vitess, and how companies including Facebook and YouTube addressed growth and increasing database workloads. ### Source excerpt Why has it taken so long to get good Postgres sharding? The last 20 years are the answer. ## History of Transit-Free (Tier 1) Networks DevFeed: [History of Transit-Free (Tier 1) Networks]() Original publisher: [Read original article]() Published: 2026-08-05T21:48:07Z Content type: article Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [Routing (disambiguation)](), [BGP](), [networking](), [Internet]() Tags: [as1](), [as1239](), [as174](), [as701](), [bgp](), [history](), [networks](), [ripe-ris](), [routing](), [tier1](), [transit]() ### AI overview The article examines the history of transit-free, or Tier 1, networks and tracks when autonomous systems became or ceased to be transit-free. It discusses historical evidence from BGP routing table dumps, RIPE RIS, Oregon Route Views, and related records. ### Source excerpt I find the concept of transit-free / Tier 1 networks fascinating. These are networks which, by definition, are transit-free. They do not have any transit and can reach the entire routing table just through peering relationships. The importance of these networks has reduced over time as more and more peering happens directly between eyeball networks and content networks. But regardless, I always find it fascinating that these networks effectively define the full autonomy of the internet routing table. Together with the trust in 13 magical root DNS servers and these transit-free networks define what we call "the internet" today. I was once chatting with my friend and guru Martin Levy (now happily retired) about which networks were possibly transit-free when the internet started. He suggested that Wikipedia history on Tier 1 networks has many of them. The challenge with the Wikipedia page on Tier 1 networks is that the list of transit-free networks appears on 14 Nov 2005. This leaves a gap around which networks were transit-free before Nov 2005. Before Nov 2005, Nov 2005 and till now I had an email exchange with Mr Randy Bush and he kindly replied with some hints. According to him AS701/702/703/704 (UUnet / now Verizon), AS174 (PSI / now Cogent), AS1 (BBN) and AS1239 (Sprint) were transit-free networks before this period. The oldest routing dump on RIPE RIS is from 1999 but those dumps are very small and contain too few routes to establish anything. RIPE RRC00 from September 1999 has "view" files, which are essentially a "sh ip bgp dump" and the following month they seem to have moved to the MRT format. On Oregon Route Views, the oldest I can find is this dump from 08 Nov 1997. This brings me to a possible, although not perfect, method to document the history of transit-free networks. Timeline Method Before-Nov 1997 Assume AS1, AS1239, AS701 and AS174 to be transit-free and find who else was adjacent to all of them along with BGP routing table dumps Pre - Nov 2005 Use ## History of SpaceX: Synthesis, the Independence Assumption, and Projection through 2050 DevFeed: [History of SpaceX: Synthesis, the Independence Assumption, and Projection through 2050]() Original publisher: [Read original article]() Author: Brendan Sechter Published: 2026-08-05T09:00:00Z Content type: opinion Language: en Sources: [Brendan A R Sechter's Development Blog]() Topics: [Framework]() Tags: [aerospace](), [analysis](), [business](), [framework](), [history](), [open-questions](), [projection]() ### AI overview This concluding article in a History of SpaceX series retrospectively assesses the series' framework, argues that its supposedly separable conditions are coupled, and examines how that independence assumption affects assessment. It also projects the analysis to 2050 under stated assumptions, ranks failure modes, and identifies unresolved questions. ### Source excerpt This article closes the History of SpaceX series. It has three tasks. The first is retrospective, restating the seven forcing-function conditions and the three capital-formation legs that the series opener introduced and that the intervening ten articles developed, and assessing what each turned out to establish. The second is critical, and it is the article's principal contribution. Across three independent articles the series encountered the same structural surprise, namely that conditions the framework treats as separable are in fact coupled, and the closing article argues that the coupling is general and not incidental and that the framework's independence assumption biases the assessment in opposite directions depending on the state of the world. The third is projective, extending the analysis to 2050 under explicitly stated assumptions and with the failure modes ranked, not merely listed. The article treats the alternative contemporary configurations that the commentary offers as templates, comprising the defense-technology venture, the failed-governance case, the intelligence-anchor case, and the patient-single-funder case, and the deep historical precedents comprising the industrial consolidation, the corporate research laboratory, the endowed foundation, the mass-production firm, and the early aircraft manufacturers. The article closes with the load-bearing open questions the series as a whole leaves unresolved, which are more numerous than any single article's closing section suggested. The Synthesis Problem The mapping problem for a closing article differs from that of the eleven that precede it. Those articles each asked what happened along one dimension. This one asks whether the dimensions were the right ones, whether the framework built from them holds together, and what it predicts. The series advanced a thesis, which the series opener states as the singular-conjunction claim. The claim is that a particular venture is the only modern case satisfying ## History of SpaceX: The Category-Dominating Commercial Spinoff and the Internalization of Anchor Demand DevFeed: [History of SpaceX: The Category-Dominating Commercial Spinoff and the Internalization of Anchor Demand]() Original publisher: [Read original article]() Author: Brendan Sechter Published: 2026-08-04T09:00:00Z Content type: article Language: en Sources: [Brendan A R Sechter's Development Blog]() Topics: [communications](), [Deployment](), [service]() Tags: [aerospace](), [beta](), [business](), [capacity](), [customer](), [deployment](), [history](), [international](), [launches](), [operational](), [partnership](), [regulatory](), [revenue](), [service](), [spacex](), [subscriber]() ### AI overview This article examines SpaceX's commercial spinoff as the internalization of an anchor customer. It explains how the spinoff consumes the parent's launch output at marginal cost, traces its deployment, service rollout, integration, subscriber and revenue development, direct-to-cell expansion, capital requirements, and regulation, and compares the configuration with other satellite-constellation businesses. ### Source excerpt This article is the eleventh in the History of SpaceX series and the third and last treating the capital-formation legs that the series opener introduced. The category-dominating commercial spinoff concerns the business the venture built on top of its own capability, and the article's organizing claim is that the spinoff is not a diversification into an adjacent market but the internalization of an anchor customer. Where the Anchor Demand article A283 treats a government customer buying launches, this article treats the venture becoming the customer it had previously needed someone else to be. The decisive economic property is not that the spinoff grew large. It is that the spinoff consumes the parent's output at marginal cost while every competitor attempting the same business must pay a market price the parent sets. The article walks the January 2015 announcement and the capacity argument that motivated it, the deployment sequence from the first operational batch of May 2019 through the service beta of 2020 and the commercial rollout of 2021, the vertical integration and the internal transfer price that the whole arrangement turns upon, the coupling between constellation deployment and launch cadence, the subscriber and revenue trajectory across the 2020 through drafting-date period, the direct-to-cell extension beginning with the carrier partnership announced in 2022, the capital intensity and the replenishment obligation that a short-lifetime constellation imposes, and the regulatory position across the Federal Communications Commission, the International Telecommunication Union, and the national regulators whose authorizations the service requires. The article contrasts the configuration against the Iridium and Globalstar precedents, in which comparable constellations were built without a captive launch capability, and against the OneWeb and Kuiper cases, in which competitors attempted the business while buying launch at market. The article closes with an expli ## History of SpaceX: The Patient-Private Capital-Formation Leg and the Manufacture of Patience DevFeed: [History of SpaceX: The Patient-Private Capital-Formation Leg and the Manufacture of Patience]() Original publisher: [Read original article]() Author: Brendan Sechter Published: 2026-08-03T09:00:00Z Content type: opinion Language: en Sources: [Brendan A R Sechter's Development Blog]() Topics: [structure](), [Google](), [Development]() Tags: [aerospace](), [article](), [business](), [company](), [google](), [history]() ### AI overview This analytical article examines how private-capital instruments financed SpaceX's development despite venture-fund time constraints. It focuses on investor entries, funding rounds, tender offers that provided liquidity without an exit, investor time horizons, and dilution management, while comparing the structure with Iridium and OneWeb. ### Source excerpt This article is the tenth in the History of SpaceX series and the second of three treating the capital-formation legs that the series opener introduced. The patient-private leg concerns the private capital that financed the development the government leg did not, on terms that surrendered equity and did not surrender the mission. The article's organizing claim is that patience is not a temperament that investors possess but a structural property that instruments manufacture, and that the instruments are identifiable, describable, and largely absent from the commentary that attributes the outcome to investor conviction. The binding constraint on private capital in the venture form is the fund-life clock, which obliges a fund to return capital to its limited partners on a schedule that has no relation to the development horizon of any portfolio company. The article walks the fund-life constraint and the duration mismatch it creates, the August 2008 Founders Fund entry at the moment of maximum distress, the 2009 Draper Fisher Jurvetson entry, the January 2015 Google and Fidelity round motivated by a business line that did not yet exist, the round and valuation sequence across the 2015 through drafting-date period, the semi-annual tender-offer mechanism that gives liquidity without exit and that the article treats as the decisive structural innovation, the composition of the investor base and the horizon heterogeneity across it, and the dilution management that preserved the control configuration the Governance article A287 analyzes. The article contrasts the configuration against the Iridium capital structure, in which a debt-financed constellation faced a fixed obligation schedule that no development delay could accommodate, and against the OneWeb funding withdrawal, in which a nominally patient investor proved otherwise. The article treats the contemporary defense-technology venture wave and the Anduril and Palantir comparisons as the downstream consequence. The arti ## How a medical database developed at MIT evolved into a global standard of data-sharing DevFeed: [How a medical database developed at MIT evolved into a global standard of data-sharing]() Original publisher: [Read original article]() Author: Emma Foehringer Merchant | Institute for Medical Engineering and Science Published: 2026-07-29T14:00:00Z Content type: news Language: en Sources: [MIT AI News]() Topics: [data](), [Database](), [datasets]() Tags: [academic](), [artificial-intelligence](), [data](), [database](), [electrical-engineering-and-computer-science-eecs](), [global-data-sharing](), [harvard-mit-health-sciences-and-technology](), [harvard-mit-health-sciences-and-technology-hst](), [health](), [health-care](), [health-data-nexus](), [health-sciences-and-technology](), [history](), [history-of-mit](), [history-of-science](), [history-of-science-and-technology](), [information-systems](), [institute-for-medical-engineering-and-science-imes](), [internet](), [medical-data-sharing](), [medicine](), [mimic-medical-information-marked-for-intensive-care](), [mit-imes](), [mit-rle](), [physionet](), [repositories](), [research](), [research-laboratory-of-electronics](), [school-of-engineering](), [science](), [thomas-heldt](), [tom-pollard]() ### AI overview An MIT-developed collection of digitized electrocardiogram recordings became the foundation of PhysioNet, a global repository for biomedical and clinical data. The platform now hosts hundreds of databases and supports research users worldwide. ### Source excerpt The visionary PhysioNet platform launched 25 years ago, based on a system developed at MIT in the 1970s. It has become one of the most comprehensive biomedical and clinical data repositories in existence. ## Why AI agent session logs can preserve reasoning that code and Git history omit DevFeed: [Why AI agent session logs can preserve reasoning that code and Git history omit]() Original publisher: [Read original article]() Published: 2026-07-29T00:00:00Z Content type: opinion Language: en Sources: [Juri Strumpflohner]() Topics: [AI Bots](), [AI Development](), [context](), [Software Engineering](), [Git]() Tags: [agent](), [agents](), [ai](), [ai-agents](), [context](), [git](), [history](), [logs](), [polygraph](), [reasoning](), [software-development]() ### AI overview This opinion article argues that AI agent session logs can preserve prompts, dead ends, corrections, and other reasoning that may be absent from source code and Git history. It presents session logs as a complementary software-development artifact because agent context can disappear when a session ends. ### Source excerpt Your agent sessions are more important than your Git history You want to understand a part of the codebase, so you run to see who implemented it. Except it wasn't really them, it was their agent, and that agent, along with the reasoning that went into that code, is long gone. We're working at a higher level of abstraction now, and the reasoning behind a change can vanish the moment the agent session that produced it ends, leaving nobody, human or agent, able to explain the exact "why" later. ## Context engineering for AI: what it is & how to build it DevFeed: [Context engineering for AI: what it is & how to build it]() Original publisher: [Read original article]() Author: Simba Khadder Published: 2026-07-29T00:00:00Z Content type: tutorial Language: en Sources: [Redis Blog]() Topics: [AI Chat](), [AI Bots]() Tags: [agent](), [agents](), [ai](), [ai-agent](), [apps](), [crm](), [engineering](), [history](), [how-to](), [inference](), [infrastructure](), [latency](), [llm](), [model](), [policy](), [prompt-engineering](), [reasoning](), [support](), [systems](), [tech-de](), [tool]() ### AI overview A guide to context engineering for AI agents: selecting and managing the instructions, history, retrieved documents, tool outputs, and state sent to an LLM during inference. It explains how deliberate context management helps avoid hallucinations, excessive context, latency, and degraded reasoning in multi-step agent workflows. ### Source excerpt Your support agent confidently tells a customer they qualify for a refund under a 60-day return policy. Your actual policy is 30 days. The agent hallucinated the longer window, and the easy reaction is to blame the model. But the model never saw your ... ## Celebrating 5 years of Jetpack Compose DevFeed: [Celebrating 5 years of Jetpack Compose]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-07-28T16:00:00Z Content type: article Language: en Sources: [Android Developers Blog](), [Android Developers Blog]() Topics: [Jetpack Compose](), [Android](), [Kotlin](), [Compiler](), [XML]() Tags: [android](), [apis](), [apps](), [community](), [compose](), [developers](), [development](), [devices](), [engineering](), [history](), [jetpack](), [mobile](), [production](), [release](), [ui](), [updates]() ### AI overview The article celebrates five years of Jetpack Compose, tracing its evolution from the 1.0 release in 2021 to version 1.11. It highlights Compose's adoption in Android production apps, expansion across mobile and other form factors, development history, community involvement, and progression from Material 2 to Material 3 Expressive. ### Source excerpt Posted by Rebecca Franks, Developer Relations Engineer, Nick Butcher, Product Manager, Loryn Hairston, Product Marketing Manager, Android Today, we officially celebrate five years since the release of Jetpack Compose 1.0. From version 1.0, announced on July 28th, 2021, to our latest 1.11 release, we've seen the APIs evolve significantly over the years, and we're taking a moment to celebrate. When we officially announced the 1.0 release, we promised a simpler, faster, and more intuitive way to build native interfaces on Android. Looking back, it's safe to say that Compose didn't just deliver on that promise, but also completely changed the Android ecosystem, with more than 68% of the top 1,000 apps using it in production today. History Over the last five years, Compose has grown steadily. In the early days, we explored showing you how to build layouts with the basic Box, Row, and Column. Today, we've expanded Compose to work not just on mobile devices, but to other form factors such as Compose for TV, WearOS, Glance for Widgets, and even display glasses with Jetpack Compose Glimmer. We recorded an Android Developers Backstage episode with Clara Bayarri, Engineering Lead for Jetpack, and two former leads of the team, Romain Guy and Chet Haase, along with Tor Norbye, Senior Engineering Director. In this episode, they discuss the history of Compose and the early days of development. Compose highlights over the years Looking back The beginnings of Compose were very different from what you know today. Two projects were happening in parallel inside the Android team. At the time, the Views toolkit team was thinking of unbundling the UI Toolkit into a library to help with development speed, and make it easier for developers to adopt and control updates. Meanwhile, a team was working on a novel idea to build declarative layouts by embedding XML inside Kotlin, which looked something like this: Those two efforts merged to produce what you know today - a fully declarative UI Too ## IBM to acquire HRL Laboratories DevFeed: [IBM to acquire HRL Laboratories]() Original publisher: [Read original article]() Author: Ryan Mandelbaum Published: 2026-07-23T11:00:00Z Content type: article Language: en Sources: [IBM Research]() Topics: [ibm](), [.NET Conf]() Tags: [acquisition](), [explainer](), [history](), [ibm](), [quantum](), [research](), [science](), [technology]() ### AI overview IBM announced a definitive agreement to acquire HRL Laboratories, citing HRL's silicon-spin qubit expertise as complementary to IBM's quantum-computing research. The article also recounts HRL's history, including its contributions to aviation, electronics, radar, and the invention of the laser. ### Source excerpt Exploring the storied history of HRL Laboratories, from the invention of the laser to silicon spin qubits. ## How Sentry replaced ASCII snapshots with structured context for Seer Agent DevFeed: [How Sentry replaced ASCII snapshots with structured context for Seer Agent]() Original publisher: [Read original article]() Author: Mihir Mavalankar Published: 2026-07-16T09:00:00Z Content type: article Language: en Sources: [Sentry Blog]() Topics: [context](), [dashboards](), [Document Object Model (DOM)](), [Claude]() Tags: [agent](), [claude](), [context](), [cost](), [history](), [structure]() ### AI overview Sentry describes replacing ASCII page snapshots with structured semantic context for its Seer Agent. The change is intended to reduce token costs and context degradation while enabling richer interaction hints and future page manipulation. ### Source excerpt How Sentry replaced ASCII page snapshots with structured semantic context to make Seer Agent faster, cheaper, and ready for agentic actions. ## Build Durable Chat Memory for RAG Using ScyllaDB and LangChain DevFeed: [Build Durable Chat Memory for RAG Using ScyllaDB and LangChain]() Original publisher: [Read original article]() Author: Cynthia Dunlop Published: 2026-07-14T12:54:49Z Content type: tutorial Language: en Sources: [ScyllaDB]() Topics: [AI Chat](), [Language models]() Tags: [2026-2](), [ai](), [ai-ml](), [ann](), [cassandra](), [database](), [ecosystem](), [embeddings](), [history](), [how-to](), [langchain](), [language-models](), [latency](), [memory](), [rag](), [retrieval](), [scalability](), [sentence-transformers](), [vector]() ### AI overview A tutorial on replacing LangChain's in-memory chat history with ScyllaDB for durable RAG chatbot memory across restarts and replicas. ### Source excerpt How to replace LangChain's in-memory chat history with ScyllaDB -- so your RAG chatbot retains context across restarts and scales across replicas [Next page]()