Hacker News Reader

I have found success in using your "coping mechanism". I usually alternate between 2 projects that need my "engineering cycles" and then have N that need my "management cycles", which I don't find as exhausting and don't drain "steam" as quickly.

In bodybuilding, this is called "periodization", I'd say that's a pretty accurate term to describe this.

View on HN

this sounds interesting to try for me. Software engineering alone wears off for me after a while on a project to the point I simply cannot type a single line for it if forced. Managament is where I am really good at coming up with ideas/plans/strategies but the day-to-day following-up (including staying calm and friendly in the face of very slow employees sometimes) also is soul crushing and depressing after a while. My sweet spot somehow is in the middle an hopping between projects, mentoring engineers and also doing my own projects on the side or even spearheading initiatives... sometimes.

What cycle times/scheduling works best for you? how do you deal with the dread of picking up a topic again after letting it go mentally?

To be honest I go by feel. I usually can't spend more than 3 full focus days on something without getting burns.

Reply on news.ycombinator.com