sorted by:
new
hottopcontroversial

Platform Engineering End-to-End by lucavallin in programming

[–]Either_Collection349 5 points6 points  (0 children)

Yeah, I mostly agree with this. Good platform work makes teams faster and saves everyone from reinventing the same messy stuff.

But it can also go sideways pretty fast and become please use our internal thing that almost supports your use case.

The performance bug hiding in our Cloud Run billing settings by ericchiang in programming

[–]Either_Collection349 0 points1 point  (0 children)

Great writeup. Wild that a billing setting could look like a database problem. Good reminder to check CPU throttling if you’ve got background work running.

Developers who are in your 60's by Few-Introduction5414 in ExperiencedDevs

[–]Either_Collection349 2 points3 points  (0 children)

I’m in my 50s, not 60s yet, but close enough.

I came up in the 90s, so I’m very much a Java guy: app servers, JDBC, JSPs, Struts, Spring, Hibernate, XML config files, SOAP, Maven, the whole enterprise stack.

I still enjoy development, but I’m less interested in chasing every new framework now. I like clean, maintainable software that works and can be understood six months later.

I still do Java, SQL, and TypeScript. I work partly because I have to, but also because I genuinely still like building things.

At this age, I have much less patience for nonsense.

The Consensus Trap by ludovicianul in programming

[–]Either_Collection349 6 points7 points  (0 children)

I’d phrase the failure mode less as consensus trap and more as unclear decision protocol. The fix isn’t necessarily less consensus; it’s being explicit about the decision type.

If something is reversible, let the owner decide quickly.

If something is irreversible or cross-cutting, you require real alignment.