I’m intrigued that there’s a “movement”. I suppose that’s what you need to get news articles and promote change. What’s old is new.
I’m intrigued that there’s a “movement”. I suppose that’s what you need to get news articles and promote change. What’s old is new.
- Small selection of services (databases, queue's,...) If a service was not yet in house, brace yourself for a year of meetings, enterprise contracts, security audits,...
- Overprovisioning of everything as it was a weekly to monthly process to acquire new resources
- lots of half-assed documentation with many manual steps being missed. Sometimes the DEV environment was so different from the PROD environment you couldn't reliable trust deployments.
- lots of outdated software and servers with tooling that promised to ease all of that while delivering none of it.
- different teams for different components, all with their own procedures, zero API's and you hoping that the one guy that actually helps you is not on a holiday.
- Very strange limitations because how all the different vendors had their own set of restrictions and zero incentive to adopt another vendors solution.
Oh yeah, they were still running Python 2 for parts of the main application. It was literally like traveling back a decade. I found dependencies that hadn't been updated in 10 years.