Any advice for improving the quality of your software team’s pull requests before they head to review? Looking for ways to increase the quality of PRs across the board and reduce the changes needed.

Software Development Quality, Testing and Security

1.3k views2 Upvotes3 Comments

Sort by:

CTO in Software7 months ago

GitHub pre commit hooks that run local linters, test and other automatic checks before each commit.

Pair programming

Don’t do PR but go for trunk based approach:-)

Director of Engineering8 months ago

Practice methodologies such as Scrum which make each team member responsible for ensuring that their code is up to scratch before pushing it.

Senior Director Software Engineering8 months ago

Will answer at a high level, but happy to elaborate if helpful :)

1. Written standards, agreed on by the team, and an expectation that folks read them when they join the team, as part of a team onboarding process.

2. If your organization is pro-gen-ai, there's tons of potential there for this.

3. Automated code quality systems and tests

Content you might like

Do you think Low Code / No Code platforms will result in fewer developer jobs?

Yes50%

No45%

Unsure3%

View Results

Are you currently hiring AI developers?

Yes, we’re hiring39%

No, we’re reskilling current staff50%

No, we’re fully staffed 11%

No, and we don’t plan to hire for this

View Results

What’s your reaction to news that Meta is planning to let developer candidates use AI during coding tests? Would you let candidates openly use AI during the interview process?

For on premise environment, does your company run Kubernetes worker nodes on VM or BM(bare metal), and why?

Looking at adopting Blazor for small to mid-sized projects (primarily the Server-Side Interactive mode). Any thoughts on Blazor Server-Side in production - whether development experience, user experience, support, etc? Have you had to support a user base that has less-than-ideal network conditions?