Knowing how to code is NOT enough: The root problem in our learning process

👋, first of all, thank you for the immense value you bring to the community. Your courses have taught thousands of us how to master code. But today I want to put a challenge on the table for a future course.

I've realized the root problem we have in current tech education: We consume hundreds of hours of tutorials learning languages and frameworks, but we DO NOT know how to design software. We know how to write a class in Java, but when a client asks for a project from scratch, we hit a brick wall. We are missing the lost link: Object-Oriented Analysis and Design (OOA/D).

Anyone who wants to build real software (whether at home or at a company) needs to master skills that go way beyond the programming language itself:

✅ Gathering real requirements (without getting overwhelmed).

✅ Differentiating and documenting functional vs. non-functional requirements.

✅ Writing Use Cases that actually add business value.

✅ Translating those Use Cases into Sequence Diagrams and Domain Models.

✅ Knowing how to elegantly assign responsibilities to objects (GRASP/GoF Patterns).

The request: Could you guys consider making a full course on OOA/D?

But with the Amigoscode magic: 100% PRACTICAL. We don't want more boring, 200-page university theory that no one reads.

We want to see Nelson sit down with a "client", extract the messy requirements, draw the diagrams on a whiteboard, and then translate it into real code step-by-step using Agile iterations.

I believe this is the ultimate leap to go from being just a "coder" to a true Software Engineer/Architect.

4 comments

Knowing how to code is NOT enough: The root problem in our learning process