tl;dr:Engineering teams are increasingly outsourcing non-core, yet critical parts of their stack to third-party vendors. This post delves into the challenges and emerging solutions of using third-party services in your stack. It discusses five key principles of modern developer tools: code-based resource management, source control management, rich type definitions, CI/CD integration and managing tools as part of your deployment lifecycle.
tl;dr:Engineering teams are increasingly outsourcing non-core, yet critical parts of their stack to third-party vendors. This post delves into the challenges and emerging solutions of using third-party services in your stack. It discusses five key principles of modern developer tools: code-based resource management, source control management, rich type definitions, CI/CD integration and managing tools as part of your deployment lifecycle.
tl;dr:"Here are the principles of the modern developer tool that emerged from our own work solving customer challenges, and that we're seeing in other developer tools we use." The authors discuss the following: (1) Work with resources in code. (2) Source control management. (3) Rich type definitions. (4) Run tests locally and in your CI workflow. (5) Manage as part of your deployment lifecycle.
tl;dr:Chris discusses his company's principles for shipping code: (1) Lean into trunk-based development. (2) Ship high quality so each feature "needs to feel cohesive, work near flawlessly, and be the best iteration of itself for it to be valuable." (3) Make it easy for everyone on the team to ship. (4) Keep a weekly changelog to include all of the features shipped over the past week. (5) Optimize for developer autonomy.
tl;dr:"To build a truly great developer tool you need to go beyond the default empathy that new engineers have for developers at large. You need to use the tool itself, exactly as a customer would." Chris shares Knock's onboarding principles, process, onboarding project and more.
tl;dr:Knock’s co-founder and CTO Chris Bell outlines the five principles they’ve used at Knock to ship value to customers every week and to create a culture of autonomy and ownership.
tl;dr:Chris discusses his company's principles for shipping code: (1) Lean into trunk-based development. (2) Ship high quality so each feature "needs to feel cohesive, work near flawlessly, and be the best iteration of itself for it to be valuable." (3) Make it easy for everyone on the team to ship. (4) Keep a weekly changelog to include all of the features shipped over the past week. (5) Optimize for developer autonomy.