If your software runs on my device, you don’t get to treat my resources as free.
That’s mine.
You’re spending my CPU, battery, memory, and data plan. That’s my time and money.
Respect your users.
Burning server cycles isn't the same; the ethical bar for the client is higher.
Only a few days left to get 25% off my Web Component Engineering course.
Use code GOODTIDINGS25 before Jan 10:
bluespire.com/course/web-c...
Web Components, DOM, modern CSS, a11y, forms, design systems & more.
Merry Christmas!
"For to us a child is born, to us a son is given; and the government shall be upon his shoulder, and his name shall be called Wonderful Counselor, Mighty God, Everlasting Father, Prince of Peace."
- Isaiah 9:6
A festive red and green banner advertising the Good Tidings Sale with 25% Off the Web Component Engineering course.
The interactive learning experience showing the course table of contents, a learning video, an interactive demo, and associated reference materials.
I heard some folks missed my recent Web Component Engineering course sale, so I’m running one more:
✅ 25% off w/ code GOODTIDINGS25
✅ Through the 1st week of 2026
Web Components, DOM APIs, modern CSS, a11y, forms, design systems, tools, and more!
bluespire.com/course/web-c...
If you’ve been meaning to invest in your UI skills, this is a good moment: 25% off with code GRATITUDE25, now through Nov 30. 👇
bluespire.com/course/web-c...
It’s great for app and framework devs who want to really understand the platform, design system teams building component libraries, and anyone responsible for serious UI engineering.
You get 13 modules, 170+ videos, an interactive in-browser learning app (no local setup), runnable demos, slides, downloadable notes, and a certificate of completion.
This course is a deep, practical tour of the Web Platform: DOM APIs, Web Components, modern CSS, accessibility, forms, design systems, app architecture, tooling, and more.
🚀 I’m running a Thanksgiving sale on my Web Component Engineering course. Through Nov 30, you can get 25% off with the code GRATITUDE25.
bluespire.com/course/web-c...
Read the full post on my blog here:
eisenbergeffect.medium.com/default-isnt...
Default Isn’t Design.
Familiar feels true but often isn’t.
I wrote about the psychology (System Justification) behind framework monoculture, the quiet costs it creates, and a standards-first path that still meets teams where they are.
Reflex → Evidence → Contracts → Users.
Last night I timed a product page load taking close to 6 seconds. This was on a desktop computer on a fast connection.
I did a few tests on my mobile phone as well.
Several times, the home page was completely unresponsive.
One of the pages, I counted out loud to 30 before the content was visible.
There's no excuse for a distinguished engineer to be completely unaware of major performance problems that any customer can see and also unreceptive to discussion.
I have a feeling that if their leadership understood they were preventably losing millions of dollars...
And just to be crystal clear:
The issue was not the tech stack or the perf problems.
The issue was the lack of ownership, awareness, and receptiveness to solving big problems, particularly coming from the Distinguished Engineer and the Principal who interviewed me.
Egregious.
I'm interested in building great things and helping others who are also interested in building great things.
I'm not interested in average.
I'm not interested in ok.
Great.
There were lots of red flags, but fortunately at this point in my career, I don't need to settle for mediocrity, deal with status quo crap, or endure toxic, broken culture. I will tell you straight up if I think you are making a mistake (tactfully and politely).
This was my 3rd interview, and prior to this no one had explained what this team was doing, what their stack was, their architecture, etc. The 2nd interviewer was from a different team and didn't know. The 1st interviewer gave me a different description.
(And no, this wasn't about Web Components.)
Eventually, I told them "Let's stop the interview, because unless you are open to me coming in and proposing changes around X, Y, and Z, then I don't think I'm a compatible candidate."
The interviewers "had not heard" of any performance problems, and did not seem open to my architectural criticisms or ideas on how to objectively improve the performance and scalability of their systems (based on my career experience working on similar solutions for multiple companies in the past).
I visited their customer facing e-commerce site on a fast internet connection with a fast machine, and it's a trainwreck (3s+ to load the home page). If the customer can see how slow your crap is, even on a high-end rig, then you have a problem! The evidence of the failure is there for all to see.
Well, I suppose it's no surprise at this point, but this group had picked the worst possible e2e architecture combination (100% perf/customer experience failure rate at every company I've seen it done at.)
And just because someone at a big company has a fancy title, doesn't mean they know what they are doing either. Often, especially if they have been at the company for a while, they are least able to think about the problem in a fresh way and find the best solution.
I had an interview for a Distinguished Engineer role at a big company yesterday...
It convinced me once again that most big companies don't know how to do quality, performance mature engineering.
Sure. Incoming...
Here's the link where you can get my course with this huge discount!
bluespire.com/p/web-compon...
Don't miss it. I won't have a discount like this again soon.
Group rates and PPP pricing available. Just reach out.
A screenshot of the interactive learning app showing 4k video teaching, interactive code, reference and notes, and a portion of the course's table of contents.
Hey friends! 🚀
I’m running the biggest sale ever on my Web Component Engineering course: 25% off through July 🎉
It’s full of hands-on, flexible training to help you build components, design systems, and apps. Use code SUMMERFUN to get it now!
(Link in the follow up.)
#webcomponents #frontenddev
I definitely have concerns that this might break various JS frameworks, and potentially a lot of bespoke solutions.
I wasn't aware of this. This seems like a major breaking change, if true.
The problem isn't that AI is actually capable of replacing software engineers.
It isn't. Not even close.
The problem is that there are a bunch of ignorant, foolhardy people in leadership positions who *think* that AI can replace software engineers.
This is causing real harm.
I’d be on board with that.
