frontend
Wrapping Up the Decade: What I Hope Front-End Learns Next
Thoughts from the intersection of code, craft, people, and progress.
Ten years of tech, and the core lessons still apply.
The last decade gave front-end development extraordinary capability and a corresponding number of ways to centre a div. For the next one, I hope we keep the ambition while paying more attention to resilience, accessibility and whether the complexity is actually helping users.
Predictions are most useful when they reveal what we value now. I am less interested in guessing the winning tool than in asking whether the web ahead will be more capable, more humane and easier to build for.
I have learned to be suspicious of advice that only works in a tidy example. Real projects come with history, deadlines, uneven confidence and requirements that move while you are looking at them.
Prefer the thing that survives contact
Front-end work has a habit of looking simple from a distance. The browser then introduces real content, small screens, old devices, keyboard navigation and somebody using the product in a way nobody drew in the design file.
That is why I favour choices that are easy to inspect. Start with semantic HTML, let CSS do the layout work it was designed for, and add JavaScript where it creates genuine value. Cleverness is occasionally useful; legibility is useful every day.
The best front-end code does not show off. It makes the interface feel obvious.
The web is wonderfully forgiving, but users should not have to rely on that forgiveness. Build from sturdy foundations and the interesting parts become much easier to enjoy.
There will always be exceptions. The trick is to make them deliberate exceptions rather than habits nobody remembers choosing.