3 ms·
Sometimes it's more about learning clever architecture than clever, or better code. Clever architecture can often help keep your code an order of magnitude sim
by j45 12y ago
Sometimes it's more about learning clever architecture than clever, or better code. Clever architecture can often help keep your code an order of magnitude simpler.
The issue you may run into is seasoned developers are the ones who learn this over time.
Conversations based around "why" help a team understand the importance of:
- creating a codebase that they will still want to / be able to work on without dealing with poor decisions of the past, o
- being kind to your future self
- realizing not everyone has had a relationship with a codebase for 3, 5, or even 10 years and what that might look like. In the real world, existing code bases are a reality. Optimizing for that reality, instead of the clean slate that university assignments, or startups provide can also be an important light bulb.
- peer reviews, and teaching the why you do things a certain way are far more likely to get the lasting result you are seeking.