I've worked at a startup that could've trivially ran on a single VPS and kept things simple yet had a dedicated infra guy using a full k8s setup.

▲

Zetaphor 4 hours ago | parent | next [-]

I once interviewed for a small print shop that was proudly throwing out every AWS product name when describing their stack. They serve a few hundred customers and their previous system worked for decades entirely over email and a web form. I decided I wasn't interested around the point where he explained how they're migrating to lambdas

	▲	ryandrake 4 hours ago \| parent [-]
		LOL, I'm laughing and I wish it was because this was funny rather than terrifying.

▲

skeeter2020 8 hours ago | parent | prev | next [-]

hey - devs aren' the only ones who fall in the premature optimization trap! Everyone from the CTO envisioning the scale of their future startup down to the IT intern is influenced by this, plus it's in the best interest of a dedicated infra guy to have a lot of dedicated infra. If you don't manage people K8s can become your kingdom and the size a badge of importance.

	▲	deaux 6 hours ago \| parent [-]
		In this case I think it was a bit of CTO envisioning scale, then a bit of CTO genuinely overestimating what is needed, plus a good amount of CTO just being the average nerdy dev who likes the idea of shiny toys and cool sounding stuff - "we're running on k8s!". A year or so after I left they ran out of money. They would've lasted longer if the infra guy would've just stayed the backend guy and helped get projects done more quickly instead of shiny k8s setups for projects with a dozen end-users per day. Recently I saw that the CTO has started a new startup - and ironically the only guy who he took with him onto the new team looks to have been the infra guy! I don't blame infra guy, he genuinely believed he was doing the right thing.

▲

InfraScaler 7 hours ago | parent | prev [-]

How else are you going to put k8s on your CV? :-P