> What I wanted was to say “hey Siri, call Claw Phone” and have the audio system in my Toyota become an IDE. So I build it.
Or just focus on driving? Why we are doing it to ourselves? It seems so toxic to fill every possible little moment with… productivity? Is it even productive?
This comment is too emotional but i just felt so sad while reading this
show comments
cevn
> I didn’t build Twilio. I didn’t build the Realtime API. I didn’t build Claude Code or MCP.
I didn't write a blog post.
show comments
cloche
I get that many people are tired of too many AI posts and there's an influx of negative comments but I think this is genuinely amazing. Think about watching Star Trek in the 60s and seeing people talk to computers and them understanding and being able to communicate back. We're literally living in the future!
zahlman
The best time to solve personal problems with those techniques, perhaps. That is not the same as (and might be opposed to) the best time to seek employment or go into business using those techniques; there isn't going to be much of a market for things that your (employer's) potential customers could trivially do themselves.
show comments
MeetingsBrowser
I see this sentiment constantly. AI tooling is better than ever and its making building things easier than ever. I have respected coworkers who say that are maxing out multiple $200/month subscriptions.
But I have yet to see any results? Where is the useful stuff?
show comments
Schiendelman
This is just an advertisement, it's not about being a "duct tape engineer", and the various coding agents are already great duct tape engineers, so I can't imagine someone writing a compelling blog post about it anyway.
show comments
mrbonner
This has been the the case all the time: most of our work are connecting pipes using glue code/duct tape so to speak. But now, we are delegating this to AI. Nothing new for me.
heohk
All modern SaaS is just other SaaS glued together
tired_and_awake
I feel as if a lot of this what Google home (or other "home like" products) could have been and they have failed miserably. As a Google home user I find it can't answer the simplest questions that would require even the hint of an integration within Google's own ecosystem.
f311a
I hope he does not use it and just wanted to advertise his project to get some Github stars...
axegon_
The good times are yet to come though: when all the slop held together by spaghetti, duct tape, chewing gum and hairballs starts falling apart and someone needs to fix it. If the slop bubble doesn't start popping soon, in 10 years a handful of people will end up being better paid than COBOL developers are now cause they'd be the only one that know what a compiler is. Personally I'm not too enthusiastic about the prospect so if I'm lucky, I'll be enjoying early retirement and watching all hell break loose from a camper van near the sea somewhere.
show comments
Hugsbox
And when you get home to check out the results, you won't understand any of the code :)
jupr
This is a completely insane way to check how many emails I have in my inbox I love it.
j45
It's the spaghetti code years all over again but with ai. :)
bluefirebrand
I tend to call this sort of "I glued a bunch of external services together to make a useful tool" Software Plumbing, not Engineering.
Anyways I think what you've demonstrated that it's actually a really bad time to be a "Duct Tape Engineer" because anyone with a bit of knowhow can coax the AI to build them some pile of loose data pipes and leaky abstractions that appears useful. The market for this sort of software builder is about to get very crowded
> What I wanted was to say “hey Siri, call Claw Phone” and have the audio system in my Toyota become an IDE. So I build it.
Or just focus on driving? Why we are doing it to ourselves? It seems so toxic to fill every possible little moment with… productivity? Is it even productive?
This comment is too emotional but i just felt so sad while reading this
> I didn’t build Twilio. I didn’t build the Realtime API. I didn’t build Claude Code or MCP.
I didn't write a blog post.
I get that many people are tired of too many AI posts and there's an influx of negative comments but I think this is genuinely amazing. Think about watching Star Trek in the 60s and seeing people talk to computers and them understanding and being able to communicate back. We're literally living in the future!
The best time to solve personal problems with those techniques, perhaps. That is not the same as (and might be opposed to) the best time to seek employment or go into business using those techniques; there isn't going to be much of a market for things that your (employer's) potential customers could trivially do themselves.
I see this sentiment constantly. AI tooling is better than ever and its making building things easier than ever. I have respected coworkers who say that are maxing out multiple $200/month subscriptions.
But I have yet to see any results? Where is the useful stuff?
This is just an advertisement, it's not about being a "duct tape engineer", and the various coding agents are already great duct tape engineers, so I can't imagine someone writing a compelling blog post about it anyway.
This has been the the case all the time: most of our work are connecting pipes using glue code/duct tape so to speak. But now, we are delegating this to AI. Nothing new for me.
All modern SaaS is just other SaaS glued together
I feel as if a lot of this what Google home (or other "home like" products) could have been and they have failed miserably. As a Google home user I find it can't answer the simplest questions that would require even the hint of an integration within Google's own ecosystem.
I hope he does not use it and just wanted to advertise his project to get some Github stars...
The good times are yet to come though: when all the slop held together by spaghetti, duct tape, chewing gum and hairballs starts falling apart and someone needs to fix it. If the slop bubble doesn't start popping soon, in 10 years a handful of people will end up being better paid than COBOL developers are now cause they'd be the only one that know what a compiler is. Personally I'm not too enthusiastic about the prospect so if I'm lucky, I'll be enjoying early retirement and watching all hell break loose from a camper van near the sea somewhere.
And when you get home to check out the results, you won't understand any of the code :)
This is a completely insane way to check how many emails I have in my inbox I love it.
It's the spaghetti code years all over again but with ai. :)
I tend to call this sort of "I glued a bunch of external services together to make a useful tool" Software Plumbing, not Engineering.
Anyways I think what you've demonstrated that it's actually a really bad time to be a "Duct Tape Engineer" because anyone with a bit of knowhow can coax the AI to build them some pile of loose data pipes and leaky abstractions that appears useful. The market for this sort of software builder is about to get very crowded