mo server

(disco.cloud)

804 points jryio | 2 comments | 21 Oct 25 20:28 UTC | HN request time: 0.396s | source

Show context

hinkley ◴[21 Oct 25 21:08 UTC] No.45661730[source]▶

> The Real Insight: Staging Became a Free Commodity

Not free, it became a productivity boost.

You now have a $35k annual budget for the maintenance, other overhead, and lost productivity. What do you spend it on?

> The team also took on responsibility for server monitoring, security updates, and handling any infrastructure issues themselves

For a place that’s paying devs $150k a year that might math out. It absolutely does not for places paying devs $250k+ a year.

One of the great frustrations of my mid career is how often people tried to bargain for more speed by throwing developers at my already late project when what would have actually helped almost immediately was more hardware and tooling. But that didn’t build my boss’ or his bosses’ empires. Don’t give me a $150k employee to train, give me $30k in servers.

Absolutely no surprise at all when devs were complicit with Cloud migrations because now you could ask forgiveness instead of permission for more hardware.

replies(1): >>45665682 #

1. thomasfromcdnjs ◴[22 Oct 25 06:53 UTC] No.45665682[source]▶

>>45661730 #

I know everyone in thread today is having fun embracing the hacker ethos and running things themselves.

But I've migrated plenty of companies off custom deployment setups to PAAS and told many ceo's simply what OP above has shared. Even a part time dev ops engineer is still $60000 a year, and that can buy us a LOT on PAAS. Using PAAS you can have effectively zero dev ops, I've also trained non technical people on how to scale their own servers if no devs are around because you just have a web based UI slider.

I consider myself a developer who cares more about the business, risk, profits and runway. A lot of developers don't share this mentality (which is fine btw always need engineers who like engineering for engineering sakes) but in meetings you will have a hard time beating me in an argument if you try to say that running servers ourselves would be "cheaper", and/or even faster, safer and definitely not more stable. (obviously not in all situations, but kind of most for modern crud web apps that don't require complicated compute setups)

I'm probably being overly antagonistic, forgive me for that, though highly recommend questioning the real cost of running your own setups.

replies(1): >>45673522 #

2. hinkley ◴[22 Oct 25 18:52 UTC] No.45673522[source]▶

>>45665682 (TP) #

As a lead or principal dev you are constantly shuffling old problems off to new people so you can stay on top of new or broadening problems. It’s a lot easier to delegate problems if you’ve made them smaller during your watch. I’ve seen enough of the consequences of failure to delegate. But it takes a bit of self awareness to see how being a bottleneck affects other people while or after you are busy unblocking them.

Volunteering to be preempted by broken systems more often is a sucker’s bet. Solve problems so they stay solved. It’s more work now, but reduces the interest rate on past work so you can get new things done.

↑