AI won’t replace software engineering, it changes the economics of writing code. But prompts aren’t enough.
To safely guide AI agents, we need executable specifications. Discover why Acceptance Test-Driven Development (ATDD) is the future of AI coding.
📽️ (link in bio)
Why do so many software engineering teams see their development speed slow to a crawl? In this week's video, I explore the single biggest challenge in modern software engineering and programming: coupling.
Now on @ModernSoftwareX
📽️ (link in bio)
The greatest thing about adding a dependency to a project is removing it when you realize life is simpler without it.
I added one in yesterday, started using it and then today, I reverted 2 commits and removed the dependency.
It's feels just like losing weight.
there's this valley of despair when programming with agents
you either have to be an inference maximalist or minimalist, but anywhere in between you just get slop and pain
Not arguing that it’s not „not accurately covered“, but there isn’t nothing, so the DDR comparison doesn’t hold imo:
The BBC topic page for „child grooming“ has over 20 result pages:
https://t.co/Iu34OuGbtr
This report stating „… there was growing evidence from the early 2000s that gangs of predominantly Asian men were grooming, trafficking and sexually abusing mostly white working-class girls in the town“ is from April 2022:
https://t.co/3hFvAfXBjE
What once began as a noble experiment in forming a digital currency unencumbered by financial institutions, cryptocurrencies have proven to be an abject failure by every measure.
There are on the order of only 30 million bitcoin wallets whose value is greater than $100 US; this represents at best about 0.36% of the world’s population, hardly a sufficient number to provide a global medium of exchange. While there certainly exist some fringe cases of utility, most notably by individuals needing to transport value outside dictatorial countries with broken and oppressive economies, cryptocurrencies are largely an object of speculation, driven by market manipulation and the economy of the greater fool and favored by criminal organizations and countries such as Russia and North Korea seeking to avoid sanctions. The ancillary industries spawned by cryptocurrencies – NFT and DeFi and so-called Web3 - never gained traction, and indeed proved to enrich a small few at the expense of the many.
At the start of this technology, I was curious and hopeful, but it is clear that human greed has irredeemably ruined it for all.
I've been thinking a lot about this.
Some loose thoughts, on what I think contributes to the (perceived) lack of new businesses and software.
1.) AI is very unlike previous technology revolutions in one way: it's a text field that scales with your ambitions. If you don't know what to put in the text field, you won't get a lot out of it. And it's hard to know what to put in there.
Imagine if Cloud computing had been rolled out via a freeform text field in which you can type your wishes and people give you examples of text that worked for them. This matters a lot for adoption and diffusion of new technology.
2.) Knowledge about how to use AI compounds in strange ways. A friend of mine worked in a German non-tech company in sales when they rolled out AI, a 1.5 years ago: "courses" for AI, free ChatGPT accounts, prompt engineering, "You are a senior marketing leader creating the yearly presentation..." 95% of what they learned is now useless.
My own knowledge has grown, but it feels less like technical knowledge, more like instinct: pattern recognition, knowing when to take hands off the wheel, when to put them on again, when to restart, when to change approaches and prompts, ... How do you package and teach that to a whole company that's non-technical? Big effect on adoption.
3.) AI also changed what software gets shared. Why share something that barely cost you any effort and that took 5min? I can only speak for myself, but a lot of code that I previously shared online, I shared not necessarily because it was useful, but because I was proud of it: I learned a lot building it, I spent a lot of time on it, I tweaked it, I polished it. I shared because I wanted to say "I made this." I don't have that feeling when I prompt something into existence in 5min.
4.) At the same time, let's call it: it's unclear what software is worth building anymore.
When mobile happened, the app stores were full of tiny apps. People made money with them. Now, with AI, building tiny apps seems not worth the effort. Or B2B SaaS: it's not clear yet where we all will end up on build-vs-buy, but it's clear the tradeoffs have changed.
5.) Then there's this other tectonic plate moving: the models have been getting better, consistently. So even if you think "it's worth building this piece of software, because the models can't do this" — are you sure that's still the case in 6 months?
6.) Combine that and, well, I don't know how to better put it than: software to do x isn't valuable anymore, when you can get a model/agent to do x.
Take one of the most famous examples of indie hacker success: patio11's Bingo Card Creator, a website that lets you create bingo cards. Technically not that hard, but valuable to those who want to do x: create bingo cards. But now? I'm sure I can use ChatGPT, or Gemini, or Claude and they can create me bingo cards on demand. There might still be value in BCC as a piece of software (I haven't looked at it in a while), but my point is that it's very hard to know what software will be valuable, because "this software allows you to do x" isn't as valuable as it was 10 years ago.
7.) On top of all of that, adoption is jagged, in a very very strange way: the people who are maybe the least likely to appreciate the value of AI adopted it first.
Where AI works the best, by far, is software development. And who adopted it there first? People who are interested and passionate about software. But AI's progress shows us more than ever that software's value was never the software itself — it's the business outcomes it enables. Now, who's least likely to appreciate that? People who really valued software for being great software, regardless of business utility.
8.) In some sense, the ultimate user of AI is a founder or CEO: someone who wants to achieve business results and sees software as purely a means to an end. But the group that adopted it first has a lot of people who care more about the software than the business outcome. The ultimate user of AI might not be the person who loves making software. It might be the person who wants the result software used to produce.
This is a very interesting time to be in software.
Hey @github, I am begging you to implement `gh auth login --secure-enclave` (we can workshop the name). It’s no panacea but it would really help with the harvesting malware flying around!
just never forget that the devs who yap about AI being the best thing ever all day never really knew how to program well to begin with.
They are idiots telling you that the world is solved (charitable read) or worse, they are selling you something and are attempt to deceive you.
This is why we see the same cycle every time. Opus 4 = God's gift to humanity to OMG its utter trash within a few months. The same thing happens with every model release because these people don't even know what dev is. They are larpers.
I believe this is what Geohotz meant when he: "I’m calling it now, the adoption of AI agents into software development will be one of the most costly mistakes in the field’s history."
Twenty years ago, after joining Google, I published my old Amazon internal "drunken" blog rants all at once, almost fifty of them. They went super viral and led to me getting famous almost overnight, though nothing compared to five years later with the Platforms Rant. (When the Platforms Rant was making the rounds, my buddy Andrey Gubarev told me he'd just gone to visit his parents in Northern Siberia, and they only knew two things about Google, and I was one of them.)
But for the time, in 2006, my Drunken Blog Rants made a big splash.
To my lasting regret, @Werner made me take the best one down, six days after posting, because he felt it exposed too much proprietary Amazon information. And I complied, because he had asked soooo nicely, unlike their Head Legal Counsel who threatened to personally chew my balls off if I so much as hinted at recruitiing anyone from Amazon to Google.
Well, twenty years later, I went looking for it, and of course, Fable found it for me in an old zipfile inside another zipfile in Google Cloud Storage inside a CVS repository whose Attic happened to have a copy of every single original Amazon blog rant.
Look what they did to my boy Fable. That was uncalled for.
I re-read the post 20 years later, and it really was the best one. The world might have had GraphQL years earlier if they'd been able to read it. The post lays out with memorable examples exactly why Amazon needed something like GraphQL, even calling it a query language.
The article does expose a lot about how Amazon's databases and service APIs worked back in 2004, so it was reasonable to take it down. But had I known better, I would have just edited it.
The essay: https://t.co/3k93BOF8cB
System packages in mise: define apt/brew/dnf/pacman dependencies in mise.toml. In the case of brew, you don't actually need the brew cli installed so you could bootstrap a machine with mise only.
https://t.co/rnG5Nn6tFW