Product delivery is simple and complex, all at the same time. The issue is that we always want 3 dimensions of delivery. We want it: Quickly, Bug-free, All the “important” features. The problem is that you can only deliver on 2 of the 3 at the same time.
Most software engineers start by thinking about the code. Instead, start with the why so you solve the right problem the first time.
Every software engineer has that moment. You are assigned a feature requirement. It could be a Jira ticket or a sticky note. You first start brainstorming if this is possible, how you would achieve it, and how much time it might take. But before you start thinking through the technical implementation, you need to step back and ask "why"?
🎙 WebJoy, Season 1, Episode 17 (Sep 22, 2022)
Joe Natoli joins the show to talk about his origin story, how he started in design before the internet was a thing. How he jumped into designing for the internet early on and ultimately realized real fulfillment comes from helping people learn.
🎙 Code Newbie, August 2022
In this episode, we talk about documentation, with Eddie Hinkle, lead front-end engineer at Glassdoor, and host of the WebJoy podcast. Eddie talks about what documentation means in the context of development, why good documentation is so important, and how gaining good documentation skills early on can give you an edge in your career.