If you see this post, take a few minutes and listen to this song in silence. Itβs my churchβs favorite worship song.
O God Would You Move / Awake My Soul (Live) https://t.co/ANNkwO0nwW via @YouTube
Just watched my wife maneuver through 4 menu items to reset the trip odometer. Remember when you just had to push the mechanical reset on the actual gauge? Soon it will be a voice command ποΈ
If you're a developer moving back to the CLI with AI try CMUX, an open source native macOS terminal. Vertical tabs, notification rings when agents need attention, split panes, and a CLI for programmability.
https://t.co/WGLur87oEo
we will need to rebuild and rewrite much of software to adapt to a new, faster pace.
code used to arrive one drop at a time. soon, if not already, code will be written as if it were a continuous stream, like a violent river twisting and turning as it pleases.
this is not a new thing: big tech cos have had to deal with this with the enormous scale of their engineering teams. but now ai has brought an incredibly elastic and capable workforce wielded by every engineer. this is your problem now, and the only way to adapt is to evolve your systems so agents - even and especially the ones with little context about the right way of doing things - can thrive. make the easy thing the right thing.
your codebase is becoming organic architecture. agent contributions grow around the constraints and guardrails youβve designed. good software engineering matters even more now! and no, the continuous stream of code is not something you have to watch helplessly. be more ambitious and design systems, frameworks, and languages to control the chaos.
the time for mourning coding is long over