If you’re trying to break into software engineering right now, in 2026, in the age of AI coding assistants, you need to understand something: the bar hasn’t just moved. It’s been launched into orbit.

Our State of the Designer report explores how designers around the world are upleveling their skills, keeping craft high, and turning new pressures into creative momentum.

Unlike the scrollable scroll-state queries, scrolled remembers the last direction you scrolled into, which you can use to build “hidey bars”: when scrolling down (or having scrolled down), the hidey bar hides itself. When then scrolling back up, the hidey bar reveals itself.

It’s mostly CSS! A li’l JS sprinkle just to position the ::picker() and the selected option together; the JS is nice to have, CSS does the real work.

If you want to continually refine your website-building skills and deliver better end products, performance, UX/UI quality, and workflow efficiency all matter deeply. As with many aspects of our digital lives, web design requirements, tools, and techniques are constantly evolving.

Everybody who routinely takes screenshots on a Mac knows very well the motor memory heaven and hell that are the screenshotting shortcuts: ⌘⇧3 to grab the whole screen, ⌘⇧4 to grab part of it, hold ⌃ ahead of time to put the result in the clipboard, press space at the right moment to select a window, hold ⌥ at a different time to remove a shadow, and so on. (Yes,…

Learn how UX and product designers are adopting AI—from tools and workflows to challenges, impact, and predictions for the future of design.

Logos stayed fixed, color palettes were locked down, and typography rules were carefully controlled to avoid variation.

The “Productivity Paradox” is officially here. In early 2026, we’ve seen that high-velocity code generation without architectural oversight leads to massive technical debt. As senior developers, we’re moving away from simple autocompletion toward local-first AI coding agents that offer transparency and data sovereignty.

Prescriptive class name conventions are no longer enough to keep CSS maintainable in a world of increasingly complex interfaces. Can the new @scope rule finally give developers the confidence to write CSS that can keep up with modern front ends?