3 ms·
I do exactly the opposite of this. The stuff I work on is mostly trivial except for the complexity and feature interaction involved in real apps. At most, the
by eternityforest 4y ago
I do exactly the opposite of this.
The stuff I work on is mostly trivial except for the complexity and feature interaction involved in real apps.
At most, there might be one or two interesting problems that can be isolated... but usually not.
If I'm learning a new framework, all the features individually are a 10 minute google search. I'll forget how to use them, but IDE autocomplete will remind me.
I'm not that interested in memorizing 1000 function signatures. I'll learn them in a year of actually using them, if I in fact actually ever use them.
What I'm interested in is how you manage complexity with that framework, and I want to be sure I exercise all the features you only need in larger apps.
I could see keeping experiments separate as being good if you are trying to learn how to build small software. If you plan to do microservices, or you work on a lot of interesting problems that aren't just assembling trivial things, or you just enjoy small and light things.