re: How do you avoid rabbit holes? VIEW POST


It's been about 11 years since I started writing code professionally, and I'm not sure I'm capable of avoiding rabbit holes.

Whether it's web, desktop apps, databases, or game dev, I just can't help but over analyze. The products always turn out great because of it, but often much later than planned.

Tasks at my real job still gets done on time, mostly, since my rabbit holing largely occurs on my side projects. That knowledge then gets applied to future iterations of the work at my job.

Maybe that's the key for me: do the boring thing first for jobs that are time sensitive and important. Then allow myself to deep dive topics since I enjoy it, and mix the new stuff in as appropriate?

Code of Conduct Report abuse