Measured, not eyeballed
I spent a career going under the covers of the software I use: finding out how things actually work, where performance excels, where it suffers, and then teaching what I learned to other people.
This blog is that habit, written down.
The posts here follow one rule: measured, not eyeballed. Claims come with numbers, numbers come with method, and when I did not verify something, I say so. Expect deep dives on frontend mechanics: how frameworks schedule work, what change detection actually costs, why some architectures age well and others accumulate debt in installments.
First real post coming soon: what an Angular-shaped mind needs to know when learning React.