this post was submitted on 23 Jul 2023
180 points (100.0% liked)
Technology
37739 readers
782 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
His utter lack of understanding about how SAaS companies work is astounding. Having worked on the backend of several, they’re all hot garbage and brittle. That’s why there were so many “useless” engineers. You know, the ones he shit canned when he acquired the company? Surprise, they were probably the only reason the dumpster fire wasn’t burning down the whole city block. The thing Elon fails to understand is that someone didn’t just write Twitter on one go and gift it on to the world. It has evolved over many many years. Technology stacks change, frameworks change, standards change and these companies are trying to continually add features to applications and don’t have the luxury of just rewriting the whole stack every time something new comes out. The end result is something that is often more akin to a living organism than a website or application. He probably thinks Twitter is some program running on every server that can just be rewritten and replaced. I can’t wait for the day they try to replace it and it ends up setting Twitter back a decade.
This is your brain on Great Man Theory. ~Strawberry
He did actually say at once point about scraping all the code base & starting from scratch!
Software Developer pro tip: Never ever get involved in any effort to rebuild the old system in new tech.
Make a new, smaller system to take new market instead of the old system? Good.
Suffer for years through an endlessly growing checklist of things that must be in this new thing because they were in the old thing? Arguing with sales whether you have to again rush out a fix for a customer that is important and absolutely depend on this integration with Microsoft Bob that nobody in the dev team even knew existed in the old system until the customer complained? Have release schedules set years in advance and constantly pushed because this thing will never ever ever be accepted as a replacement of the old system? Bad.