Instance: programming.dev
Joined: 4 months ago
Posts: 128
Comments: 8
London based software development consultant
Posts and Comments by codeinabox, codeinabox@programming.dev
Comments by codeinabox, codeinabox@programming.dev
Instead, most organisations don’t tackle technical debt until it causes an operational meltdown. At that point, they end up allocating 30–40% of their budget to massive emergency transformation programmes—double the recommended preventive investment.
I can very much relate to this statement. Many contracts I’ve worked on in the last few years, have been transformation programmes, where an existing product is rewritten and replatformed, often because of the level of tech debt in the legacy system.
I originally shared this after stumbling upon it in one of Martin Fowler’s posts.
The article reminds me of how my mother used to buy dress patterns, blueprints if you will, for making her own clothes. This no code library is much the same, because it offers blueprints if you wanted to build your own implementation.
So the thing that interests me is what has more value - the code or the specifications? You could argue in this age of AI assisted coding that code is cheap but business requirements still involve a lot of effort and research.
To give a non-coding example, I’ve been wanting to get some cupboards built, and every time I contact a carpenter about this, it’s quite expensive to get something bespoke made. However, if I could buy blueprints that I could tweak, then in theory, I could get a handyman to build it for a lower cost.
This is a very roundabout way of saying I do think there are some scenarios where the specifications would be more beneficial than the implementation.
Thank you everyone for your input. I have created a separate community, !aicoding@programming.dev, for AI coding related discussions.
I agree with you on that point, and the same could be said about the meat and dairy industry. However I don’t think the answer is censoring discussions about cooking beef or chicken.
You can’t compare racist posts, which are a form of hate speech and a breach of this instance’s code of conduct, with discussions about topics that you don’t agree with.
Good question. I have asked this very question https://programming.dev/post/45013854
Expensive as hell! 🤑
Yegge describes Gas Town as “expensive as hell… you won’t like Gas Town if you ever have to think, even for a moment, about where money comes from.” He’s on his second Claude account to get around Anthropic’s spending limits.
I can’t find any mention online of the per-account limits, but let’s conservatively assume he’s spending at least $2,000 USD per month, and liberally $5,000.
I am not surprised that there are parallels between vibe coding and gambling:
With vibe coding, people often report not realizing until hours, weeks, or even months later whether the code produced is any good. They find new bugs or they can’t make simple modifications; the program crashes in unexpected ways. Moreover, the signs of how hard the AI coding agent is working and the quantities of code produced often seem like short-term indicators of productivity. These can trigger the same feelings as the celebratory noises from the multiline slot machine.

c/Aii
I can very much relate to this statement. Many contracts I’ve worked on in the last few years, have been transformation programmes, where an existing product is rewritten and replatformed, often because of the level of tech debt in the legacy system.
The Software Quality and Productivity Crisis Executives Won’t Address (flowchainsensei.wordpress.com)
I originally shared this after stumbling upon it in one of Martin Fowler’s posts.
The article reminds me of how my mother used to buy dress patterns, blueprints if you will, for making her own clothes. This no code library is much the same, because it offers blueprints if you wanted to build your own implementation.
So the thing that interests me is what has more value - the code or the specifications? You could argue in this age of AI assisted coding that code is cheap but business requirements still involve a lot of effort and research.
To give a non-coding example, I’ve been wanting to get some cupboards built, and every time I contact a carpenter about this, it’s quite expensive to get something bespoke made. However, if I could buy blueprints that I could tweak, then in theory, I could get a handyman to build it for a lower cost.
This is a very roundabout way of saying I do think there are some scenarios where the specifications would be more beneficial than the implementation.
How much "boilerplate tax" different languages have: a 400M LOC analysis (boyter.org)
Comments
The Browser Hates Surprises (frontendmasters.com)
A Software Library with No Code (dbreunig.com)
Vibe Coding Kills Open Source (arxiv.org)
Comments
On craft and AI (slightknack.dev)
Comments
Tactical tornado is the new default (olano.dev)
Trust signals are broken (ordep.dev)
EU Open Source Policy Feedback (socialwebfoundation.org)
Try text scaling support in Chrome Canary (joshtumath.uk)
Nice Select (nerdy.dev)
AI Slopageddon and the OSS Maintainers (redmonk.com)
Performance-Optimized Video Embeds with Zero JavaScript (frontendmasters.com)
Thank you everyone for your input. I have created a separate community, !aicoding@programming.dev, for AI coding related discussions.
Explicit resource management in JavaScript (allthingssmitty.com)
Forget technical debt (ufried.com)
To be clear: I do not think we should actually forget technical debt. Also, this is not the nth post discussing if “debt” is an appropriate metaphor. I do not have a strong opinion regarding the metaphor. My point is rather that I realized in a recent discussion that in the end, it is not so much about technical debt but rather about something else, and I wanted to share the thought.
QuitGPT — OpenAI Execs are Trump's Biggest Donors (quitgpt.org)
I agree with you on that point, and the same could be said about the meat and dairy industry. However I don’t think the answer is censoring discussions about cooking beef or chicken.