3 ms·
Kinda unrelated to topic at hand but I always wanted to ask this to other programmers: Author mentions that he traded sleep for code, and I hear this from so m
by DethNinja 6y ago
Kinda unrelated to topic at hand but I always wanted to ask this to other programmers:
Author mentions that he traded sleep for code, and I hear this from so many people but I really cannot understand how well they manage to pull this off. I simply cannot code productively if I get less than 7 hours of sleep or code for more than 8 hours straight, and caffeine doesn’t help me. So how do you people manage to pull this off? I’m really envious that people can code all day long but does it really provide good code? Doesn’t that increase the bug count of the code?
- latencyloser 6y agoEasy, most of the code we write is pretty mindless. Boilerplate tying together of various internal libraries to make it play nice that you've done too many times to count. Following someone else's wiki page instructions on how to implement some "best practice" that needs to be done for a production system. Writing CRUD operations and such. Writing unit tests for all these things. Sure mistakes happen when you're exhausted but the stuff is hard from mentally demanding given the bar that they're supposedly hiring for. I don't say that disparagingly, this is 90% of my day to day life as a mid-level engineer at a FAANG. The other 10% I might get to do something "neat" that I can justify somehow. It depends on the team of course, but I find the Author's experience believable.
- julianlam 6y agoHe (or she) didn't say they coded well on limited sleep, so there's the trade-off.
- valbaca 6y agoamznymous here Don't do it :) Please don't be envious It didn't produce good code, but to be fair, the project didn't need to have great code, just working code. It absolutely increased the bug count. Again, in hindsight and with a calmed mind, it's obvious.