Over the past years, the author of the cURL project, [Daniel Stenberg], has repeatedly complained about the increasingly poor quality of bug reports filed due to LLM chatbot-induced confabulations, also known as ‘AI slop’. This has now led the project to suspend its bug bounty program starting February 1, 2026.
Examples of such slop are provided by [Daniel] in a GitHub gist, which covers a wide range of very intimidating-looking vulnerabilities and seemingly clear exploits. Except that none of them are vulnerabilities when actually examined by a knowledgeable developer. Each is a lengthy word salad that an LLM churned out in seconds, yet which takes a human significantly longer to parse before dealing with the typical diatribe from the submitter.
Although there are undoubtedly still valid reports coming in, the truth of the matter is that the ease with which bogus reports can be generated by anyone who has access to an LLM chatbot and some spare time has completely flooded the bug bounty system and is overwhelming the very human developers who have to dig through the proverbial midden to find that one diamond ring.
We have mentioned before how troubled bounty programs are for open source, and how projects like Mesa have already had to fight off AI slop incidents from people with zero understanding of software development.
US sports brand launches probe after extortion crew WorldLeaks claims it stole huge dataset
Nike says it is probing a possible breach after extortion crew WorldLeaks claimed to have lifted 1.4TB of internal data from the sportswear giant and posted samples on its leak site.…
Some machines are failing to start after security updates, prompting yet another Microsoft investigation
Microsoft is investigating reports that its January 2026 security updates are leaving some Windows 11 machines stuck in a boot loop, adding another entry to this month's bumper post–Patch Tuesday borkage list.…
Autonomous agents may generate millions of lines of code, but shipping software is another matter
Opinion AI-integrated development environment (IDE) company Cursor recently implied it had built a working web browser almost entirely with its AI agents. I won't say they lied, but CEO Michael Truell certainly tweeted: "We built a browser with GPT-5.2 in Cursor."…
Privacy tools are a start, but real freedom lives in the digital outskirts of the web
Opinion The Net is born free, but everywhere is in chains. This is a parody of Jean-Jacques Rousseau's 1762 book The Social Contract where he said the same about humans, but it's nonetheless true. The Net is built out of open, free protocols and open, free code. Yet it and we are bound by the rulemakers who build the services and set the laws of the places we go and the things that we do, not to our advantage.…
Forza Horizon 6's Steam page shows the bare minimum users will need to play the racer. Microsoft says the requirements have increased compared to the previous entry, which you'd expect, though it does include Intel's B390 iGPU.
Coauthoring a book can be a challenge. While the authors share a common goal, each might have a different writing style, voice, and writing cadence, as well as specific ways of organizing a chapter. Most of these differences are easily remedied through an initial virtual session where the authors agree on a consistent style, format, voice, and so on, with occasional follow-on virtual sessions to ensure consistency. However, in our experience, this is not enough.
Between the three of us, we’ve coauthored five highly successful technical books over the years. This blog post is about three techniques that have helped us overcome some of the challenges of coauthoring, with a particular emphasis on one of the most useful techniques: the in-person experience.
Create a Narrative Arc
Everyone loves a good story. Stories capture our attention for one reason: They have a solid narrative arc, a literary term for the path a story follows. It’s what gives any story a clear beginning, middle, and end.
The narrative arc of a story
A good story starts out with exposition to set the scene, introduce the characters, and communicate the stakes. As time progresses, the tension increases, conflicts arise, and the story becomes more complex. Finally, the climax of the story unfolds, leading to the resolution and ending. This is how great books are written—including technical ones.
The first thing we do in any book project with O’Reilly is to collectively establish the narrative arc. This allows us to focus on telling a story about our subject.
Involve Your Editor
We attribute much of our success to heavily involving our editor in the entire writing process. We’ve learned that having our editor understand our narrative arc and our style and voice choices pays off in spades. Your editor is not there just to revise your grammar: They guide you through the writing process, teaching you better writing skills along the way and ensuring consistency throughout the book.
We include our editor in our weekly meeting calls and our constant text and email exchanges. She essentially functions as an additional coauthor and adds a tremendous amount to the overall finished product. Make no mistake—the editor makes all the difference in the world, not only to the finished product but to the overall writing experience.
For each book, we create a shared Google spreadsheet that helps all of us (including our editor) remain organized. It’s our source of truth for which chapters each author will draft, complete with each chapter’s deadlines and current status. It also includes room for short notes on each chapter. It’s always open during our weekly meetings.
Meet in Person
While the first two tips help coauthors stay organized and focused on a common goal, by far the most valuable technique we use is periodically meeting in person. We meet at least twice per book, sometimes more if we can arrange it logistically. Before each meeting, we all contribute to an agenda, listing things we are struggling with or want to discuss. We meet over a long weekend, starting Friday afternoon and going through Sunday. We make sure to take breaks and have fun too: We go out to a nice dinner each night and play board games well into the evening.
This might not seem necessary, given the ease of virtual meetings, but the results of these in-person meetings have been staggering. We rotate the location of the meeting between coauthors’ houses to ease travel costs. Although scheduling and traveling to in-person meetings can be expensive and logistically challenging, every time we’ve done it, we’ve come away with new ideas and fresh energy. We are convinced none of these creative ideas would have emerged without face-to-face discussion. There’s something about discussing the book in-person that brings new ideas and insights to light. Each time we meet in person, we discover a new angle or aspect of the book we are working on.
One of our many in-person working sessions at Neal’s house
Here are some examples of how our in-person meetings have significantly influenced our books:
When we were planning the first edition of Fundamentals of Software Architecture, we decided to create comparison charts rating the pros and cons of each of the architectural styles we were writing about, but struggled with getting the granularity right. After much frustration, we decided to meet in person and dedicate the time to the comparison charts, resulting in the final version of the well-known star-rating charts found in the book. It was this experience that convinced us that in-person meetings are an invaluable part of the success of a coauthored book.
While writing Software Architecture: The Hard Parts, we found ourselves struggling with how to contextualize each chapter’s topic. When we met in person, we came up with the idea of starting each chapter with dialogue showing a fictional team undergoing a large migration from a monolithic system to a distributed one.
When writing Head First Software Architecture, one of us was struggling with a particularly difficult chapter. After numerous virtual meetings full of suggestions and three revisions of the chapter, it still wasn’t quite right. It wasn’t until our in-person meeting that we all saw it—the chapter was literally upside down. We inverted the chapter to build up to the big picture rather than starting with the big picture, and the chapter became one of the best-written ones in the book.
We’re currently writing a book called Software Architecture Patterns, Antipatterns, and Pitfalls. We created a template for everything we wanted each pattern to cover, but it didn’t quite work for the chapters on antipatterns and pitfalls. Through all our weekly virtual calls and numerous side emails and texts, we simply couldn’t seem to get it right—something was missing. It wasn’t until our first in-person meeting that we found the solution: changing the generic section heading “Context” to a chapter-specific question that gets right at the point of the chapter and provides context for the antipattern.
However, that wasn’t the magical piece. Once we all saw how well this worked for the antipatterns and pitfalls, we decided to use this technique for all the chapters. Now each chapter of the book starts with a motivating question for why this pattern, contextualizing it for both the author and reader and making the table of contents more useful. We’re confident this simple piece of brilliance would never have happened through virtual meetings.
At that same meeting, we also worked on our other current project, Architecture as Code. We changed the order of the chapters to fit a better narrative arc as a result of an intensive in-person gathering. Without being in person and seeing the overall book flow together, the narrative arc would likely not have changed to the new and improved one.
If you’re coauthoring a book, we highly recommend having at least one in-person gathering, if logistics allow. The success of our books should be testimony enough that this technique works.
A study of 50,807 German health searches found Google’s AI Overviews cite YouTube more than any other site. The AI also pulls links beyond top results, so quick symptom answers can lean on lower-bar sources.
Most Excel sheets are dumb—they contain static text that has no connection to the real world, forcing you to manually update prices and stats by hand. Value tokens change that. These smart pills link your cells directly to live data from the web, turning a boring, stagnant grid into a professional, self-updating dashboard.
So you keep hearing about how Home Assistant is the ultimate smart home platform, but you still feel lost. Here are some burning questions you might need answered before you can take the next step.
Amazon Prime Video is wasting no time ushering in hit flicks. I, for one, appreciate the fresh rotation. This week, we’re closing out January with a wee bit of drama, thrills, and action, and then we’re strolling into February with an easy-going cult classic.
Login
