Swizec Teller - a geek with a hatswizec.com

    Why everything must change every five years

    You complain about JavaScript fatigue, and that's valid. The ecosystem moves fast, and it's hard to keep up. Dare I say impossible?

    But won't you think of the authors and the conferences and the speakers and the trainers and video course makers and everyone else working hard to teach you all the new things?

    A whole industry relies on new things coming out to confuse you!

    Why, if you're not confused about that new feature, who will come to our talks? Who are we going to teach?

    If a new framework doesn't come out to boil the ocean and replace everything that existed before it, who is going to buy the hundreds of books and video courses that we want to make?

    You can't make more sales if there's nothing new to sell. If you can't make more sales, how are you gonna pay rent? Hosting fees? Vacations in Bali?

    Sure –– hundreds, even thousands of people enter the field every day. People change jobs and become software engineers. People go from one type of engineering to another. People grow up and get their first jobs.

    The field is growing, and that's a good thing. You can sell your conferences and your books and your courses to the newcomers.

    But wouldn't it be nice if you could also sell them to everybody else? There's a lot more of everybody else.

    Software Engineering is growing at about 24% per decade. You can't build a training industry on that. Not a big one anyway.

    There's a whole other 76%! You can sell stuff to them.

    But you first need to get them confused.

    Invent a new frontend framework. Say that tables are bad and CSS rules all. 10 years later, turn CSS into tables. Double whammy!

    Create new bundlers and compilers and tell everyone that JavaScript must be compiled – it's really much better that way. Invent a whole new way to talk to backends because REST and Ajax are lame.

    Don't tell anyone that all these things are pretty much the same as always behind the scenes. You still need Ajax to talk to the backend, everything still turns into HTML in the end, and CSS still winds up a bunch of <style> tags no matter what bundler you use. 🤫

    It's the oldest play in the book. Invent something new, convince everyone it's better, watch a cottage industry spring up around it. Training, consulting, all the things.

    But really, we're all at the mercy of this. Sometimes, I think the big companies just have too many engineers with nothing to do so they keep coming up with new things.

    ¯\_(ツ)_

    Did you enjoy this article?

    Published on February 23rd, 2018 in Opinions, Personal, Thoughts,

    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. 👌"

    ~ Ashish Kumar

    Join 15,883+ engineers learning lessons from my "raw and honest from the heart" emails.

    ⭐️⭐️⭐️⭐️✨
    4.5 stars average rating

    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

    Want to brush up on modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    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 ❤️

    Created by Swizec with ❤️