This just means that your line manager, whose role it is to ensure all resources under them are working at efficient capacity, is not doing his/her job.
And in turn neither is his manager.
And in turn neither is his manager.
I would much rather a developer work 10 hours and accomplish what needs to get done than work 40 and negatively impact the business.
It feels like there is a third option here that I can’t quite put my finger on.
Systems need slack to respond to change. A fully utilized queue quickly leads to infinite backlogs.
People seemingly end up having a lot more time for _defining processes_.
There are people at nearly every large company I’ve worked on that so more meta work, and sometimes demand more meta work than actual work.
Like there are folks that are actively costing productivity in exchange for the meta work.
I’ve challenged them to actually back the work they’re doing with data and how it’s actually helpful and generally there’s no follow up. It’s amazing.
Half of what they did was never committed into git, because a software versioning process is for dummies. And the other half could only be found in a random feature branch, because they didn't need any review process, their code was always faultless.
Whatever was running in production did not match any state of the repository, because CI/CD processes only get in the way.
The documentation never matched their code because documentation is only for people that don't know what they're doing, and we shouldn't hire such people anyway.
Not saying that's you. But that is the type of person you appear to me when you proudly proclaim that processes have no value.
I'm not talking about the use of git, etc. I'm not even talking about process in relation to the code either. It's process for tracking how we track projects. Like, that level of indirection.