Magpie Log

Magpie Log

Archives
Log in
Subscribe
8 November 2026

The walls of text

Hi! I am sure you’ve also been in a situation where you are working on something with an LLM, and you get a wall of text to read. All you wanted to know was if your ideas and you were on the right track or if you missed something crucial. Whether it is worth pursuing or the clanker will give you an insight to make you rethink the hypothesis and start anew.

In all these cases, you get a wall of text to read first.

The problem is worse with code harnesses and, subsequently, with code. It used to be the case that while designing an architecture or a solution, you would first draw from your experience. You would consult your teammates and/or friends, read an article online and find that someone else had the exact same need. Mostly because software engineering problems are more common than one assumes. Then you write the limited number of things that you need in the moment and know about, and then you start the work.

Now, the know-it-all LLM takes every topic, every problem, every system, to its logical final/extreme state. Puts in everything. ‘Oh you need an auditable log for your app? Well, only a new table where you write a new entry for an action is too naive. How about you create a separate database with a separate db user, you know, so existing users couldn't access it. How about you create a new postgres instance altogether. Isolated, air gapped. Tack on 2-factor auth for access. Security, you know. How about you take daily backups in an S3 bucket - locked bucket even. How about you create a new application to see the dashboard of entries. Put 2-factor auth on that as well. Make it extendable, with plugins. How about you create a framework, for others, for the community. Open source it and provide AI services in a managed version of it. New business. More money. Did you think about that? Do you think this works? When do you need me to start the work on it. I can build the whole thing while you sleep. Just say the word. I'll spit out a million lines of code which you will never read.’

You get the point. 

Related to this, the other day I watched a video from an engineering channel about combined ‘code factories’. Where everyone from the team works on it together. How product owners have already started prompting features in some teams. Designers too, already change the visual look of the app. They submit a PR, tests pass, then auto-merge. Understandably for and engineering channel, he saw the question coming. 'What will the engineers do?' Well, ‘they will review the code to make sure things are right’, he said. The person wasn’t being sarcastic. He genuinely presented the inevitability of engineers reviewing code more than anything in this new normal. So that everyone prepare for this scenario.

Reading walls of code; besides reading walls of text. All the time.

I am tired of this.

I understand we are seeing tokens become commoditized now. There will always be cheap tokens from here on out. The question is: will one have time to consume it all?

You cannot go back to the old way. Mostly because you’ll expose yourself to vulnerabilities; and the fact that you will not build as much and therefore not have as much market share as others.

The only way forward looks like giving up; on reading large walls of text, and code, as others have. Letting the agent decide everything, and band-aiding things when they break.

Maybe we stop reading code and start reading fiction.


Book I want to read

Unequal Exchange, by Arghiri Emmanuel

Unequal Exchange by Arghiri Emmanuel | Goodreads

English, French (translation)

I discovered this from Barry’s economics (youtube) and even tough it is preaching to the choir kind of thing for me, I think everyone reads a book different and forms their own unique approach or stance. So goes this on my bookshelf.


Interesting reads

  1. Zen of Reticulum

  2. Norway promotes tourism with toilets

  3. *sshole


A project I discovered

Rebuilding the Internet for a Better World

PeerSky

A Local-First P2P Browser for desktop and mobile: Access, Communicate, and Publish Offline

I discovered Reticulum (article above) through this while on my quest to find different browsers available out there.


A photo I took

A building rises into the dark hazy sky. With a step ladder design of windows which glow from inside, the top of the building is engulfed in fog and is almost invisible. The far edges also seem to dissolve into the fog
Into the Haze

I made quite a few mistakes and was generally not happy with the text in last week’s newsletter. So I rewrote parts of it after the email was sent out. If you haven’t read it yet, and are interested, read it through this link instead of the email.

Until next week! 👋

Don't miss what's next. Subscribe to Magpie Log:
← Newer Do you recall your dreams? Older → On socialising, familiar and new
usaa.ma
Bluesky
Powered by Buttondown, the easiest way to start and grow your newsletter.