Live data from Hacker News

Using AI to write better code more slowly

nolanlawson.com

451–460 of 511 posts

Re: Using AI to write better code more slowly

#451
post #159

Another day, another AI-related thinkpiece (that people upvote to post their own thinkpieces in the comments)

This is the HN way. Never is there actual discussion about the contents of an article. Instead, a Hacker News will read the headline and will write a diary post in the comments.

Re: Using AI to write better code more slowly

#452
post #414
post #220

Earlier quoted context omitted.

Nap while you can. The baseline is slowly raising; AI fed with organization context will hunt you down and lay you off, as it has done at multiple companies this spring already.

I mean, I didn't read it as a joke. Taking a rest can lead to a clearer ability to think... thereby being more productive, not less.

For the record I took it 100% seriously, having been wfh since covid I’ve taken more than one nap during ‘work hours’ myself… I’m saying ‘spin up an agent and go for a long walk’ being ok is close to over and it’s over in some companies already - and it isn’t because they’re monitoring what you’re doing, it’s that they know what is possible from those few folks who don’t go for walks and spin up more agents instead.

Re: Using AI to write better code more slowly

#453

Earlier quoted context omitted.

[flagged]

What an arrogant comment. You have no idea what kind of software the parent commenter is working on. If you think all software can be handled by AI then I'm afraid you're the one who doesn't know what they're doing.

People come up with excuses all the time trying to claim their special little project won’t work with AI. Ohhh there’s no training data. Ohh there’s no manual. Oh no digital instructions. Always turns out to be a user issue. People make these claims because they want to feel special. They want to believe no one else can do their job.

Re: Using AI to write better code more slowly

#455

I find myself spending on average more time in LLM review/resolution loops than it would take for me to write the code by hand. Partially because once I'm in the flow I write very very quickly and the code pours out sometimes faster than I can write. But also because the LLM code on the first few tries is generally really really bad. What I find interesting though is that spending the time to personally review and di…

It’s weird how insecure people are on HN that they need to downvote and flag comments when their feelings are upset. Instead of learning and accepting that they are wrong and there is room for improvement. They close their eyes plug their eyes and scream until the comments are flagged.

Re: Using AI to write better code more slowly

#458

As a junior, i do actually enjoy going back and forth with the AI discussing different ways to implement something and exploring alternatives. More often than not, I'd have an architectural idea that I'm not that confident in. The process of talking with the LLM takes a long time but it helps me sharpen the initial approach or even come up with a new one depending on the requirements.

Yes agreed with you on this.

Re: Using AI to write better code more slowly

#459

Earlier quoted context omitted.

I follow the same process. I have a design in mind for the problem at hand, but I don't reveal it to Codex. I go back and forth a bit to see if its proposals are better than mine. I go back and forth on tradeoffs of various approaches. And then I ask it to compare its proposals with mine. I "win" most of the time but there are many times where it shows a me a better, or simpler approach, or makes me rethink the solut…

I really like this pattern and use it often, this 'not showing my cards'. The second I hint towards the LLM what I prefer it will become sycophantic and invent nonsense why my preferred solution is better. I'm sure there's an interesting study on how users 'leak' their preference unintentionally to the LLM; perhaps when users list their options, they often put their prefered option first; but not showing the cards on…

There's an easy workaround that helps instead of listing options, just describe the problem constraints and ask it to propose approaches independently.

Re: Using AI to write better code more slowly

#460
post #400

As a junior, i do actually enjoy going back and forth with the AI discussing different ways to implement something and exploring alternatives. More often than not, I'd have an architectural idea that I'm not that confident in. The process of talking with the LLM takes a long time but it helps me sharpen the initial approach or even come up with a new one depending on the requirements.

Be sure to explicitly ask for critiques or alternatives. In my experience the machine is really susceptible to a sort of anchoring effect.

I've got to the point where sometimes I frame my question as if I disagree with it, just to allow the AI to "agree" with me and actually critique it.

"My team mate wants to X, but I feel like that might be a bad idea. What could go wrong?", etc.

Post reply on HN