I started using Angular a few months ago. I hated it. Backbone was so much better.
And I never liked how much logic Angular hides from you. When I work on something, I want to understand the whole system. Having a bunch of "Here be dragons, don't go here" signposts everywhere feels weird.
How can you reason about your code if half of it is hidden?
There was a case where I spent a whole day chasing down a bug because of that. When you clicked on a thing an unrelated thing cried out in pain and the app crashed.
Turns out Angular was messing up the event cycle and tried to update something before a different thing made it ready to be updated. Yes, very descriptive, I know. But Angular's "This thing can't be called, derp" was super helpful too.
Had to wrap a bunch of code in
The past few weeks I poked at Backbone again. My love.
And you know what, I can't argue with results. Despite everything I hate about Angular on a philosophical level, it gets the job done. Fast.
Getting stuff done with Angular is just so much easier. Especially the simple stuff that I don't want to think about. Want something to be visible or not?
ng-show. Want to display a value to users?
And so on.
All these trivial little things that, yes, are simple, and, yes, I can code in my sleep, but with Angular I don't have to. It takes 10 seconds with Angular, 3 minutes with Backbone.
Who cares right? It's only 94% quicker. Oh ...
It adds up, man. It really does.
And because I don't have to care about these tiny things, I get to spend more brain cycles on the main logic. It even leaves enough time to deal with the millions of steps of responsibility misdirection between the various controllers.
onclick= ten years ago?
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. 👌"
Senior Mindset Book
Get promoted, earn a bigger salary, work for top companiesLearn more
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
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
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️