4 ms·
late stage "startup" who had struggled with growth for years, they thought they needed to invest in building a more complex system and infrastructure, and they
by WYepQ4dNnG 5y ago
late stage "startup" who had struggled with growth for years, they thought they needed to invest in building a more complex system and infrastructure, and they hired tons of engs (who actually had literally nothing to do) ...
instead what they really needed was to focus on their customers and build them a useful product that simply worked.
They spent months building and deploying their own k8s cluster: EKS was "vendor lock in" so that wasn't a good choice for them, but guess what, all their infrastructure was already running in AWS anyway and their product was already vendor locked in: RDS, S3, etc ...
also ... to make things even more complex, they thought they needed to go all-in super distributed micro services: it took literally months to get new "services" up and running in production. It was a s*t show!
One of the many story of let's break the monolith, embrace microservice, thus k8s ... gone horribly wrong.
Eventually most engs left ....
- 908B64B197 5y ago> but guess what, all their infrastructure was already running in AWS anyway and their product was already vendor locked in: RDS, S3, etc ... I laughed, but your response doesn't answer my question regarding engineers comp.
- WYepQ4dNnG 5y agostock options, not great
- rantwasp 5y ago> Eventually most engs left .... and now have k8s on their resume. Bazinga!
- rachelbythebay 5y agoDid we work for the same company?