The Changelog: Software Development, Open Source - The tech monoculture is finally breaking (News)

Episode Date: February 2, 2026

Jason Willems believes the tech monoculture is finally breaking, Don Ho shares some bad Notepad++ news, Tailscale's Avery Pennarun pens a great downtime apology, Milan Milanović explains why you can only code 4 hours per day, and Addy Osmani on managing comprehension debt when leaning on AI to code.

What's up nerds? I'm Jared, and this is ChangeLog News. For the week of Monday, February 2nd, 2026, Maltbot may be dead because it was renamed to OpenClaw, but Malt Book is very much alive and is currently teeming with AI agents who share, discuss, and upvote each other because we told them to. Don't worry. humans are invited to observe, I suggest starting in the Today I Learned, sub, or going outside.

Yeah, let's do that. We could all use more vitamin D anyhow. Okay, let's get into this week's news. The tech monoculture is finally breaking. Jason Willems really lifted my spirits with this post, but first, the long slow decline. Quote, in the early 2000s, tech began a decades-long consolidation. Almost everything we used before became a function of a single device. Our devices lost their unique personalities. Phones became our alarm clocks, flashlights, calendars, cameras, GPS units, music players, radios, journals, and gaming devices, all at once. We betrayed our focus in the pursuit of convenience and the personality of our devices for homogeneity. End quote.

The benefits of this transition were clear to us, but at what cost? Jason argues it was high. I tend to agree, but the pendulum is starting to swing in the other direction. quote, new paradigms are emerging for the first time since mobile. VR is no longer experimental. Early AR is starting to reach consumers. Meta shipped a wearable that normal people use thanks to a clever Rayband partnership and associated equity stake. 3D printers have become real household products. Wearables are diversifying, smart rings, over-the-counter glucose monitors, connected beds, end quote. Jason says he acquired more new devices in 2025 than in the

previous five years combined and 2026 is off to a hot start too. Quote, we'll never truly recreate the late 80s or mid-90s. SaaS, subscription pricing, and centralized platforms are here to stay. But this feels like the beginning of another golden era. One to find less by

consolidation and more by variety, personality, and choice. Notepad++ hijacked by state-sponsored hackers. Notepad++ author Don Ho shares some bad news. Following the security disclosure published in the version 8.8.9 announcement,

the investigation has continued in collaboration with external experts and with the full involvement of my now former shared hosting provider. According to the analysis provided by the security experts, the attack involved infrastructure level compromise that allowed malicious actors to intercept and redirect update traffic destined for notepad++.org, end quote. The attackers were able to redirect update traffic to malicious service, for a regrettable length of time.

What's a dev to do? Quote, I deeply apologize to all users affected by this hijacking. I recommend downloading version 8.9.1, which includes the relevant security enhancement and running the installer to update your Notepad++ manually. With these changes and reinforcements, I believe the situation has been resolved. Fingers crossed, end quote.

Notepad++ is, in my elderly opinion, one of the coolest pieces of software on the entire internet. What a shame. This is why we can't have. nice things. Hypergrowth isn't always easy. Tailscales, Avery Penneron penned a system downtime apology so good, I'm sharing it here for you to enjoy and perhaps to emulate. Quote, it's true that many of our outages don't sever existing connections. That's a deliberate part of the design. But if you happen to need the control plane during those minutes, you feel the outage at full

force. That's not acceptable. Tailscale is critical infrastructure for a lot of organizations, and we have to earn that trust by making these incidents rarer and shorter. So, what are we going to do about it? Well, a few things. End quote. After sharing four concrete steps, the tailscale team is taking to mitigate future problems, Avery says, quote, I'm not going to lie to you.

None of us are proud of having counts on fingers. Nine periods of partial, downtime, or maybe slowness, in one month. Even though almost all were resolved in less than an hour. Even though your data plane kept going, because, well, that's who we are. and who we are is a team that would rather over-communicate than under-communicate. Even when an incident is brief or affects only some customers, we want it to be visible and explained. We are going to keep counting every single small outage and measuring it

and fracturing it into two smaller outages and eventually obliterating it, one improvement at a time. That's just how it's done. End quote. The closer is a link to the form where you can report an outage and a link to their career page for those who like solving problems like the ones they face. Chef's Kiss. It's now time for sponsored news. Agenic development needs forcable databases.

Repelit and Tiger Data built the same thing. And here's why. Agenic experimentation requires forcable state. Repelit recently published details about their internal snapshoting infrastructure. They call it bottomless storage and it's built on GCS with immutable 16 megabyte blocks. Tiger Data read it and realized they've been solving the same problem with fluid storage just with different tradeoffs. This convergence wasn't accidental. It's what happens when you actually build for how agents work. See, agents don't execute linearly. They branch, they fail, they retry. They explore multiple paths before

converging on a solution. Traditional databases assume a few long-lived environments. Agenic developments invert this entirely. You need databases that you can fork instantly, experiment on safely, and rollback without consequences. The technical divergence is interesting, though. Replit optimized for append-heavy workloads with 16-mecbyte blocks, where a single 4-kilabyte update amplifies to 16-megabyte rights. Tiger Data went with 4-kilobytes, about 1 millisecond of read latency, and less than 5 milliseconds of right latency, optimized for the fine-grained random access patterns that database workloads actually produce. Different roads, same destination. Snapshot-based infrastructure isn't optional for production

a.mast systems. It's foundational. Read the full comparison at tigerdata.com or check the link of the newsletter to get to that blog post. You can code only four hours per day. Here's why. Here's Malan Milanovic. Quote, you probably felt it. After a few hours of coding, your brain isn't as fresh anymore. A good day can give you maybe three to four hours of deep, focused coding. After that, quality and focus drop. Research in cognitive psychology also supports the pattern. Across the teams I've led and coached, the same loop keeps showing up. Developers judge themselves by an eight-hour ideal, then feel behind when only a few hours produce real output. But high-focus work has a ceiling, treating three to four hours as the primary objective

leads to better software and less burnout. End quote. This certainly resonates with me. Back in my contracting days, I tried to bill six hours each day, and I'd only bill when I was actively coding, and getting to a consistent six hours was rough. The rest of Milan's article covers the cognitive ceiling, where developer time actually goes, the cost of interruptions, flow as a force multiplier, strategies for deep work, and why managers should care. Comprehension debt, a hidden cost we don't track.

Here's Adi Asmani on managing comprehension debt when leaning on AI to code. Quote, generation, or writing code, and discrimination, reading code, are different cognitive capabilities. You can review code competently even after your ability to write it from scratch has atrophied. But there's a threshold where review becomes. rubber stamping, end quote. I feel seen in this one. I've certainly looked at areas of a code base I oversaw

the writing of and struggled to understand what is going on. That being said, I've done that for code I wrote personally as well. Sometimes, as recently as yesterday. Addie says, quote, the dangerous part, it's trivially easy to review code you can no longer write from scratch. If your ability to read

doesn't scale with the agent's ability to output, you're not engineering anymore. You're hoping. That's the news for now, but go and subscribe to our ChangeLog newsletter for the full scoop of links worth clicking on, such as Backseat Software, a lightning fast private Gmail archive and search system, and a tool to render mermaid diagrams in your terminal. Get in on the newsletter at changelog.News. Have yourself a great week. Like, subscribe, and leave us a five-star review. If you like the show, and I'll talk to you again real soon.