3 ms·
One thing I realized after some rather ugly burn out a few years ago is that I mostly created my misery myself - there were demands and questions if I can take
by nisa 3y ago
One thing I realized after some rather ugly burn out a few years ago is that I mostly created my misery myself - there were demands and questions if I can take on some work but no psychopath managers, no deadlines that couldn't be moved.
I created most of the pressure myself - my biggest sin was working more hours than being paid because I wanted the project to succeed. It was never appreciated and only lead to be being angrily called on Sunday if something was broken - something my lazier 9 to 5 colleagues never experienced.
So I'd say instead of practicing no, first practice setting boundaries and practice organizing yourself.
Additionally a perverted mechanism came into play because I cared and wanted to improve the product at the time - the others kind of said: do if you like but that came without any real support and it lead to me being kind of laughed at as a hot air talker just because I was the only one that wanted to improve things.
Looking back I should have quit way earlier and of all things I shouldn't work overtime for free.
Having to say no could have been avoided if I had a good schedule that I could have used to prioritize the orders and giving the person making the demands an overview of my workload.
Watch out if there is some unhealthy inertia in your organization and especially be careful doing important silent work. It won't be thanked.
Either quit and look elsewhere or watch out that your workload is fair and similar to your colleagues even if that means to not solve that interesting problem because it's not your official job.
- vlabakje90 3y ago> [...] something my lazier 9 to 5 colleagues never experienced. I think your reply shows perfectly well that guarding your boundaries is not exactly laziness.
- gwervc 3y agoInteresting experience. For anyone considering switching jobs because they were in your situation, here is my survival guide of doing jack shit as a software developer: - set medium/low expectation. To that effect don't work more than 5-6 hours out of your 6-7 hours day. This way you'll always have capacity to work more dor a rush and may be priced for that; conversely if you're always working at fill capacity and for some reason you can't deliver be you'll be criticized for it and your previous hard work will go unnoticed. Of course deliver acceptable output, preferably just above the bare minimum to keep the job. - learn to shift blame. The CI is slow, code is crap, etc. Sugar-coat it with ideas for improvements. Those will realistically never happen but you'll pass as a bit more positive while the blame can be shift to the people making the decision not to improve things. - know the laws applicable to you, and to businesses. Whoever has knowledge has an edge, and the HR department sure know a lot. Check primary and secondary sources. It's not because someone or the company say something that it's true, and some threat are simply inapplicables and bet on worker's lack of knowledge.