Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

+ - How to convince a team to write good code?

Submitted by Anonymous Coward
An anonymous reader writes "I am part of engineering team that maintains a very important component in our company. Our code quality and general engineering quality focus has been very weak: we have frequent buggy releases, our latencies are shooting up, our test coverage is nearly non existant, and it is impossible for a new comer in our team to get onboarded and be productive in less than a month due to unnecessary complexity.

A group of 2-3 of us want to change that, and we know what needs to change technically — what are better code review and release processes, better build tools etc. But despite that, the quality of our code and design continues to suffer and that continues to get released in the name of keeping the scheduled release date (product guys don't like to wait). We feel that if the right thing is done everytime, we would can eliminate our issues and still release at the same pace.

How do we affect the social change where everyone is convinced what is better and take the effort to do it?"
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

How to convince a team to write good code?

Comments Filter:

Breadth-first search is the bulldozer of science. -- Randy Goebel

Working...