Esa-Matti Suuronen retweeted
I really believed a whole generation of developers, who only know open source from npm and pypi, miss how open source actually used to work.
When Debian or a Linux distribution ships a dependency they take responsibility of it. If there is a security issue and it’s not fixed by the developer upstream, they fix it for their users.
Debian and others basically vendor every thing they distribute. They honor the license and they maintain patches. Most of the stuff that you get from your Linux distribution is basically a (small) fork.
The same is true for Apple, Microsoft and others. The open source software they ship, they carry that responsibility.
That doesn’t mean that security fixes are not upstreamed, but Apple or Debian or anyone else won’t jump in Twitter to shame a developer into compliance with their ways. They are not dependent on the health of a packaging infrastructure. They own their software including all the things it depends on.
I want that thinking back. Because it fundamentally makes people feel more responsibility and it shares the burden of issues. It also does not put so much focus and attention on the one overworked developer who just happened to have too much of the world depend on their library. Remember: they carry a responsibility they never signed up to and they never got compensated for.
Hey @zeddotdev, the new parallel agents feature is awesome!
Is there a way to see what worktrees I have actually open? I can find only a list of all worktrees. I have sometimes trouble finding my active trees
46
This is the best article I've read about the shift AI is causing in software development. Long but highly recommend reading:
modular.com/blog/the-claude-…
74
Esa-Matti Suuronen retweeted
Software engineers: Context switching kills productivity.
Also software engineers: I'm now managing 19 AI agents and doing 1800 commits a day.
We’ve spent years complaining that managers who expect a quick 5-minute chat ruin our focus for the next hour. But a ping from an agent every few minutes, that’s ok?
We celebrated Paul Graham’s essay “Maker’s Schedule, Manager’s Schedule” in which he argued:
“When you're operating on the maker's schedule, meetings are a disaster. A single meeting can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in.”
Now we see software engineers claiming huge productivity gains from hordes of AI agents, celebrating thousands of commits per day from their 19 agents.
Either context switching was never really the problem, and we oversold our need for deep focus. Or we're not actually reviewing 1800 commits a day.
If we couldn't context switch before, we're not managing 19 agents. We're blindly trusting them.
That’s not engineering, it’s gambling.
I really like this take. Something I've observed as well but not being able to put in words. Velocity of LLM based coding is like a drug but might not be good for the end result, or you for that matter.
A few things I've noticed as all devs write code with AI.
When you write foundational / architectural code of a new project by hand, you "feel" the code pushing back if your abstraction isn't right. You feel when something is harder than it should be. The code is telling you it's not in the right shape. Good engineers are sensitive to this.
When you're using an LLM, you keep pushing right through this in a way that feels like you're making progress, and it may even be directionally correct in a sense, but the underlying foundation of it all is actually bad in a way that either kills progress of the LLM later as it buckles under the complexity it has created or destroys your ability to maintain the code long term.
Related to this, I see a general restlessness with just sitting and thinking about a problem for a while.
As I've been working on a new library here at Laravel, there have been days where it feels like I mainly just stare at my screen thinking about something. When Claude Code is at your fingertips, it's tempting to just start yapping into the terminal and watching code come out the other end. Again, directionally correct in some ways, but often doesn't land on the elegant solution that is waiting to be discovered.
1
96
Esa-Matti Suuronen retweeted
Replying to @htmx_org
I still balance my checkbook and keep track of all my personal finances using software I wrote in 1985. Blue background looks better, though, will change that.
Esa-Matti Suuronen retweeted
Here's my favourite method for getting Go/Zig/Rust-like errors in TS.
It's by returning custom errors from functions.
- Shows right in the return type
- Easy checking with instanceof
- No deps required
Second day in Torino for #WCEU, setting up the @findkitcom booth, some pizza and even some coding: Made a Findkit powered search for the conference site 😁 #WCEU2024
1
4
254
Esa-Matti Suuronen retweeted
Replying to @firt
Remember Page Transitions introduced in #IE 5.5? Finally that they are coming back after 24 years! simplehtmlguide.com/pagetran…
This is what I want the most from AI assistants in the near future for sure. Would be so nice quality of life improvement as a dev. Can't be too far off now.
Replying to @adamwathan
"Here's 3 commits where you can see me updating a few components by hand, and here's the documentation for the new library. Please apply this same type of change in a contextually accurate way for my other 197 components and commit it to a branch I can review."
Is that real?
211
Also bucket names are global so it is very easy to guess a reserved one.
Better to always add some randomness to the names.
Ok, this is bonkers... S3 charges you for unauthorized requests 🤯 so someone can DDOS you by making unauthorized to your private bucket!
All it takes is for them to guess your bucket name 🤦♂️
medium.com/@maciej.pocwierz/…
138
Haha, I might actually some day migrate to ESM
Replying to @JoyeeCheung
Also, I wrote a bit about my understanding on why this took ~5 years more than it should have : joyeecheung.github.io/blog/2…
Esa-Matti Suuronen retweeted
Also, I wrote a bit about my understanding on why this took ~5 years more than it should have : joyeecheung.github.io/blog/2…
AWS just dropped new QuickJS based #Javascript runtime "LLRT" aka Low Latency Runtime written in #Rust with partial Node.js API support.
Tried to migrate to @vite_js in @remix_run but failed miserably. It does not seem to like @pnpmjs monorepos with CJS 😬
Could not figure workaround for the "exports is not defined" error
I think my ESM avoidance is coming to an end... 😅
129
and CSS has been getting new existing features faster than ever. Truly a weird move.
still insane to me that @digitalocean bought @css tricks and did nothing with it, no new content since April 2023, nada
138



















