A look at an example task an interviewer might give you and all the details of how you could approach and and what they are watching for.
Set a variable in Pug, then create an inline script which sets that variable for using in JavaScript and use setProperty to pass it to CSS.
Accordion details, toggle switches, styleable selects, responsive video, and more!
If you’ve applied `container` to an element, know that, for the next little while, that makes a new “formatting context” in Safari, and does not in Chrome or Firefox.
You can build your own TypeScript build process, and you might want to if you need true type checking and compatibility with a wider ecosystem of tools. But lots of tools, including now Node itself, just accept TypeScript as if it were JavaScript.
Why can’t we see if a feature is polyfillable or able to be progressively enhanced in the baseline data? There are reasons.
It’s quite fun to have an element react to another element scrolling in an unexpected way!
Jacob Voytko shares the tale of a very difficult bug to track down. It’s always interesting to get a little insight into how people go about narrowing down the scope of a bug. In this case, it narrowed all the way down to code you’d never guess would be the cause of the bug, but such is the nature of our work sometimes.
If you haven’t heard about the bug about the 500 mile limit on email, that’s a real classic.
The fourth issue of The HTML Review is out. Wonderful writing framed by entirely different and unusual interactive interfaces, brought to you by the power of web technology. A zine come to life.
Just try to pick a favorite.
Steve Yegge makes the prediction in Revenge of the junior developer that this current wave of AI “agents” that help us code with more capability than just type ahead suggestions and refactorings, like file creation, command line usage, and more, is just the fourth wave of six. The fifth is an individual developer managing multiple agents (a “cluster”) which gives way to “fleets” of agents in the sixth.
The revenge part? Junior developers, less stuck in their ways, will be quicker to adapt to these new ways of working. I think it’s interesting to think about, but my experience, the value of someone who deeply knows how to understand a system and fix and prevent problems, traits that define a senior developer, will remain as valuable as ever.
I enjoyed this blog post from Blake Watson about a simple requirement and then going down the rabbit hole of functional programming to solve it in increasingly reusable, if mind-bending ways. By the end:
Creating a function that returns a function that returns a function can get a little trippy to think about. But what we’ve done is make our work reusable and flexible.
Blake admits he didn’t actually use the fully functional abstracted functional version. I vibe with that. Take it as far as you can without sacrificing clarity.
Developer news, information, and advice — right to your feed reader of choice.
RSSHere's our page on guest writing. It's a win-win-win!
Frontend Masters donates to open source projects through thanks.dev and Open Collective, as well as donates to non-profits like The Last Mile, Annie Canons, and Vets Who Code.
