Category: Git
-
The Dangers of Rubber Stamping a Git Pull Request
Rubber stamping involves a developer skimming push request reviews and approving them without a substantial review of the request. Typically, this happens when a more senior team member submitting code will not be challenged by a reviewer who assumes the work will be good enough. However, this can also become a habit when a team…
-
Scope Creep in Git Projects: What to Do
Everyone knows what scope creep is – and what repercussions can happen if it is left to spin out of control. There are a lot of different definitions. In this case, let’s focus on what happens when the original scope changes (or grows) after implementation has already begun. Very often, scope creep can happen slowly,…
-
How to Avoid Sub-Par Product Ownership
Sub-Par product ownership usually shows up in one of two ways: However, it may be a challenge to recognize the signs. Here’s how. Recognizing the Signs of Weak Product Ownership If you’re facing sub-par ownership, you’ll notice the pattern when you begin to experience recurring scope creep that’s driven by the same owner(s). One way…
-
Give Your Git Developers a Sense of Ownership in the Code
Do you have an engineer that hops, skips, and jumps all over the codebase? You likely will notice how they’ll move from front-end issues to refactoring to switching over to another area of the database. You might even see that their submissions are never really challenging problems. Typically, it’s helpful if a developer isn’t relegated…
-
If Engineers Refining Git Code as They Go, Encourage it!
Your codebase is a continuously evolving organism. However, it develops, not across its entire base at once. Instead, it changes unevenly here and there over time. There are some engineers, however, that will take it upon themselves to clean and refine as they go, even if it’s not an essential task. If encouraged, this can…
-
How to Maximize Consistent, High-Quality Performers on Git
If you are lucky enough to have a developer – or a number of developers – that consistently turn in high-quality work week in and week out, don’t be afraid to celebrate them. Also, figure out how they do what they do, and see if you can replicate that across your team. What is a…
-
If Your Developer is Overanalyzing, Here’s What to Do
Do you have a developer that is getting hung up on a specific area of code? Maybe they’re entirely focused on a single area for a very long time while seemingly not making that many changes. They could be trapped in a problem they can’t resolve, and if you don’t deal with it head-on, you’re…
-
Is Overhelping in Git Causing Issues Among Developers?
Collaboration across your team is excellent. It’s a natural process, especially when working with Git, as the entire platform is designed to have everyone work in tandem and collectively check commits, submit pull requests, and ensure the best code is being put forward for every project. That said, over helping can happen. Overhelping is when…
-
Don’t Just Look for Problems in Git Commits. Celebrate Wins, Too
When reviewing code, we’re often so focused on finding problems that we forget to zero in on those within the team submitting perfect commits. When your developer understands the issue at hand, breaks it into smaller tasks, and presents near-perfect code, remember to take a moment to applaud them. Taking note not only buoys the…