Performance is part of the product.
Fast software doesn't just benchmark better. It feels better.
About the observer
I'm a software engineer who likes the parts just beneath the surface.
Rendering, browser behavior, architecture, performance, tooling, and the small decisions that make software easier to live with tend to hold my attention longer than they probably should.
Most of my day-to-day work is on large customer-facing web applications, particularly e-commerce systems. I like software that feels simple because somebody took the time to deal with the complicated parts.
Things I've written down and kept
Notes from the margins
Good abstractions remove work.
If an abstraction mostly gives us more vocabulary to remember, I'm not convinced it helped.
Learn the system, not just the framework.
Framework knowledge expires. Understanding rendering, state, networks, browsers, and software design tends to stick around.
A finished thing teaches you what a prototype can't.
The awkward parts usually don't introduce themselves until somebody actually has to use it.
Own the outcome, not just the ticket.
The implementation is only part of the job.