4 ms·
Feel free to ignore/downvote me - just wondering: is this a thing people do? I certainly understand and support it, but I have never seen it happen at work (an
by sotojuan 9y ago
Feel free to ignore/downvote me - just wondering: is this a thing people do?
I certainly understand and support it, but I have never seen it happen at work (and I work in a start up, not some old boring enterprise shop). After eight hours, if I want to program at all I'll probably mess around with some new language or whatever, not "train". Same with my coworkers. Maybe I am lucky, but the things I do at work challenge me such that I learn something after every project.
Anyway, I did ask a similar question one time, check it out:
https://lobste.rs/s/uu6v1o/what_is_deliberate_practice_for https://lobste.rs/s/uu6v1o/what_is_deliberate_practice_for
To give you a direct answer, how about doing LeetCode exercises, starting from the easiest and building up? If you take your time and note down how you solved each problem, you will start to notice patterns and can apply those at work to solve stuff quicker. But IMO, if we are talking about performing "better" at work programming, it's more about the skill of taking business specs/feature request and fitting them with the existing codebase :-)
- muzani 9y agoI think it's less likely to happen at a startup, because there is more work to be done. Larger companies often have some kind of official training (even the boring enterprises). I know this, because I freelance with a training company and often do things like training courses to teach a bunch of companies how to do Material Design. It takes a lot of time and error to mess around, and some libraries have such immense productivity boosts that it's a waste of time not to do them. In my case, I once bought an ergonomic keyboard and realized that I was typing the wrong way for years. My typing speed halved for about a week, so I did some 30 min/day training routine until I got it back up to an acceptable rate. But I think that I could actually be typing a lot faster if I bother to practice with it. There are some other things - debugging tools, keyboard shortcuts. And there are some major things like learning RxJava, Kotlin, Butterknife, or some architecture, which isn't always possible with 30 mins/day, but may cost productivity if delayed and something you want the whole team up to date with.