3 ms·

Don't get me wrong, its plausible, but like why was this one guy able to replace everyone? yes he was faster and junk, but like what the fuck were all of you do

Don't get me wrong, its plausible, but like why was this one guy able to replace everyone? yes he was faster and junk, but like what the fuck were all of you doing? How was he able to replace an entire stack in less than a month without introducing huge amounts of logical errors? The "healthcheck" that is provided is just junk. It gives you app uptime, great, but that's _useless_ without context. Oh its neat, but also fucking pointless. I'm not a node person, but you can write the same thing is ~12 lines of node. Is this AI slop with some rage bait sprinkled in?

sshine 1y ago
> what the fuck were all of you doing? Hotfixing fires caused by brittle software, causing more brittle software. > How was he able to replace an entire stack in less than a month There weren't hundreds of thousands of lines of code. The conceptual model was already mature and well-understood. So there was little new understanding to be gained, only fixing bugs in a second iteration. > without introducing huge amounts of logical errors? Supposedly by being a good engineer who tests things against the existing solution and new tests. > The "healthcheck" that is provided is just junk Yes, the whole story seems made up. A moral of the story may be: Build huts with mud, and skyscrapers with steel. There are so many historical precedents to suggest that rewriting anything from scratch is extremely risky. This story, while it may be fake, suggests that you shouldn't altogether abandon the idea and live in mediocrity. As a person without a huge amount of legacy risk on my shoulders, I like that.
mingus88 1y ago
I didn’t read the whole thing because login but yes, firing the whole team thanks to one rockstar is the most braindead bit of management I have ever heard Let’s say it’s easy to replace those people with Rust engineers (it isn’t) Lets say there were no critical bugs introduced in a total rewrite (there almost certainly were) Let’s say that morale among the rest of the org won’t instantly nosedive because a whole team got canned over architecture decisions they had no part in (it will) Are we to believe that this unicorn 10x Rust engineer wont instantly be bored out of their skull because now that the team is gone there is no one left to maintain the devops pipelines, write all the docs and runbooks, and all that tedious stuff that any regular team handles? How long until this rockstar unicorn ninja bails for another fun Rust from scratch project elsewhere?

sshine 1y ago

> what the fuck were all of you doing? Hotfixing fires caused by brittle software, causing more brittle software. > How was he able to replace an entire stack in less than a month There weren't hundreds of thousands of lines of code. The conceptual model was already mature and well-understood. So there was little new understanding to be gained, only fixing bugs in a second iteration. > without introducing huge amounts of logical errors? Supposedly by being a good engineer who tests things against the existing solution and new tests. > The "healthcheck" that is provided is just junk Yes, the whole story seems made up. A moral of the story may be: Build huts with mud, and skyscrapers with steel. There are so many historical precedents to suggest that rewriting anything from scratch is extremely risky. This story, while it may be fake, suggests that you shouldn't altogether abandon the idea and live in mediocrity. As a person without a huge amount of legacy risk on my shoulders, I like that.

mingus88 1y ago

I didn’t read the whole thing because login but yes, firing the whole team thanks to one rockstar is the most braindead bit of management I have ever heard Let’s say it’s easy to replace those people with Rust engineers (it isn’t) Lets say there were no critical bugs introduced in a total rewrite (there almost certainly were) Let’s say that morale among the rest of the org won’t instantly nosedive because a whole team got canned over architecture decisions they had no part in (it will) Are we to believe that this unicorn 10x Rust engineer wont instantly be bored out of their skull because now that the team is gone there is no one left to maintain the devops pipelines, write all the docs and runbooks, and all that tedious stuff that any regular team handles? How long until this rockstar unicorn ninja bails for another fun Rust from scratch project elsewhere?