My guess is that you focus on the wrong things, most burnouts I've seen at peers (I never had one, by applying some simple rules) and colleagues (product/services providers, non-technical) involved money. When you work for money you handle the tasks as a burden, when you code for your side-projects you should get energized.
an email from a client, requesting some changes to her online application form.
I think you didn't got down by technical and implementation reasons, but rather for not doing what you like and/or when you like it.
My story ..
I for one quit doing side-projects a long time ago, I thought (and I was right) that the burden of dealing with the end users, their lack of knowledge and professionalism and so on did not worth it on the long run.
My sanity is worth more then some extra cash. Also by using that extra time on learning I took my career to the next level each couple of years. I could learn what I liked, I could brake things and didn't pay for the damage if it occurred and so on.
So how do I keep the burnout away, a few simple rules I have:
no payed side-projects
lots of breaks (during the week, outdoor sports, swimming, walking ...)
holidays that does not involve any technology
do what you like (I'm blessed that this also pays the bills)
master the schedule, not vice-versa. I should lay the terms when I do what and where (outside of work ofc)
Just a coder and a dad. I love my family and I love to code!!!! started coding at 11, so I have 25 years under my belt. Still love learning about it every day. Black lives matter!
I do feel like you are partially right on the part where you say that I'm focused on the wrong parts. I specifically cut out all clients, except this one. She pays well and normally doesn't request to many changes.
The other night I did free work on the layout, because it was fun. Then today when she asked for the changes on the form, I was annoyed. You nailed it with the fact that it is because it's not a fun thing I want to do, but a work item.
I'm not practicing most of your items, but I think I need to start doing so. These specifically.
lots of breaks (during the week, outdoor sports, swimming, walking ...)
holidays that does not involve any technology
master the schedule, not vice-versa. I should lay the terms when I do what and where (outside of work ofc)
I appreciate you taking the time to respond.
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.
My guess is that you focus on the wrong things, most burnouts I've seen at peers (I never had one, by applying some simple rules) and colleagues (product/services providers, non-technical) involved money. When you work for money you handle the tasks as a burden, when you code for your side-projects you should get energized.
I think you didn't got down by technical and implementation reasons, but rather for not doing what you like and/or when you like it.
My story ..
I for one quit doing side-projects a long time ago, I thought (and I was right) that the burden of dealing with the end users, their lack of knowledge and professionalism and so on did not worth it on the long run.
My sanity is worth more then some extra cash. Also by using that extra time on learning I took my career to the next level each couple of years. I could learn what I liked, I could brake things and didn't pay for the damage if it occurred and so on.
So how do I keep the burnout away, a few simple rules I have:
Thank you for your response.
I do feel like you are partially right on the part where you say that I'm focused on the wrong parts. I specifically cut out all clients, except this one. She pays well and normally doesn't request to many changes.
The other night I did free work on the layout, because it was fun. Then today when she asked for the changes on the form, I was annoyed. You nailed it with the fact that it is because it's not a fun thing I want to do, but a work item.
I'm not practicing most of your items, but I think I need to start doing so. These specifically.
I appreciate you taking the time to respond.