The problem is that every living entity in a 10 kilometer radius around me, seems to be hellbent on getting me to do anything but coding. Refining work estimates, fixing badge access rights, fixing a driver issue, telling people that you cannot do 1000 things at the same time, teaching the new developer how shit (doesn’t) works, mangling Jenkins into a functional state again, explaning that thing I did a year ago but is only now used (it was very high prio a year ago), writing documentation that noboby ever reads, progress meetings, specialty group meetings, knowledge sharing meetings, company wide meetings, etc.
Just say no. Decline meeting requests. Set your own priorities. It’s not like they can fire the guy who operates the CI and apparently the physical security systems as well while still writing code for high priority projects.
I had a team of contractors working on some code. They had learnt in their previous jobs to document everything in the work wiki (aside from the design documents which have their own repository)
And it was good they did, since the project was put on hold due to too much mismatch between backend and front, and all the contractors were fired (a day before Xmas) leaving the useless doco as the best reference for whoever needs to resurrect our code
Agreed on all of that. As I understand it, periods of better worker markets make for less of that nonsense people are willing endure. I’ve seen a recent trend of corporations turning up the BS because the job market has been tightening up and people are less willing to take risks.
But I love coding at work?!
The problem is that every living entity in a 10 kilometer radius around me, seems to be hellbent on getting me to do anything but coding. Refining work estimates, fixing badge access rights, fixing a driver issue, telling people that you cannot do 1000 things at the same time, teaching the new developer how shit (doesn’t) works, mangling Jenkins into a functional state again, explaning that thing I did a year ago but is only now used (it was very high prio a year ago), writing documentation that noboby ever reads, progress meetings, specialty group meetings, knowledge sharing meetings, company wide meetings, etc.
You can always write code for Free Software projects in your free time and contribute to a good cause.
Just say no. Decline meeting requests. Set your own priorities. It’s not like they can fire the guy who operates the CI and apparently the physical security systems as well while still writing code for high priority projects.
I had a team of contractors working on some code. They had learnt in their previous jobs to document everything in the work wiki (aside from the design documents which have their own repository)
And it was good they did, since the project was put on hold due to too much mismatch between backend and front, and all the contractors were fired (a day before Xmas) leaving the useless doco as the best reference for whoever needs to resurrect our code
Agreed on all of that. As I understand it, periods of better worker markets make for less of that nonsense people are willing endure. I’ve seen a recent trend of corporations turning up the BS because the job market has been tightening up and people are less willing to take risks.
That’s exactly it. When I code for my own projects, I don’t have to deal with any of that shit.