DEV Community

Discussion on: You ain't gonna need it

Collapse
 
miguelmj profile image
MiguelMJ

This is completely spot on. I deal with overengineering myself and I'm learning to have a more realistic approach to the solutions I code. One approach I'm trying is that, when I'm not sure if something is going to be really needed, then I put a short time limit to implement it. If it takes too long, I quit and continue with the rest of the code.
I only want to add one thing: you can do overengineering in personal projects to learn. I have a lot of code that I never use, but I try to have it heavily commented and its common that I revisit it to see how I thought that certain problem could be solved.
However, the focus of this code is not quality, but experimentation and learning, so its important to keep it separated from real code!
Great post, Lina :)

Collapse
 
linajelincic profile image
Lina Jelinčić

Thank you!
I like the idea of overengineering personal projects. It really can be a great way to fully grasp some concepts and find out what is going on under the hood. In the worst case scenario, you learn how not to do something, which is also a great thing!