Elezea — link posts

I Left Port 22 Open for 54 Days: An SSH Honeypot Study

Rian van der Merwe — Sun, 10 May 2026 00:16:16 GMT

This post is a fascinating look at how botnets actually work. I don’t want to spoil the takeaways so I’ll just quote this (but you should read the whole thing):

Your server isn't special. Nobody is "targeting" it. Every IP address on the internet is being continuously probed by automated systems. Within seconds of exposing port 22, you will receive login attempts. This isn't a question of "if" but "when" — and the answer to "when" is "immediately."

Thanks for still believing in RSS! Feel free to get in touch.

Song of the Day: May 6, 2026

Rian van der Merwe — Thu, 07 May 2026 02:47:35 GMT

This song is all over my Instagram Reels for some reason and it is such a vibe I can't get enough of it.

▶ Listen on Spotify

Thanks for still believing in RSS! Feel free to get in touch.

Why Did Hollywood Stop Making Dramas?

Rian van der Merwe — Fri, 01 May 2026 22:21:18 GMT

I guess this shows just how old I am because I loved every single one of the “Oscar-bait” movies in this list (I do agree on TCM though)...

When I was a kid, I would watch Turner Classic Movies and try to appreciate films from the 1940s, only to find the exercise strangely difficult. I could admire them—in theory—but I struggled to experience these stories the way their original audiences did.

I feel similarly about many Oscar-bait dramas of the 1990s, including but not limited to: Chocolat, American Beauty, Shakespeare in Love, Scent of a Woman, The English Patient, and Life Is Beautiful. I simply don’t understand what contemporary audiences saw in these films.

That aside, as usual Daniel makes an interesting larger point, about why we don’t see as many dramas as we used to:

Action and horror, meanwhile, have visceral elements that translate across generations: big dinosaurs, jump scares, campy set pieces, and other straightforward pleasures. The first ten minutes of Raiders of the Lost Ark are timeless and feature almost no dialogue.

Thanks for still believing in RSS! Feel free to get in touch.

How to stay relevant when the PM role keeps rewriting itself

Rian van der Merwe — Wed, 29 Apr 2026 00:25:50 GMT

Melissa Perri chimes in on how AI is changing the product role, and makes the case for measuring PMs by decisions changed and outcomes shipped, not by tickets written and docs generated:

If you are a PM, stop measuring your productivity by how many tickets you wrote, how many pages of documentation you spun up, or how fast you closed the loop on the last sprint. That work is going to keep getting easier.

Measure your productivity by how often you changed a decision that mattered, how often you saw around a corner, how often a senior leader walked out of a room thinking differently because of something you said. How often your shipped features translate into real customer outcomes is what matters.

Everything I read is saying the same thing right now: judgment, customer understanding, and the ability to change a senior leader's mind in a room are the skills that AI can't touch. I'm not disagreeing necessarily, but I do think that narrative is missing a big new skill that is needed. I wrote about this in What actually changed about being a PM:

I was talking to my wife the other day about what I’m doing, and she asked the obvious question: “Why are you automating your job away?” My answer: the people who automate their own jobs away are the ones who become more valuable, because the craft is now in orchestration — setting up the layers so the AI does the right thing.

I also continue to think about this quote from Org Design in the Age of AI and how the focus is shifting from "information movers" to builders:

The old PM spent most of their energy making ideas legible to other people. The new PM validates directly — prototyping, running data analyses, generating first-pass implementations. [...] The managers who thrive will be the ones whose real contribution was always judgment, coaching, and navigating ambiguity — not routing information.

Thanks for still believing in RSS! Feel free to get in touch.

Product Roadmaps: How the Best Product Teams Plan for Uncertainty

Rian van der Merwe — Tue, 28 Apr 2026 22:32:05 GMT

I'm a big fan of Now/Next/Later roadmaps, and I think it adapts particularly well to an AI-assisted world, so I was curious to read Teresa's Take on different roadmap models. It's a fun trip through different prioritization frameworks, and I do like her reframing of the Now/Next/Later approach:

Here's what I've seen work best: Take the Now Next Later format, but instead of filling every column with features at different levels of detail, change the type of content as you move across columns. [...]

Specifically, I list solutions in the Now column, opportunities in the Next column, and outcomes in the Later column.

Thanks for still believing in RSS! Feel free to get in touch.

Deezer: AI-generated tracks now represent 44% of all new uploaded music

Rian van der Merwe — Sat, 25 Apr 2026 23:40:08 GMT

This is characteristically dry press release language, but the stats are interesting:

Deezer, the global music experiences platform, is now receiving almost 75,000 AI-generated tracks per day, representing roughly 44% of the daily uploads. This amounts to more than 2 Million AI-generated tracks uploaded per month. Thanks to Deezer's industry unique measures, consumption of AI-generated music on the platform is still very low, between 1-3% of the total streams. In addition, a majority (85%) of these streams are detected as fraudulent and are demonetized by Deezer.

I’m simultaneously surprised (but not, because grifters) that the amount of uploads is that high, and surprised (but not, because music lovers) that it’s generally a very unsuccessful way to make money. My continuing refrain will be that let’s use AI for the things that it’s good at, and leave the really important stuff (like art) to humans.

Thanks for still believing in RSS! Feel free to get in touch.

AI Prototyping Is Changing How We Build Products at Uber

Rian van der Merwe — Fri, 24 Apr 2026 15:26:01 GMT

There is no doubt that this post was at least 80% written by AI but I’m not even super mad about it because that is just the way of the world now, and the summary it generated from how Uber works is actually legit interesting:

A prototype without a PRD can drift away from the problem the team intends to solve. A PRD without a prototype can remain abstract, leaving room for inconsistent interpretations. [...] If going from idea to prototype is now fast and cheap, the PRD can no longer be the primary place where ideas are defined. Its value increasingly lies in capturing intent, tradeoffs, success metrics, and decisions.

The PRD as an artifact is in the spotlight right now in a way that I think is really healthy. Should it remain but change its JTBD? Should it be an eval instead? Who knows. Let’s figure it out together...

Thanks for still believing in RSS! Feel free to get in touch.

Org Design in the Age of AI

Rian van der Merwe — Wed, 22 Apr 2026 00:15:59 GMT

This post on org design really resonated.

Most companies today are using AI the way you'd use a faster horse — to make the existing structure run a little better. The companies that pull ahead will be the ones willing to ask a harder question: what would we build if we were designing this organization from scratch, today, knowing what AI can do?

We have to seriously rethink the SDLC, design it from scratch in the context of how our own organizations work. It’s not about a global “right” process any more. The question now becomes “How can the humans in our team, at our company, at this point in time, work best together to serve our customers?”

Thanks for still believing in RSS! Feel free to get in touch.

The peril of laziness lost

Rian van der Merwe — Tue, 21 Apr 2026 23:31:35 GMT

Oh, this is very good. On the classic take that the core characteristic of outstanding engineers is “laziness”:

The problem is that LLMs inherently lack the virtue of laziness. Work costs nothing to an LLM. LLMs do not feel a need to optimize for their own (or anyone's) future time, and will happily dump more and more onto a layercake of garbage. Left unchecked, LLMs will make systems larger, not better — appealing to perverse vanity metrics, perhaps, but at the cost of everything that matters. As such, LLMs highlight how essential our human laziness is: our finite time forces us to develop crisp abstractions in part because we don't want to waste our (human!) time on the consequences of clunky ones.

The best engineering is always borne of constraints, and the constraint of our time places limits on the cognitive load of the system that we're willing to accept. This is what drives us to make the system simpler, despite its essential complexity.

This is exactly why I practice Fear-Driven Development, and why everything I do in code includes multiple versions of asking Claude Code “do we need this?” and “is this adding bloat?”

Thanks for still believing in RSS! Feel free to get in touch.

Is Hip-Hop in Decline? A Statistical Analysis

Rian van der Merwe — Sat, 18 Apr 2026 00:59:06 GMT

I love this blog and try not to link to it too much, but this one about how fewer people listen to hip hop was especially great.

So, what’s filled the space hip-hop once dominated? A blend of new arrivals and familiar mainstays. Latin music—led by Bad Bunny—and Asian pop, powered by K-pop acts like BTS, have expanded their global footprint. At the same time, legacy formats are resurging: country is booming, driven in large part by Morgan Wallen, while the loosely defined “alternative” category continues to gain share across the charts.

I particularly love how he tries to avoid causation/correlation errors in his hypotheses. Like this one I hadn’t thought about:

Streaming adoption laggards: Hip-hop uniquely benefited from early streaming adopters in the 2010s. Younger listeners—who were predisposed to the genre—were among the first to embrace platforms like Spotify, giving hip-hop an outsized digital footprint. More recently, late adopters—like country fans, older cohorts, and global audiences—have rebalanced the charts, lifting genres like country and K-pop.

Thanks for still believing in RSS! Feel free to get in touch.

Evals Are the New PRD

Rian van der Merwe — Wed, 15 Apr 2026 17:31:37 GMT

Braintrust makes a good case (apologies for the X.com link...) for rethinking how PMs work on AI products: the eval replaces the PRD.

An eval is a structured, repeatable test that answers one question. Does my AI system do the right thing? You define a set of inputs along with expected outputs, run them through your AI system, and score the results using algorithms or AI judges.

The eval becomes both the spec and the acceptance criteria. The directive to engineering:

"Here is the eval. Make this number go up."

That's very different to how most teams work today, but I can definitely see the industry moving this way. Product usage generates signals, observability captures them, and evals turn them into improvement targets. The PM's job is to define what "good" looks like in code and curate the data that reveals what "bad" looks like.

The PM skills that transfer are the same ones that always mattered — discovering needs and opportunities, and making judgment calls about what to build for business value. The difference is that instead of a document that describes the intent, you have a test suite that encodes it.

Thanks for still believing in RSS! Feel free to get in touch.

No One Else Can Speak the Words on Your Lips

Rian van der Merwe — Tue, 14 Apr 2026 02:17:00 GMT

Ben Roy explains why prompting an LLM to write an essay misunderstands what writing actually is:

People fundamentally can't prompt good essays into existence because writing is not a top-down exercise of applying knowledge you have upfront and asking an LLM to create something. AI agents also can't create good essays for the same reason. Even though their step-by-step reasoning is more complex and iterative than human prompting, a chain of thought is still trying to accomplish a predefined goal. By contrast, real writing is bottom up. You don't know what you want to say in advance. It's a process of discovery where you start with a set of half-baked ideas and work with them in non-linear ways to find out what you really think.

I will continue to argue that for general business writing LLMs are fantastic if they are given the right context and guidance, and that it can save hours of work (with high quality results). But all my experiments with using LLMs for creative writing has so far fallen flat. Maybe—likely?—that will change within the next few months. But for now, the brain work this kind of writing requires remains. Not a bad thing imo.

Thanks for still believing in RSS! Feel free to get in touch.

Zombie Flow

Rian van der Merwe — Sun, 12 Apr 2026 14:54:13 GMT

Derek Thompson goes into the history of the "flow" concept, and how tech and entertainment companies learned to simulate it without any of the substance psychologist Mihaly Csikszentmihalyi originally had in mind:

Algorithmic flow is flow without achievement, flow without challenge, flow without even volition... To be lost in the lazy river of algorithmic media is to be lost the current of life without a mind. Zombie flow.

Ten years ago the question was how to get into flow more often. Now it might be how to get out of the fake version fast enough to remember what the real one felt like.

Thanks for still believing in RSS! Feel free to get in touch.

AI might actually need more PMs

Rian van der Merwe — Fri, 10 Apr 2026 20:51:22 GMT

Amol Avasare, Anthropic's Head of Growth, said on Lenny's Podcast that maybe PM jobs are not going to shrink as much as we may have thought...

Rather than immediately replacing PMs, AI is currently increasing engineering leverage the fastest, which creates new pressure on PMs and designers. In larger organizations, that may actually increase the value of PMs who can guide priorities, manage alignment, and sharpen decision-making—especially as engineers take on more "mini-PM" responsibilities.

Thanks for still believing in RSS! Feel free to get in touch.

Eight years of wanting, three months of building with AI

Rian van der Merwe — Fri, 10 Apr 2026 20:41:58 GMT

Lalit Maganti writes about building a SQLite parser with AI — a project he'd been putting off for eight years, finished in three months. His comparison of AI coding to slot machines is uncomfortably familiar:

I found myself up late at night wanting to do "just one more prompt," constantly trying AI just to see what would happen even when I knew it probably wouldn't work. The sunk cost fallacy kicked in too: I'd keep at it even in tasks it was clearly ill-suited for, telling myself "maybe if I phrase it differently this time."

Also, I agree that this is still true today, but I'm not convinced it will remain true beyond 2026:

AI is an incredible force multiplier for implementation, but it's a dangerous substitute for design.

Thanks for still believing in RSS! Feel free to get in touch.

Endgame for the open web

Rian van der Merwe — Sun, 29 Mar 2026 17:57:15 GMT

Anil Dash has a long essay on the state of the open web and not all of it rings true for me, but buried in the opening is a wonderful definition of what the open web actually is:

The open web is something extraordinary: anybody can use whatever tools they have, to create content following publicly documented specifications, published using completely free and open platforms, and then share that work with anyone, anywhere in the world, without asking for permission from anyone. Think about how radical that is.

It does feel like if the web got invented in 2026, it would not have been left as an open technology for long (see also AI and how much open source models are lagging).

Thanks for still believing in RSS! Feel free to get in touch.

Negative space in writing

Rian van der Merwe — Tue, 24 Mar 2026 00:14:41 GMT

Tracy Durnell explores non-visual negative space—what happens when writing leaves room for the reader to think:

The current design trend of business and self-help style books is to use tons of subheadings and callout boxes and always, a list of the key points at the end of the chapter. While this is a highly skimmable format and often nice visual design, it essentially sucks the negative space out of the text — the places in which the reader might step back and consider their own examples or anticipate what point the author is trying to make. There's no time for hunches here.

And:

The negative space of the text helps build the aesthetic experience. Small details flavor the text with a sense of reality. Drawing out events — leaving questions unresolved and conflicts unsettled — can build tension. And textual space creates a gap for the reader to make the personal decodings of the text that build meaning.

Not everything has to get to the point immediately. Sometimes the best thing a writer can do is leave room for the reader to get there on their own. I'm thinking about this because I'm currently reading The Will of the Many. It is slow, and long, and one of the best books I've read in ages. The negative space is probably a big reason why I love it so much.

Thanks for still believing in RSS! Feel free to get in touch.

Agentic manual testing

Rian van der Merwe — Mon, 23 Mar 2026 23:53:30 GMT

Simon Willison has a practical guide on manual testing with coding agents. Two tips I've already started using:

It's still quick for an agent to write out a demo file and then compile and run it. I sometimes encourage it to use /tmp purely to avoid those files being accidentally committed to the repository later on.

And:

If an agent finds something that doesn't work through their manual testing, I like to tell them to fix it with red/green TDD. This ensures the new case ends up covered by the permanent automated tests.

Thanks for still believing in RSS! Feel free to get in touch.

When Using AI Leads to “Brain Fry"

Rian van der Merwe — Sat, 14 Mar 2026 13:58:45 GMT

I am definitely feeling the "brain fry" right now:

We found that the phenomenon described in these posts—cognitive exhaustion from intensive oversight of AI agents—is both real and significant. We call it “AI brain fry,” which we define as mental fatigue from excessive use or oversight of AI tools beyond one’s cognitive capacity. Participants described a “buzzing” feeling or a mental fog with difficulty focusing, slower decision-making, and headaches.

The research is fascinating and worth reading, with super interesting findings like this:

As employees go from using one AI tool to two simultaneously, they experience a significant increase in productivity. As they incorporate a third tool, productivity again increases, but at a lower rate. After three tools, though, productivity scores dipped. Multitasking is notoriously unproductive, and yet we fall for its allure time and again.

Earlier this week I had this thought: "Oh no, I think I've blown out my context window. I wish I could add some more tokens to my brain. Until then I might just have to respond to new requests with 401 Unauthorized."

And that's when I realized I probably need to go touch grass or something.

Thanks for still believing in RSS! Feel free to get in touch.

AI should help us produce better code

Rian van der Merwe — Sat, 14 Mar 2026 13:43:35 GMT

As usual, Simon Willison hits the nail on the head here:

If adopting coding agents demonstrably reduces the quality of the code and features you are producing, you should address that problem directly: figure out which aspects of your process are hurting the quality of your output and fix them. Shipping worse code with agents is a choice. We can choose to ship code that is better instead.

Also see Mitchell Hashimoto’s idea of “harness engineering”:

It is the idea that anytime you find an agent makes a mistake, you take the time to engineer a solution such that the agent never makes that mistake again.

Thanks for still believing in RSS! Feel free to get in touch.