Hacker News new | ask | show | jobs
by cmiles74 397 days ago
When I started working in the field (1996), I was told that I would receive detailed specs from an analyst that I would then "translate" into code. At that time this idea was already out of fashion, things worked this way for the core business team (COBOL on the AS/400) but in my group (internal tools, Delphi mostly) I would get only the most vague requirements.

Eventually everyone was expected to understand a good deal of the code they were working on. The analyst and the coder became the same person.

I'm deeply skeptical that the kind of people that enjoy software development are the same kind of people that enjoy steering and proofing LLM generated code. Unlike the analyst and the coder, this strike me as a very different skill set.

3 comments

> I'm deeply skeptical that the kind of people that enjoy software development are the same kind of people that enjoy steering and proofing LLM generated code. Unlike the analyst and the coder, this strike me as a very different skill set.

indeed. people generally hate foreign/alien code, or rather - love their style too much. it is not hard to recognize this pattern - ive seen it with colleagues, with my students, with some topnotch 10x-coders back in the day. so proofing is a skill one perhaps develops by teaching others do things right, but is not something most people entertain about.

on the other hand, people who lack time and patience to implement complex stuff may benefit from this process. particularly if they are good code-readers, and some seasoned devs become such people. i can see little chance they wont be using llms to spit code out.

but the two groups largely don't overlap and are different as astronomers and astronauts.

I worry a bit about people who like writing code but don’t like reading and debugging it. There are enough “throw it over the wall” coders.
Yeah, AI will kill all mundane brick layering jobs.

The real software engineering role, with architecture, customer management, discovery phase, risk analysis and all the other kind of stuff, not yet.

I have people skills damnit!
I don't mind reading and debugging my own code, or any other code written with a plan by someone with a clue.

Reading and debugging slop code is not the same thing, not even close.

For me it dependa on scale. Asking AI for something small and specific is a joy. Asking it to make a big change is a nightmare I so far only try every time a new model comes out.