Generics, combined with conditional types can make for an incredibly powerful combination. When you look at things the right way, you can ask very useful questions about your types that allow you to build the precise API you want.
An underdog media query, resolution queries, comes to the rescue here in defining radial gradients that don’t blur or get the jaggies.
The web platform has a heaping helping of more design capability built into it than any design software does.
CSS module scripts help keep the dream of co-locating files that all relate to a component, without needing a bundler.
You can get your hands on ranges of text in JavaScript, then apply a named “highlight” on them, so you can style that range in CSS with no other selector necessary.
The whole point of auto-fit and auto-fill is that you aren’t saying how many columns to use. But if you knew how many the browser chose, you can make nice design decisions.
A row of logos that animate forever perfectly and don’t have any duplicated HTML or JavaScript at all is quite a trick. Thanks modern CSS!
One of the dev jobs out there is DevRel or “Developer Relations”. A role like that is very likely going to involve teaching and helping people learn a products API. And, if the company has one, SDK’s around that API. Can you articulate the difference between them? At a minimum, that would be good to be able to do for that job interview.
Emre Tezisci has a pretty good article explaining: APIs vs. SDKs: Key Differences, Use Cases, and Best Practices.
Another good one from Nicholas C. Zakas this time on code portability. Here’s some choices he made for a recent projects:
Portability indeed!
Nice reminder about JavaScript evolving to be more useful from Trevor I. Lasn:
// Old way (pre-2021)
if (user.name === null || user.name === undefined) {
user.name = 'Anonymous';
}
// Or using the nullish coalescing operator (??)
user.name = user.name ?? 'Anonymous';
// New way (ES2021 and later)
user.name ??= 'Anonymous';Code language: JavaScript (javascript)The final line there uses what is called the “The nullish coalescing assignment operator assignment operator” in case you need to impress people at parties.
One of the nice things about Markdown is that you can just… put HTML in there too. There is no Markdown shortcut for a <div>, but you can just use a <div>. That means you can use use <my-custom-element> as well, bringing the world of Web Components into your writing and creating of content.
What if you want a Markdown-friendly way to represent a feedback form, or a tabbed UI, or a mortgage calculator, or something else way beyond the scope of text formatting.
For these situations, what you really want is to put a token or a placeholder in your Markdown, and have something else expand it later on into a larger, more complicated HTML construct.
What you sort of need is… Markdown for More Complicated HTML™.
Enter Custom Elements.
If you want to put React components into Markdown, you’ve got MDX, but MDX can get Very Complicated™. If you just want to use Web Components in Markdown, well, Dave really said it best.
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.