Michael Stanaland
@thatmichael.bsky.social
Frontend development 🤝 Design 🤝Accessibility
Reposted by Michael Stanaland
I just made a thing:
A collection of links for web developers to navigate the web platform more easily.
🟢 Places to follow progress and keep track.
🟣 Places to make your voice heard and influence the platform with your use cases.
A collection of links for web developers to navigate the web platform more easily.
🟢 Places to follow progress and keep track.
🟣 Places to make your voice heard and influence the platform with your use cases.
Navigating the Web Platform Cheatsheet
As a web developer, navigating the web platform isn't always easy. Here are ways to keep track of what you can use, of what's new in web browsers, and ways you can influence the development of the…
buff.ly
February 18, 2025 at 8:02 PM
I just made a thing:
A collection of links for web developers to navigate the web platform more easily.
🟢 Places to follow progress and keep track.
🟣 Places to make your voice heard and influence the platform with your use cases.
A collection of links for web developers to navigate the web platform more easily.
🟢 Places to follow progress and keep track.
🟣 Places to make your voice heard and influence the platform with your use cases.
Excited by all the new cool chrome CSS stuff, but then I remember I have to wait for Safari and Firefox and then enough years to pass for the usage stats to be high enough to be able to use these features at work. Have fun (maybe) 4 years from now future Michael!
January 17, 2025 at 11:11 AM
Excited by all the new cool chrome CSS stuff, but then I remember I have to wait for Safari and Firefox and then enough years to pass for the usage stats to be high enough to be able to use these features at work. Have fun (maybe) 4 years from now future Michael!
Remember to always read Daring Fireball's footnotes. Often there's real firecrackers in there and they bring me joy
December 12, 2024 at 1:04 PM
Remember to always read Daring Fireball's footnotes. Often there's real firecrackers in there and they bring me joy
Reposted by Michael Stanaland
🌠 The best icon pack in the world right now, IMO, is Lucide (lucide.dev).
It builds on @colebemis.com’s incredible work with Feather Icons, extending it from ~300 icons to >1500.
It has fully-typed bindings for React and many other frameworks. And I just found out: they’re even more optimized! 🧵
It builds on @colebemis.com’s incredible work with Feather Icons, extending it from ~300 icons to >1500.
It has fully-typed bindings for React and many other frameworks. And I just found out: they’re even more optimized! 🧵
November 20, 2024 at 3:52 PM
🌠 The best icon pack in the world right now, IMO, is Lucide (lucide.dev).
It builds on @colebemis.com’s incredible work with Feather Icons, extending it from ~300 icons to >1500.
It has fully-typed bindings for React and many other frameworks. And I just found out: they’re even more optimized! 🧵
It builds on @colebemis.com’s incredible work with Feather Icons, extending it from ~300 icons to >1500.
It has fully-typed bindings for React and many other frameworks. And I just found out: they’re even more optimized! 🧵
Reposted by Michael Stanaland
Confused about the `exports` field in package.json?
I wrote a guide to break it down and walk you through it!
👉 hirok.io/posts/node-exports-guide
I wrote a guide to break it down and walk you through it!
👉 hirok.io/posts/node-exports-guide
Guide to the Node.js `exports` field
Take control over how your npm package is accessed with the package.json `exports` field
hirok.io
November 15, 2024 at 12:23 PM
Confused about the `exports` field in package.json?
I wrote a guide to break it down and walk you through it!
👉 hirok.io/posts/node-exports-guide
I wrote a guide to break it down and walk you through it!
👉 hirok.io/posts/node-exports-guide
Sitting quietly listening to product owners try to turn updating 6-year-old depreciated dependencies and fixing 20 second LCPs into “value for the client” statements for leadership might be the end of me
November 14, 2024 at 8:08 AM
Sitting quietly listening to product owners try to turn updating 6-year-old depreciated dependencies and fixing 20 second LCPs into “value for the client” statements for leadership might be the end of me
Reposted by Michael Stanaland
Software is HARD. Especially large, complex software. It always has been. Developers write shitty code because writing non-shitty code takes discipline, deep understanding, and immense coordination across a team.
React is not the cause of crappy web apps. Software is. No framework can fix that.
React is not the cause of crappy web apps. Software is. No framework can fix that.
November 13, 2024 at 5:56 PM
Software is HARD. Especially large, complex software. It always has been. Developers write shitty code because writing non-shitty code takes discipline, deep understanding, and immense coordination across a team.
React is not the cause of crappy web apps. Software is. No framework can fix that.
React is not the cause of crappy web apps. Software is. No framework can fix that.
Nice! This is great for peace of mind. I’ve always been really scared of “free until it’s not” services when you can’t really control the usage
A free plan to help get you started. No overages, no strings. Deploy your personal sites, or other creative explorations and grow when ready. www.netlify.com/blog/introdu...
Introducing Netlify’s Free plan
Deploy web projects with Netlify’s Free plan. Get 100 GB bandwidth, CI/CD, serverless functions, and more. No credit card required, no surprise charges. Start building today.
www.netlify.com
November 12, 2024 at 9:22 PM
Nice! This is great for peace of mind. I’ve always been really scared of “free until it’s not” services when you can’t really control the usage
Moved a repo from Jest to Vitest today and ... it didn't suck! Vitest UI really helped me move quickly through the tests that needed modification. Struggled with types though. Do we really have to keep `@types/jest` around?
November 7, 2024 at 8:16 PM
Moved a repo from Jest to Vitest today and ... it didn't suck! Vitest UI really helped me move quickly through the tests that needed modification. Struggled with types though. Do we really have to keep `@types/jest` around?
Reposted by Michael Stanaland
🌠 For years, the #1 most requested feature in CSS was Container Queries. We wanted them so badly!
Well, they’ve arrived… and none of us are using them. 😂
I think I know why, and I just published a new blog post that will hopefully change that!
Check it out:
www.joshwcomeau.com/css/containe...
Well, they’ve arrived… and none of us are using them. 😂
I think I know why, and I just published a new blog post that will hopefully change that!
Check it out:
www.joshwcomeau.com/css/containe...
A Friendly Introduction to Container Queries • Josh W. Comeau
It’s been a couple of years since container queries started landing in browsers… so why isn’t anyone using them? It turns out that container queries are kinda tricky; they’re not as straightforward as...
www.joshwcomeau.com
November 4, 2024 at 4:36 PM
🌠 For years, the #1 most requested feature in CSS was Container Queries. We wanted them so badly!
Well, they’ve arrived… and none of us are using them. 😂
I think I know why, and I just published a new blog post that will hopefully change that!
Check it out:
www.joshwcomeau.com/css/containe...
Well, they’ve arrived… and none of us are using them. 😂
I think I know why, and I just published a new blog post that will hopefully change that!
Check it out:
www.joshwcomeau.com/css/containe...
Reposted by Michael Stanaland
If we want BlueSky to be fresh start then WE need to start fresh too, that means we need to be intentional about how and when we engage.
Let’s build a culture of unabashed positivity, radical gratitude, and constructive criticism.
We are all out of excuses here. We can’t blame ‘the algorithm’.
Let’s build a culture of unabashed positivity, radical gratitude, and constructive criticism.
We are all out of excuses here. We can’t blame ‘the algorithm’.
November 4, 2024 at 11:53 PM
If we want BlueSky to be fresh start then WE need to start fresh too, that means we need to be intentional about how and when we engage.
Let’s build a culture of unabashed positivity, radical gratitude, and constructive criticism.
We are all out of excuses here. We can’t blame ‘the algorithm’.
Let’s build a culture of unabashed positivity, radical gratitude, and constructive criticism.
We are all out of excuses here. We can’t blame ‘the algorithm’.