4 ms·
Is it really? It's another way of saying that conditions in the tech industry change every 2-3 years, which isn't all that controversial a statement.
by nostrademons 7y ago
Is it really? It's another way of saying that conditions in the tech industry change every 2-3 years, which isn't all that controversial a statement.
- discreteevent 7y agoSometimes it's because developers just want to change tech to enhance their cv or keep themselves entertained. That's scary. Sometimes it's rewritten because it's so unstable because debt wasn't paid off but total cost of writing it twice is much more than paying off as you go along. That's scary too.
- deleted 7y ago[deleted]
- mobjack 7y agoOften times if something needs to be rewritten, it means that the feature became popular enough that it needs to scale up. It is not a bad problem to have. Even well written code might not scale or be flexible to changing requirements. The feature could even be removed. The effort it took paying off tech debt prematurely would have been a waste.
- thrower123 7y agoI thought this was the old quote Fred Brooks quote, "Plan to throw one away; you will anyway." Although then you butt up against the "Second System Effect", so you're damned if you do, damned if you don't.
- nostrademons 7y agoWithin consumer tech, it's more like "Plan to throw it all away; you will anyway." I used to measure code lifetime in half-lives at Google: the half-life of most of the code there was about a year, meaning that after a year, 50% of your code will have been deleted. It's pretty accurate: by the time I left after 5 years, about 97% of the code I'd written had been deleted. Ironically, I'm told that my one contribution (after 10 years) that still exists is an attribute-renaming CL that I wrote over break at a team summit; basically the whole team agreed it was a good idea, we would never have a chance to fix the problem later, so I just went and did it before the framework got too entrenched to change. Meanwhile stuff I slaved over for months, sometimes even stuff that was directly sponsored by a VP (who is no longer there) or got commendations from the CEO (who is also no longer there) was gone within 1-2 years.
- collyw 7y agoIn my experience prototypes / proof of concpts always end up in production. Might as well make a half decent first attempt.
- JohnFen 7y agoI think that's a different statement, actually. Expecting code to be replaced every 2 or 3 years is nervous-making for a couple of reasons. First, new code is always less reliable than old code, so -- all other things being equal -- devs should lean toward keeping the old code rather than replacing it. Second, code should be architected so that any changes required to adapt to changing conditions should be limited in scope. The bulk of code for most projects should only very rarely need changing to adapt to changing conditions.
- nostrademons 7y agoYou're presumably used to operating in an enterprise environment with O(1000) customers and O(10) developers, not a consumer environment with O(100M) customers and O(1000) developers. Reliability issues at large consumer tech companies will usually be caught by the QA/canary/SRE process. If they're not, you'll hear about them soon enough with 100M users banging on the product, and then just do a rollback and fix it on a more leisurely pace. Consumer expectations in non-tech industries have gotten so low that you can burn down whole towns, poison people, and leak millions of records of personal data with few consequences to the company; not being able to access your favorite video for 15 minutes is comparatively minor. Also, the type of changes in market conditions consumer companies face are usually not those you can architect around. They include things like "We are no longer shipping DVDs to customers; we are streaming content online", "We no longer write web software, we're a mobile-first company", and "our business model is no longer selling personal data, it's payments". There is no architectural fix for "your product is canceled".
- JohnFen 7y ago> You're presumably used to operating in an enterprise environment with O(1000) customers and O(10) developers, not a consumer environment with O(100M) customers and O(1000) developers. I have a great deal of experience with both environments.
- user5994461 7y agoI have no idea what you're trying to say. O(1) and O(1000000) are the same thing, the O() notation ignores the constant factor.
- flukus 7y ago> Is it really? It's another way of saying that conditions in the tech industry change every 2-3 years, which isn't all that controversial a statement. I'd say it's an outright incorrect statement, fads come and go but the revolutions (like the move to web apps) are rare and take and take decades to complete. If everything around you changes every 2-3 years then you're hanging around fashionistas not engineers.
- alexandercrohde 7y agoUh... Really? The example at hand was netflix... The bulk of the platform seems pretty stable to me. If they are rewriting their best code every 2-3 years that'd be a red-flag to me.
- nostrademons 7y agoI worked on Google Search for 5 years. You would probably say Google Search is pretty stable - at least, when was the last time you noticed it go down? The half-life of code I worked on was about 1 year. Over a 2-3 year period, 75-90% of it would be gone. We did things like incrementally rewrite a million-line binary from C++ into Java while it was running, or completely change the indexing system from batch processing to continuous updating, or grow the number of documents indexed from about 80B to 1T. There's a huge iceberg of development that you don't see, much of which has to do with scalability (you generally have to rewrite every time a key metric grows by a factor of 10) and much of which is experimental, trying out new features to see what resonates with the userbase.
- markpapadakis 7y agoVery curious about what that Java program is.
- nostrademons 7y agoGWS (Google Web Server). Powers websearch, responsible for rendering everything you see when you run a search. It used to have a Wikipedia page but basically everything on the Wikipedia page was wrong so the admins eventually deleted it (edit: apparently it's back. Basically everything on the wiki page is still wrong, but at least it doesn't claim GWS is an Apache derivative now). It's the oldest continually-pushed binary at Google (originally written 1999 by Craig Silverstein; at least when I left it still had code in it from Craig, Marissa Mayer, and Sergey Brin). It's changed programming languages twice (from C to C++ around 2005, and from C++ to Java etc. around 2010), and when I left was a frankenmonster of C++, Java, and two proprietary DSLs. My understanding is that it still exists, though most of my friends at Google have since moved on to other teams.