3 ms·
Two things: 1. We read much faster than we speak, so watching a video is massively less time-effective. If the junior is doing this on company time, they’re c
by CareyB 8y ago
Two things:
1. We read much faster than we speak, so watching a video is massively less time-effective. If the junior is doing this on company time, they’re costing money.
2. There was an article somewhere about a dev exhibiting these ‘symptoms’. Turns out they were barely competent. Their entire method was to copy code they found on the Internet, and paste it in. They were entirely incapable of writing code from scratch. The article went on to elaborate that, after extensive (expensive) coaching from the senior dev who authored the article, the person turned out to be a pretty good developer. They just started their career trying to advance by gaming the system.
- scarface74 8y ago1. It depends. If I’m learning a new framework, language, or technology, I’ll generally watch a video to get an overview. This will generally tell me the what. When I start working, I might not remember the how but I’ll look that up. Whether it’s fair or not, a lot of companies look down on learning on the job - especially watching a video. I’ll ususlly watch videos at home and just read docs for specifics at work. Most of the time you can cobble together the template of a solution from code you find on line and modify it if you know what you are looking for. 2. The poster said “Their work is good...”. If their work is good, why does it matter the how?