I know some C++ and Python and have made a few small projects. I want to learn how larger software is designed, but I'm unsure how much to build myself versus using AI to generate or debug code. Where should I start?
How do I learn software engineering beyond just coding?
Answers
Start with something small enough that you can understand the whole thing, like a command-line tool that saves you a few clicks. Design and write it yourself, including the awkward parts. Getting stuck and debugging is part of the learning, not just wasted time.
Then add a feature or two over time. When a change becomes annoying, look at why. Maybe two parts are too tightly connected, or one file is doing too many jobs. Refactor it and see whether the next change gets easier. That's a practical way to start learning architecture.
Reply to this answer
AI can be useful without handing it the entire project. Try asking for an explanation of an error, a hint, or feedback on a design you've already sketched. You can also ask it to review a small piece of your code and then check its suggestions yourself.
If it generates code, don't count reading the explanation as proof you understand it. Trace what it does, test it, and try changing or rewriting it yourself. The ability to evaluate the details matters as much as the high-level design.
Reply to this answer
Find a small open source project and read how it divides responsibilities between files. Pick one modest change and implement it. Working in an existing codebase teaches a different skill from starting every project with a blank page, and you get to see design choices in context.
Reply to this answer
For a more structured exercise, build a simple web app without a framework first. Work out how requests get routed and how to split the code into manageable pieces. Then try refactoring it to use something like Flask or Django and compare which decisions the framework handles for you.
Keep the app small. The point isn't to build a production system from scratch, it's to understand what the framework is doing and why you might use one.
Reply to this answer
Don't let the architecture talk scare you away from fundamentals. Coding isn't dead, and a design diagram won't help much if you can't reason about the code underneath it. Books, guides, and tutorials are useful, but follow them up by building or changing something without relying on the walkthrough.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions