Design systems are taking the tech industry by storm, but what exactly are they? Do you even need one? This week we’re talking all things design systems. We’ll chat about component libraries and style guides, companies who are building design systems, and more!
What you’re about to hear is a series of lightning chats recorded live from All Things Open 2019. How’s this for topic diversity? 👇
A/B testing, finding your tribe, dancing, TikTok, what is happening with front-ends becoming full-stacks, Code the Dream, OSI approved licenses, breaking in to tech, a11y, hiring juniors, whiteboard interviews, better interview practices, JPGs, coding bootcamps, tech re-entry programs, and more.
KBall catches up with Phil Hawksworth of Netlify at JAMStackConfSF to dive deep into JAMStack, what it’s about, where the ecosystem is going, and what is still hard.
KBall, Jerod, and Divya dig deep into how we learn. We look into how to choose what to learn, techniques for learning, and a set of respective resources.
JS Party co-host KBall just launched a new site:
Improve your career, your relationships, and your self-confidence by becoming a better communicator.
I’ve known Kevin for awhile now and I can assure you, the dude is an excellent communicator. This, from his newsletter, resonates 100% with me:
If there’s one thing that I can point to that has contributed most to my career success, it’s been my relentless focus on improving my abilities to speak in public, write coherently, and listen carefully.
We nerded out on this stuff back on JS Party #93. I heartily suggest listening to that if you haven’t yet.
KBall, Divya, Feross, and Jerod get together to discuss tips and tricks for communicating with other coders, project stakeholders, and users.
This episode is all about conferences and there is a lot to talk about! Why even go? What makes a conference worth it? How can you get the most of the experience? Is speaking worth all the effort? How can you make your talk amazing? How can you get your talk selected? We chime in on all of these questions plus more.
With the jumping off point of KBall’s question: “What are best practices for organizing a Node project?” Mikeal and Feross drop an incredible amount of wisdom about Node, organizing using modules, release management, deployment approaches, how to adopt change, and more.
KBall, Divya, and Chris talk about what’s going on in all the big frontend frameworks, share some pro tips, and shout out awesome people and things in the community.
We’re trying a brand new segment called YepNope, wherein your intrepid panelists engage in a lively debate around a premise. In this debate, Feross and KBall argue that websites should work without requiring JS and Divya and Chris say, “Nah!”
Please let us know if you like this style episode! We had fun recording it, but that doesn’t matter much if y’all don’t enjoy listening to it.
KBall and Nick sync up with Node.js core contributor Ujjwal Sharma to dive deep into how to get into the world of open source software.
KBall catches up with Florian Rival about bring a C++ based game engine to the web by compiling to WebAssembly and creating a React-based frontend.
KBall MC’d a live show at NodeConf Colombia with a panel of 4 experts from the Node community — Kat Marchán, Anna Henningsen, Ruben Bridgewater, and James Snell. It was a great discussion about the future of Node.js and the Node.js ecosystem.
Inspired by JSParty #70, 4 quick lessons on the philosophy of testing. The motivation?
Tools like Mocha, Jasmine and Jest have made writing tests far easier… But there’s still a gap. It’s extremely hard to find information on the philosophy of testing. What to test and why. How much is enough? What type of tests should I be writing, and when does it fit into my process?
My personal favorite point is this one on the importance of looking for bigger picture patterns:
One of the great things about front-end development in 2019 is that despite the abundance of frameworks, we’ve also started to see some big megatrends that are true across frameworks. This is good news for developers because it means that as you go deep in one framework you can still pick up skills that will translate to others if need be.
Jerod, Suz, Divya, and Kball share their thoughts, opinions, and advice on developer strengths and weaknesses — compromise, communication, tool mastery, deep dives into dev history, and mentorship/sponsorship.
Our initial impressions of GitHub’s recently announced package registry, what JS skills are trending in job listings, and shout outs!
KBall, Emma, and Chris explain some things to each other like we’re five, bring stories of the week, and share some sweet pro tips.