Have you ever noticed how back in the old days of everyday computing computers used to just work? Bugs were unheard of, crashes never happened and everyone was happy. Nowadays it would seem everyone simply works around the bugs because they're expected and part of our everyday lives, crashing happens so often even your 70 year old grandfather knows he simply has to press The Key Combination and memory leaks are so commonplace everyone and their mother reboots computers when they get kind of slowish.
But why is this? WHY I ask? Why is it that with computer science booming like never before, with thousands of talented young programmers, with dozens of old tricks up everyone's sleeves, computers and their software just keep getting worse and worse? Bad design decisions are being made every day, bugs are solved years too late, sometimes never, and crashing is becoming so common certain software is just taking it for granted and is designed to work around crashes (I'm looking at you Google Chrome and IE8!). Why does this seem necessary? Is it really so much easier to make software work around bugs rather than resovling the bloody bugs in the first place?
The system is broken, computers are going to hell, and users have simply learnt to live with it. This makes me sad.
Continue reading about Computers used to work in the 90's
Semantically similar articles hand-picked by GPT-4
- Coding is bad for you
- Don't Worry; It's a Compiler Bug
- Python multiprocessing is fucking sweet
- Some life advice I learned from computer science
- Don't neglect your upgrades
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️