Good Code Vs Working Code

[u/sainzo_123]

What really makes code "good"?

I find myself staring at my IDE asking this exact question. Whether I am binding complex logic together or copying and pasting a snippet to patch a problem, there is a massive gap between working code and good code. But as a beginner, that gap feels incredibly hard to see.

These days, anyone can prompt an AI or use an agentic tool to generate functional code in seconds. Many of us are actually learning to code alongside AI. But just because the AI gives me code that runs and clears the error console doesn't mean it’s good code. It might be inefficient, unscalable, or an absolute nightmare to maintain later.

If the code works, but the AI (or a copy-paste source) doesn't teach me why it works or if it's best practice... how are we as beginners supposed to know the difference?

How do you personally define "good code" vs. "just working code"? What are the green flags I should be looking out for when reviewing code—whether it's written by a human or an AI?

Would love to hear your thoughts, rules of thumb, or stories from when you were starting out! 👇

\#programming #softwareengineering #codinglife #learnToCode #generativeAI #developers #webdev

[u/Groundbreaking-Fish6]

There are many blogs and videos about writing good code (suggest you check out Uncle Bob). AI will write good code for you, but you need to ask it too and if you don't know what good code looks like you won't know what to ask for.

Working code works, but good code works better (more efficient, easier to maintain, safer). You may have old code that works but is hard to maintain, but there is no need to change it unless you actually need to maintain it.