Workflow
Pull Request Best Practices: Our Tips
Pull requests often go wrong. Learn and adopt our list of pull request best practices so that doesn’t happen to your team.
Carlos Schults
LinearB Blog
Eng. Metrics
How to Measure Technical Debt Before You Start Tackling It
Learning how to measure technical debt will allow you to make sound decisions when thinking about software quality. Learn how in this post.
Carlos Schults
Workflow
How to Do Code Reviews Better
Code reviews have become a vital part of the software development process. They improve code quality, developer performance, and save development teams time....
Brandi M.
Recommended Posts
1
Developer Productivity refers to the effectiveness...
Zach Westall
2
DORA metrics are a proven framework for measuring...
Ben Lloyd Pearson
3
Boost developer productivity and bottom-line...
Ben Lloyd Pearson
4
Eng. Metrics
Why Code Quality Is Important to Measure
What does high-quality code look like? Developers like to say that you know it when you see it. High-quality is free of code smells. Words like “elegant&#...
Otto Nagenast
Workflow
5 Ways to Use GitHub to Approve a Pull Request
The GitHub approve pull request process is very flexible. You can approve PRs in several different ways. Learn 5 of them in this post.
Carlos Schults
Leadership
A Clear Guide on Why and How To Do Value Stream Management
Value stream management (VSM) is one strategy you can use to enhance how your company builds software. Keep reading to learn more.
Justin Reynolds
Product
7 Simple But Effective Steps to Reduce Technical Debt
Tech debt is a metaphor, but it costs you real money. In this post, learn how to reduce technical debt with 7 simple steps.
Carlos Schults
Workflow
A Guide for Team Leads on Code Review Best Practices
Have you heard the old saying, “You can have something fast, cheap or good, but you can only pick two”? Software development is no exception. Code...
Nakia
Eng. Metrics
The Four Most Useful Value Stream Metrics in Software
What are the most useful value stream metrics? Here are four. See why cycle time, deployment frequency, and defects are the most helpful.
Eric Goebelbecker
