4 ms·
The original article is really interesting. https://medium.freecodecamp.org/lessons-from-my-first-year-of-live-coding-on-twitch-41a32e2f41c1 https://medium.free
by rovyko 8y ago
The original article is really interesting.
https://medium.freecodecamp.org/lessons-from-my-first-year-of-live-coding-on-twitch-41a32e2f41c1 https://medium.freecodecamp.org/lessons-from-my-first-year-o...
I didn't even know livestreaming code was a thing aside from pre-scripted tutorials. I'll have to watch one of the streams, because the hands-on nature is probably good for learning the quirks of various techniques that you don't get from programming books.
It's too bad I spend 80% of my development time reading documentation and chasing down bugs.
- lessclue 8y ago80% is thinking and figuring things out, 20% is writing code; always.
- LandR 8y agoTHis. Solve your problem then write code. Problems solved by writing code almost always ends up with crappy / messy code / difficult to maintain code. The coding should be the easy bit, it's just implementing your solution in a language you know. It's basically just typying.
- UncleMeat 8y agoIt gets lower and lower the more senior you get because you add an entire "obtain requirements and develop consensus" step.