I build something to reason through the calls a senior would make.
How to build an autocomplete combobox that searches for people on a server, prevents outdated search results from appearing, and ensures the form submits the person displayed in the field.
How to render a Markdown comment safely in every place it shows up, with one policy for setHTML() and DOMPurify, and Trusted Types to catch code that writes the comment with innerHTML instead.
How to build a small router on the Navigation API that keeps the URL, the content, focus, and scroll in agreement, even if the user presses Back before a page finishes loading.
CSS can finally style a real select, picker and all. The opt-in also takes over the phone's own picker, so the job is scoping it to the devices where your design is the better one.
Swap a card's viewport media query for a container query the host establishes, find the breakpoints its content needs, and keep user preferences and product intent in the mechanisms that own them.
A practical way to evaluate a frontend technology as a long-term commitment, from how much of your app it takes over to what replacing it would cost, with my own decision to build on Lit as the example.
Payroll data shows 22 to 25 year old developers losing ground while every older group holds. This is the whole plan I give anyone trying to get in, a deployed portfolio held to three checks, what a certification proves that a project can't, meetups and hackathons in person first, and a search you can diagnose.
Speculation Rules can load the next page before the click, and cross-document View Transitions can animate the swap between two real HTML documents. This is how a static site navigates like a single-page app without shipping one, plus the confidence policy that decides which links earn a prerender.
The two best-known fixes for a slow list solve different problems and cost you different things. Measure which cost you're actually paying, then keep the DOM with content-visibility: auto or drop it with a virtualizer and rebuild the behaviors that disappear with it.
Two official databases scored the same Vite bug 5.3 and 7.5. Read the advisory field by field, untangle CVE, GHSA, CWE, and CVSS, check whether your own system is exposed, and time the update with npm's release-age gate.
