4 ms·
This is classical geek owning up. My first thought was, this is written with two purposes: 1) to prevent the average, non-technical person from understanding
by chadmaughan 14y ago
This is classical geek owning up. My first thought was, this is written with two purposes:
1) to prevent the average, non-technical person from understanding it ("Phew, I'm glad these guys are figuring out this stuff and not me - that's why I host with them. I don't even know what a 'dyno manifold' is!")
2) to show management how smart we are and that you still need us ("because who else is going to figure this 'routing mesh' stuff out if you fire those responsible for the outage")
A simple "we're sorry and we've given 10 lashes to the engineer performing the manual garbage collection" may have been a better approach.
Having said that, I still think Heroku is awesome.
- aiscott 14y agoRead up on the heroku architecture. These are the terms used. The manual garbage collection wasn't the problem. An unexpected data structure created by garbage collection wasn't handled in a fault tolerant manner.
- rhizome 14y agoI can guarantee you that the Heroku architecture uses an internal slang for common sysadmin concepts.
- dsl 14y agoAll the reading in the world will not change the fact they pick retarded names. Routing mesh? We call that a cluster of load balancers in the real world.
- aiscott 14y agoWell, shucks, wuts a load balancer? Sounds like some kinda doofus trying to keep a pile of shit on their head from tipping over. Jargon is jargon, and in my part of the world, you're what we call a dumb-ass. Or is that too retarded for you? Nah, I expect there ain't a name too retarded for you.