codeinabox

London based software development consultant

How Developers React to AI-Scented Blog Posts

21h 57m ago in Aii@programming.dev from writethatblog.substack.com

∪ of Target Audiences (Accessibility, SEO, AEO/GEO)

1d 13h ago in a11y@programming.dev from adrianroselli.com

The future of Siri, or: why private inference isn’t private enough

1d 22h ago in privacy@programming.dev from blog.cryptographyengineering.com

Agentic Code Review

2d 39m ago in aicoding@programming.dev from addyosmani.com

Appreciation for the small web

2d 1h ago in indieweb@programming.dev from jola.dev

Explaining Functional Programming to Non-Programmers (It's Just Excel)

2d 1h ago in functional_programming@programming.dev from cekrem.github.io

AI GPUs probably live longer than three years

2d 3h ago in Aii@programming.dev from www.seangoedecke.com

Progressively enhanced data-dense layout with grid-lanes

2d 7h ago in css@programming.dev from www.projectwallace.com

Software Is Not A Single-Player Game

2d 9h ago in programming@programming.dev from www.davidpoll.com

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.

There’s no need to include ‘navigation’ in your navigation labels

3d 1h ago in a11y@programming.dev from www.tempertemper.net

Simple Neovim autopairs

3d 3h ago in neovim@programming.dev from tduyng.com

Vibe Coding Is Dangerous, Agentic Engineering Isn't ft. Wes McKinney

5d 7h ago in aicoding@programming.dev from motherduck.com

Are you implying that Wes McKinney is also stupid, despite his open-source contributions?

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

9d 4h ago in programming@programming.dev from blog.herlein.com

Agile came from toyota?

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

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

19d 3h ago in programming@programming.dev from terriblesoftware.org

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

26d 7h ago in programming@programming.dev from a4al6a.substack.com

Could you elaborate on this?

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

AI coders are carrying half-open laptops through airports, offices, and ice rinks

1mon 5d ago in aicoding@programming.dev from www.businessinsider.com

This behaviour sounds a lot like addiction. It has been argued that AI coding tools may be triggering the same dopamine loops as slot machines.

Don't overestimate domain expertise

1mon 5d ago in programming@programming.dev from event-driven.io

An acronym for domain-driven design.

Planning to learn multiple languages and frameworks

1mon 6d ago in programming@programming.dev

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