bootily

I have wierdly come to a place in which I realize that side projects are bad for my career.

Years ago, they nurtured my talents, provided entertaining distraction from my day job and kept me curious.

After experiencing 2 years of burnout and coming fully back to life, I realize that side projects were partly to blame.

I think side projects taken too far not only is a source of exhaustion and stress but degrades my ability and desire to focus on my employers admittedly mundane work.

But since I left side projects behind I can see the quality of my paid work going sky high relative to 5 years ago.

No matter how smart, curious, creative, focused you are, there's real danger in stretching yourself too thin.

Would like to hear others experiences with this.

Was having a casual convo with another Deva few days ago about IDEs. Always a fun topic but I related to him how sick I am of eclipse after all these years and how even though say xcode is not as good an IDE that being written in C it let's me work at my speed.

This is an odd thing to me because I don't want to confuse operational speed with delivery speed. I'm not and would never claim to be a "fast" coder.

But if you have been writing code for 15 years its pretty reasonable to assume you get faster at the mechanics.

My bad days at work are not about finding the right solution. They are bad because I merely have to wait 2 seconds after I click on ANYTHING.

While 2 second push to pain is a standard for shitty websites, I can't accept that for an IDE. I guess vi wins.