Back to Course Practices of a Graceful Developer 0% Complete 0/0 Steps Practices for Design & Implementation 10 Topics Functional Mockup Do the Work The TOO HARD Code Smell Don't Use Greater-Than README-Driven Development Ship first, then code Hammers And Diapers Consistency Immediacy Aggregate Boundaries Testing Mindset 2 Topics TDD is easy! - with Michal Taszycki Risk-Oriented Testing Working Together 10 Topics Getting the Lay of the Land in an Unfamiliar Project Breaking Down Complex Pull Requests with Claudio Baccigalupo Pull Request Template - Andy Croll Git Storytelling - Part 1 Git Storytelling - Part 2 Git Storytelling - Part 3 Git Hooks for Evil and Good Asking for help ... - Jim Remsik Working Together Construct shared understanding together The Graceful Career 3 Topics Learning from the Wider Developer Community with PJ Hagerty Pitch a Plan, not a Promotion Refactoring for Interviews - Nickolas Means Conclusion and Next Steps Search (Entire Site)Search Practices of a Graceful Developer Practices for Design & Implementation Ship first, then code Module 1, Topic 6 In Progress ← Previous Next→ Ship first, then code Module Progress 0% Complete Part of README-driven-development is prioritizing delivery over getting something working on our own machine. In today's video, Jessica Kerr demonstrates this concept using an NPM example. Oop, this content isn't available to visitors. Please register or log in to continue! Responses You must be logged in to post a comment.