Skip Navigation

codeinabox

@ codeinabox @programming.dev

Posts
322
Comments
75
Joined
10 mo. ago

London based software development consultant

  • The Bosses Are Coding Again

    Jump

  • Could you qualify what you mean by "idiots"? The author and the examples he gives - Kent Beck, David Heinemeier Hansson, and Garry Tan - are all very experienced software engineers.

  • D is on the way of getting an AI slop standard library, for no good reason

    Jump

  • Funnily enough, Lemmy does allow AI-assisted code contributions, though they're not encouraged. This is mentioned in the code of conduct:

    Use of so-called Artificial Intelligence (AI) is allowed only if it is explicitly mentioned. Additionally all LLM-generated text or code must be manually reviewed by the author before submission (no vibe coding allowed).

  • Taste Is in the Spec (Cooking Is Not the Recipe)

    Jump

  • This article is not advocating AI driven development. It's arguing a human understanding the problem, and how best to solve it, is the most important work.

    I’m not anti-spec. Far from it. I think rigorous, well-structured specs are about to be the single most important artifact in software. Read the book. Adopt the format. Use the tools. The mechanics matter and I’m not waving them away.

    But the spec is a vessel. The recipe is not the cooking. If we pour mediocre understanding into a perfectly-formatted spec, we get perfectly-formatted slop, faster and at scale. The format is necessary. It is nowhere near sufficient.

    The real work - the part no tool will do for you - is the human work of digging in. Of actually understanding the problem and the person you’re solving it for, deeply enough to have an opinion about what right feels like. Of capturing not just the requirements but the taste. The why. The elegance. The exact sweet spot of how it should work.

  • Software Is Not A Single-Player Game

    Jump

  • I agree that the AI generated image is trashy, however the article is a cautionary tale about the pitfalls of relying on agentic coding, instead of collaborating with other developers.

    But there is always a ceiling on how far a single-player game can take you, even with agents. Software that lasts, software that grows, software that people can actually depend on – that is built by groups of people exercising judgment together over time. By teams developing shared taste, shared mental models, shared sense of what their product should be. None of that happens through individual prompting, no matter how clever the prompts.

  • Is Waterfall Coming Back? Sort Of. Not Really. Both — And the Bigger Question Underneath.

    Jump

  • Agile came from toyota?

    My understanding is that Kanban came from Toyota, which is an agile way of working.

  • Is Waterfall Coming Back? Sort Of. Not Really. Both — And the Bigger Question Underneath.

    Jump

  • This is a fascinating article about the history of software development. For me the key quotes are:

    The thing that killed Waterfall was that discovering your spec was wrong months later, after lots of code had been written - and fixing it cost a fortune because writing code was the most expensive part of the process.

    The key reason Agile was invented was to account for the high cost of writing code, so yes, that part of the Agile value proposition is no more.

    The risk isn’t that AI development is inherently Waterfall. The risk is that organizations with latent Waterfall instincts will use spec-generation as license to do the bad thing they always wanted to do — front-load requirements, skip customer validation, equate a fancier document with a better outcome, and ship one massive thing every quarter.

  • Using My Fucking Brain

    Jump

  • This quote from the article really sums it up:

    And to be clear, I don’t care whether you typed the code yourself. I care whether you understood it before you shipped it. I care whether you can explain why the bug happened, why this fix is the right fix, what the model might have missed, and what would make you roll it back.

  • Stop Using Pull Requests

    Jump

  • Could you elaborate on this?

  • Stop Using Pull Requests

    Jump

  • Thank you! I've updated the post with the TL;DR from the article.

  • Don't overestimate domain expertise

    Jump

  • Planning to learn multiple languages and frameworks

    Jump

  • Depending on your level of programming experience, you might find the exercises at Exercism quite useful.

  • You can save at least 40% by externalizing the CSS

    Jump

  • Open source Vercel alternatives?

    Jump

  • Could you give more context about what Vercel features you need - is the site statically generated, or do you also need Vercel Functions?

  • Open source Vercel alternatives?

    Jump

  • Claude Code Found a Linux Vulnerability Hidden for 23 Years

    Jump

  • Though that quote is followed by this, which indicates at least five of those vulnerabilities were real:

    I searched the Linux kernel and found a total of five Linux vulnerabilities so far that Nicholas either fixed directly or reported to the Linux kernel maintainers, some as recently as last week:

  • Your Engineers Aren't Lazy, Your Codebase Is Punishing Them

    Jump

  • Your comment reminded me of this article, The Software Quality and Productivity Crisis Executives Won’t Address, which discusses the lack of technical leadership when it comes to tackling technical debt, and that the solution is usually a rewrite.

    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 (Oliver Wyman, 2024).

  • Agentic slop PRs

    Jump

  • I have noticed the repository lacks CONTRIBUTING.md. If you want to set some rules about contributing, I would have added them there, instead of creating a Markdown file specific for agents. I'm very much of the philosophy that you should write documentation for humans, which has the added bonus that it will also be consumed by agents.

  • Code Review Is Not About Catching Bugs

    Jump

  • I agree but it depends on how teams create and refine their tickets. For example, you could have high level tickets, and someone picks one up and creates an implementation that's not an appropriate fit for your architecture.

  • The diminished art of coding

    Jump

  • Thank you for not assuming my motivations. Could you please elaborate on what you mean by "oneshotted"? I share a lot of articles, so I'm not surprised you recognise my username.