Nick Basile

Prepping my JavaScript for Designers course! After lots of iterations, I feel like I've finally cracked how to sequence all the JS content so it just clicks right away for designers 😁 We're up to 6 sections and over 50 lessons--can't wait to start filming!

How do product designers keep up with today’s ever expanding list of responsibilities? On the season two premiere of Technically Lit, I sat down with Sylvia Nguyen Dang, Principal Product Designer at DIG, to explore this question and a whole lot more.

If you’re a designer, PM, or builder trying to figure out how to keep up with all the change, this one’s for you. 📺 Watch here → youtu.be/iZ16iS9I7Dc

How do product designers keep up with today’s ever expanding list of responsibilities? On the season two premiere of Technically Lit, I sat down with Sylvia Nguyen Dang, Principal Product Designer at DIG, to explore this question and a whole lot more.

Sylvia shares what it’s like to design at the intersection of healthcare, technology, and collaboration while navigating the flood of new tools without losing sight of what matters most: the people you're designing for.

Our latest Tech Take episode gets into one of the most overlooked parts of product design: loading states. As designers, we love to obsess over finished screens, but the in-between moments are where trust is built (or lost).

If you’re a designer who wants to understand the real interplay between design and development, this one’s for you. Check out the full episode here and let us know what you think! www.youtube.com/watch?v=qa5n...

Our latest Tech Take episode gets into one of the most overlooked parts of product design: loading states. As designers, we love to obsess over finished screens, but the in-between moments are where trust is built (or lost).

It's often where design intent meets dev reality. Miss the mark, and the product feels clunky or broken. Nail it, and even a 10-second wait feels intentional.

Our latest Tech Take episode gets into one of the most overlooked parts of product design: loading states. As designers, we love to obsess over finished screens, but the in-between moments are where trust is built (or lost).

And… that’s a wrap for season one of the Technically Lit podcast! Thank you so much to all of the incredible guests who joined us on the show. I feel so lucky to have had the chance to speak with each of you.

Thank you as well to everyone who has taken the time to listen or watch one of our episodes. Your kind feedback truly means the world and makes it all worth it!

And… that’s a wrap for season one of the Technically Lit podcast! Thank you so much to all of the incredible guests who joined us on the show. I feel so lucky to have had the chance to speak with each of you.

Looking forward, I’m so incredibly excited to be kicking off season two! This season, we're going to focus a little bit more on product designers - specifically, how they're leveraging technology and coding skills to do their jobs better, faster, and smarter than ever before.

And… that’s a wrap for season one of the Technically Lit podcast! Thank you so much to all of the incredible guests who joined us on the show. I feel so lucky to have had the chance to speak with each of you.

Most of our Technically Lit conversations have been with people building in scrappy startup environments. That’s why I’m so excited for our latest episode with Adam Wilson who brings a very different perspective straight from Microsoft.

Adam also shared how his technical background has been a superpower. Early in his career, he was writing code to replicate customer bugs. Today, that fluency lets him navigate Microsoft’s most complex products and collaborate deeply with engineering teams.

Most of our Technically Lit conversations have been with people building in scrappy startup environments. That’s why I’m so excited for our latest episode with Adam Wilson who brings a very different perspective straight from Microsoft.

Stop thinking perfect code = a great product. Your team ships clean architecture. You polish the UI until it gleams. You document every edge case. But none of that guarantees you’re building something users actually need.

– Most founders underestimate how hard product design really is. The “what now?” moments for users take far more thought than you expect. – Cross-functional collaboration is the antidote to the “us vs. them” tension between product, design, and engineering. Squads work better than silos.

Stop thinking perfect code = a great product. Your team ships clean architecture. You polish the UI until it gleams. You document every edge case. But none of that guarantees you’re building something users actually need.

Our conversation was jam-packed with so many incredible insights, I had a hard time picking what I should share as the lead-in here. These are a few of my favorites:

Stop thinking perfect code = a great product. Your team ships clean architecture. You polish the UI until it gleams. You document every edge case. But none of that guarantees you’re building something users actually need.

Tomorrow’s Technically Lit newsletter dives into a question I’ve been obsessed with: what actually makes a great product team and how you can spot them. We’re now on Substack, so if you want the full breakdown (and future issues) grab the link in the comment 👇

Stop confusing process with culture. Your team does standups. You run retros. You’ve got a Notion doc for everything. But a full calendar and all the docs in the world won't magically translate into a stellar culture.

You can’t Notion your way out of bad vibes. You build real culture by: ✅ Modeling curiosity ✅ Rewarding transparency ✅ Cultivating psychological safety, not fear ✅ Treating mistakes as inputs, not failures

Stop confusing process with culture. Your team does standups. You run retros. You’ve got a Notion doc for everything. But a full calendar and all the docs in the world won't magically translate into a stellar culture.

As Ryan Holdaway said on this week's Technically Lit podcast: “Process is how we work. Culture is how we treat each other.” Most teams miss this. They try to fix trust issues with better tooling. Or fix communication with more meetings.

Are product and marketing the ultimate frenemies? Different tools. Different timelines. Same goal: build something people actually want. And when they don’t get along? Everything breaks. 🧵

We got into: 🤝 How product and marketing can finally stop stepping on each other’s toes ⚙️ The GTM operating system that actually works for early-stage teams 📉 Why “growth loops” became buzzwords, and how to make them real again 🧠 Building marketing systems that learn, not just launch

Are product and marketing the ultimate frenemies? Different tools. Different timelines. Same goal: build something people actually want. And when they don’t get along? Everything breaks. 🧵