4 ms·
> but at some point, professionals need to learn the basics Think about a junior joining a company. Through the first weeks they get: to be useful you need to
by viraptor 3y ago
> but at some point, professionals need to learn the basics
Think about a junior joining a company. Through the first weeks they get: to be useful you need to learn about dependency management, git, frameworks we use, data stores we use, processes for review, our ci approach, our release approach, ...
Adding yet another process your work depends on, is fiddly to setup and doesn't have good docs online really isn't great. "We can add this on top, it's just basics" can really add up with enough systems.
- palata 3y ago> "We can add this on top, it's just basics" can really add up with enough systems. That's the thing. In my view, you say "we should keep adding wrappers on top of wrappers and libraries on top of libraries, such that juniors can quickly get productive, but nobody actually understands what they are doing anymore and the smallest executable takes 50MB". I say "we should reduce the number of dependencies such that one can understand the system better, even if it means that juniors need to spend time learning the basics". Of course there is a balance to find (not everybody needs to master assembly), but the modern way, IMHO, goes too much towards productivity, and not enough towards mastering ones tools.