4 ms·

They should have fired the author/s of this abomination much earlier instead of allowing that thing to evolve up to that size.

• reificator 8y ago
  > They should have fired the author/s of this abomination much earlier instead of allowing that thing to evolve up to that size. The main author of the SQL side and original author of the frontend has been promoted to the top because the system is critical to the business needs, and since everyone else struggles to work with this monstrosity they must be a pretty great developer. Can't afford to lose them. The frontend team have threatened to quit several times unless things get better. They've been demanding version control, CI, automated deployments, a shared library, and to not use the domain-specific editor piece that prevents all this. Management (including (or because of?) the OG author) is convinced that they're pushing for these things because of job security and refuse to let them overcomplicate things. But every time they they threaten to quit they get pretty substantial raises because no one else is willing/able to deal with the mess they were left with. If you ask me, no amount of money is worth that environment, but all parties involved still work there...