Submitted by twovests in technology

I have a job I really like: Decently-paying job, good benefits, 100% work-from-home, doing fullstack development on a pretty agreeable stack, corporate is still committed to diversity and inclusion, they use my name everywhere except my tax forms, the work we do isn't particularly evil (other than being a part of capitalism), no drama in the team.

But we are deep deep deep in on AWS, and every thing I learn feels like poison I am allowing into my brain. When bombs drop on us-east-1, they'll be begging me to help set up on-prem racks, I am sure of it.

8

Comments

You must log in or register to comment.

devtesla wrote

aws really feels like a trap, easy to start but inertia will keep you on the platform once you start getting huge bills and hitting problems. but it's a "no one has ever been fired for choosing aws" situation so rip.

7

flabberghaster wrote

100%. They bill it as "you don't have to pay a guy to run your on prem hardware for you" but you absolutely do not save money once you've scaled to the point you need a few machines.

And by that point, your software is probably so tied in to proprietary Amazon stuff that they've got you in a vice.

It's the same model as Oracle: oh we're so easy to use and friendly, and we have all these great Oracle specific features, go ahead and use them! 😊 but then they have you locked in and they can just start squeezing.

2

twovests OP wrote

Going "your personal blog" mode: I don't like the bespoke names like "Route 53", but at least a lot of AWS makes sense? There are very few things I've come across (as someone toes-deep into AWS) that seem like a horrible engineering mistake made at Amazon.

If I were to build an intranet for the internet and divide everything into tiny little separately-billable services, I'd do it a lot like this.

4

twovests OP wrote

If my company didn't just sell their office space (yayyyyy they can't make me go into the office), I'd have tried to get them to invest in an Oxide rack.

5