-
Notifications
You must be signed in to change notification settings - Fork 0
2020 06 27 Extraction Day
Under that word, mostly project managers want to do so.
The biggest mistake is, to design your architecture for reusability.
Why? When you start thinking in technical requirements, your modules begin
to be irresponsible. Also the code complexity increases without want. By the
way, you can't really know the code parts, before you have coded them ;)
A better way is, first to forget the reusability. Design your classes, modules, domains, etc basing on responsibility. You will definitively find technical responsibilities. That code you collect automatically on a place outside of other core responsibilities.
In this Time-Tracker project was that also happened. Now, after some time, I start to clean the project and moved the code out into new projects:
- State Value Observer - a most as primitive redux.
- Simple Storage - Just a handler for Storage API usage.
- Application Router - Just a simple router to switch pages by using History API.
That "micro" projects have now atomic responsibility. That mean, the whole project has one technical responsibility. This will protect the project before exploding of complexity.