Yep exactly. Try adding unit tests to legacy code when your coworkers consistently ignore it. They'll be praised as fast workers who kinda sorta get the job done. All you'll get is called out for being slow and be tasked with fixing someone else's mess and your code won't be a maintenance burden.
It feels like in software dev we can just make messes and move on without accepting responsibility. Increasing scope on yourself with those small misc. tasks also means accepting more responsibility than most software devs accept which makes you a target when things don't go smoothly either through your fault or someone else's.
The biggest catch is that those 2 hours that you have butt in seat means you can't work on your own skills/side project for fear of the employer owning the code. The only thing you can do is take online courses at Coursera or Udemy as they're general enough skills.
It feels like in software dev we can just make messes and move on without accepting responsibility. Increasing scope on yourself with those small misc. tasks also means accepting more responsibility than most software devs accept which makes you a target when things don't go smoothly either through your fault or someone else's.
The biggest catch is that those 2 hours that you have butt in seat means you can't work on your own skills/side project for fear of the employer owning the code. The only thing you can do is take online courses at Coursera or Udemy as they're general enough skills.