Comment by protocolture
6 months ago
Pretty done.
Employers: Making it an obligation that I act like we have in house tools that were meant to exist 3 years ago, doing everything manually.
Customers: So beholden to their technical debt that they would rather pay ten times the opex than the capex to remove the debt.
Shits me to tears.
Sometimes technical debt is kept rather than being fixed because "if we fix this some high-value technologically-challenged clients will no longer be able to use our service."
This is actually solvable but will need an "out of the box" thinking.
Its nice to think that way but for my clients it isn't the case. Its simply friction and inertia.
The box I am in has my employer on one side, happy to have made the suggestion to move away from old technical debt, but happier still to reap the rewards of a customer who will pay massive amounts of opex to keep shit running. And on the other side the customer, too lazy to have any internal conflict over technical debt and paying massive amounts of opex is preferably than directors having arguments with each other.
None of their technical debt is customer supporting. They do supply serial keys via a truly ancient aspx website but they can also port the backend component that handles those serials pretty much instantly. It really is a choice.
Oh that's an entirely different flaming dumpster, but I feel that too.