Anxiety and Shift in Design Focus as AI Replaces Traditional Craftsmen
Problem
The discussion highlights that with the rise of LLM code generation, software engineers are shifting from 'how to build' to 'what to build', raising concerns about role boundaries, reliability of AI-generated code, and the potential replacement of human creativity.
Pain points
- AI may replace software engineers' core responsibilities
- Trust crisis regarding the quality and reliability of AI-generated code
- Anxiety over shifting from implementation to defining product goals
Questions to verify
- Do you believe current AI tools can reliably replace traditional coding work?
- In the product design phase, do you focus more on 'how to implement' or 'what to implement'?
- What concerns do you have about the maintainability and security of AI-generated code?
Evidence
quote · @Anonymous
I like the analogy as someone who is a carpenter by trade and have dabbled in creating a few working things over the last years only because of the advancement of LLM code generation.As a carpenter, you come up with *stuff* from your mind and just make it exist. LLM building feels very similar to how quickly you can from idea to something that works for a given purpose.I do think a more accurate analogy would be to place the software engineer as the construction superintendent.The superintendent is jack of all, master of none. They may specialize in plumbing, electrical, hvac, masonry, or carpentry but relies on experts where they lack. They can fix any issue with any of these trades, but only when needed. They know enough to know when something is wrong and needs corrected (and may even b
quote · @Anonymous
Instead of the most important question being “how to build this”, or “can we build this”, now the most important question is “what should we build”.
quote · @Anonymous
I like the analogy of the carpenter building the form that the masons used to build the bridge.I think it is pretty accurate for today's software construction based on a lot of posts here and on other forum threads.Software programmers today using AI just flesh out the frame of the product that they want to build then they fill that frame with AI slurry, their concrete, and that becomes the new application.
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.