That was quite the take on burnout. The lifestyle you've crafted for yourself is something we all strive for!
Good description of reality. Don't forget the 1-2 hours of coding in our free time for the average developer to keep up. But the family/chore responsibilities are actually limitless so finding the coding time, let alone downtime, is difficult.
I actually do a fair bit of coding in my unpaid time, not to keep up, so much as because I have community project ideas and things I need/want in my life. I have a growing number of repos on GitHub and can't keep up with it all, but because it's not paid, no-one's life depends on it, and it's only got very understanding stakeholders (usually also time strapped FOSS contributors) it potters along without "burnout" per se.
I do sometimes lose sleep though, because I love solving problems and it just captures my spirit and I occasionally end up trying to solve one and getting stuck, so two things can happen:
On one of those evenings I'm coding (and I suspect that's 5-10 evenings in any given month as a 90 percentile band) I might end up staying up much later than intended (and my morning rise demands, as I typically walk kids to school and need to make lunches, and have them breakfasted and dressed beforehand, not to mention myself showered, er woken up, and hopefully with some fluid intake if not breakfast too) .
Regardless of when I do retire, the problem is racing around in my min, which is thinking of all the things I've tried, have to try yet, and so on what I've learned thus far.
This little project consumed my January nights from memory:
Learning how to capture and process the Tyro sensor data, and then present it. I had equipped the street library with door sensors in December but December is rather busy on the social calendar so only got so far with working out how to read the Tyro data. Actually building that library was an on and off jobs the year prior. And even a little project like that is never quite done. Just one of the community projects on the go.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That was quite the take on burnout. The lifestyle you've crafted for yourself is something we all strive for!
Good description of reality. Don't forget the 1-2 hours of coding in our free time for the average developer to keep up. But the family/chore responsibilities are actually limitless so finding the coding time, let alone downtime, is difficult.
I actually do a fair bit of coding in my unpaid time, not to keep up, so much as because I have community project ideas and things I need/want in my life. I have a growing number of repos on GitHub and can't keep up with it all, but because it's not paid, no-one's life depends on it, and it's only got very understanding stakeholders (usually also time strapped FOSS contributors) it potters along without "burnout" per se.
I do sometimes lose sleep though, because I love solving problems and it just captures my spirit and I occasionally end up trying to solve one and getting stuck, so two things can happen:
On one of those evenings I'm coding (and I suspect that's 5-10 evenings in any given month as a 90 percentile band) I might end up staying up much later than intended (and my morning rise demands, as I typically walk kids to school and need to make lunches, and have them breakfasted and dressed beforehand, not to mention myself showered, er woken up, and hopefully with some fluid intake if not breakfast too) .
Regardless of when I do retire, the problem is racing around in my min, which is thinking of all the things I've tried, have to try yet, and so on what I've learned thus far.
This little project consumed my January nights from memory:
montagu.street-library.info/
Learning how to capture and process the Tyro sensor data, and then present it. I had equipped the street library with door sensors in December but December is rather busy on the social calendar so only got so far with working out how to read the Tyro data. Actually building that library was an on and off jobs the year prior. And even a little project like that is never quite done. Just one of the community projects on the go.