Live data from Hacker News

How to effectively write quality code with AI

heidenstedt.org

171–180 of 321 posts

Re: How to effectively write quality code with AI

#171
post #116

The best thing about this is that AI bots will read, train on and digest the million "how to write with AI" posts that are being written right now by some of the smartest coders in the world and the next gen AI will incorporate all of this, making them ironically unnecessary.

Each extra generation of AI produced crap AI consumes as training, the worse it gets. This has been mathematically proven.

Re: How to effectively write quality code with AI

#172

Earlier quoted context omitted.

Where is all the amazing software and/or improvements in software quality that is supposed to be coming from this revolution? So far the only output is the "How I use AI blogs", AI marketing blogs, more CVEs, more outages, degraded software quality, and not much of shipping anything. Is there any examples of real products and not just anecdotes of "I'm 10x more productive!"?

Sounds like a skill issue. I’ve seen it rapidly increase the speed of delivery in my shop.

[deleted]

Re: How to effectively write quality code with AI

#173

Earlier quoted context omitted.

Where is all the amazing software and/or improvements in software quality that is supposed to be coming from this revolution? So far the only output is the "How I use AI blogs", AI marketing blogs, more CVEs, more outages, degraded software quality, and not much of shipping anything. Is there any examples of real products and not just anecdotes of "I'm 10x more productive!"?

Sounds like a skill issue. I’ve seen it rapidly increase the speed of delivery in my shop.

[deleted]

Re: How to effectively write quality code with AI

#174

Earlier quoted context omitted.

Where is all the amazing software and/or improvements in software quality that is supposed to be coming from this revolution? So far the only output is the "How I use AI blogs", AI marketing blogs, more CVEs, more outages, degraded software quality, and not much of shipping anything. Is there any examples of real products and not just anecdotes of "I'm 10x more productive!"?

Sounds like a skill issue. I’ve seen it rapidly increase the speed of delivery in my shop.

[deleted]

Re: How to effectively write quality code with AI

#175

Earlier quoted context omitted.

Where is all the amazing software and/or improvements in software quality that is supposed to be coming from this revolution? So far the only output is the "How I use AI blogs", AI marketing blogs, more CVEs, more outages, degraded software quality, and not much of shipping anything. Is there any examples of real products and not just anecdotes of "I'm 10x more productive!"?

Sounds like a skill issue. I’ve seen it rapidly increase the speed of delivery in my shop.

[deleted]

Re: How to effectively write quality code with AI

#176

I wonder at the end of this if it's the still worth the risk? A lot of how I form my thoughts is driven by writing code, and seeing it on screen, running into its limitations. Maybe it's the kind of work I'm doing, or maybe I just suck, but the code to me is a forcing mechanism into ironing out the details, and I don't get that when I'm writing a specification.

>but the code to me is a forcing mechanism into ironing out the details, and I don't get that when I'm writing a specification.

This is so on point. The spec as code people try again and again. But reality always punches holes in their spec.

A spec that wasn't exercised in code, is like a drawing of a car, no matter how detailed that drawing is, you can't drive it, and it hides 90% of the complexity.

To me the value of LLMs is not so much in the code they write. They're usually to verbose, start building weird things when you don't constantly micromanage them.

But you can ask very broad questions, iteratively refine the answer, critique what you don't like. They're good as a sounding board.

Re: How to effectively write quality code with AI

#177
post #112

The post touches very briefly on linting in 7. For me, setting up a large number of static code analysis checks has had the highest impact on code quality. My hierarchy of static analysis looks like this (hierarchy below is Typescript focused but in principle translatable to other languages): 1. Typesafe compiler (tsc) 2. Basic lint rules (eslint) 3. Cyclomatic complexity rules (eslint, sonarjs) 4. Max line length en…

My setup has some of the things mentioned and I found that occasionally the LLM will lie that something passes, when it doesn't.

If you're using Claude try the hookify plugin and ask if to block commits unless the rules pass.

Re: How to effectively write quality code with AI

#178

Earlier quoted context omitted.

Yep, its a rather depressing realization isnt it. Oh well, life moves on i suppose. I think we realistically have a few years of runway left though. Adoption is always slow outside of the far right of the bell curve.

i'm sorry if I pulled everybody down .. but it's been many months since gemini and claude became solid tools, and regularly i have this strong gut feeling. i tried reevaluating my perception of my work, goals, value .. but i keep going back to nope.

I hear you. And maybe you're right. Maybe I'm deluding myself, but: when I look at my skilled colleagues who vibecode, I can't understand how this is sustainable. They're smart people, but they've clearly turned off. They can't answer non-trivial questions about the details of the stuff they (vibe-)delivered without asking the LLM that wrote it. Whoever uses the code downstream aren't gonna stand (or pay!) for this long-term! And the skills of the (vibe-)authors will rapidly disappear.

Maybe I'm just as naive as those who said that photographs lack the soul of paintings. But I'm not 100% convinced we're done for yet, if what you're actually selling is thinking, reasoning and understanding.

Re: How to effectively write quality code with AI

#179
post #121

Earlier quoted context omitted.

Alternatively, another second order effect is can't sip latte anymore because you're orchestrating 8 bots do the work and you're back to 80%-100% time saturation.

The previous second order effect is more likely. For the one orchestrating 8 bots, 7 others are not needed anymore.

Or, there is just a lot more software written as the costs drop. I think most people work with software not tailored enough for their situation..
Post reply on HN