Beware of Developers Who Do Negative Work
blog.professorbeekums.com
Beware of Developers Who Do Negative Work
1–10 of 271 posts
Re: Beware of Developers Who Do Negative Work
#2Maybe these developers that produce "negative work" think your code sucks. Ever consider that?
Re: Beware of Developers Who Do Negative Work
#3Maybe these developers that produce "negative work" think your code sucks. Ever consider that?
That's possible, but if the code is sitting there for years without bugs then it is doing positive work.
Re: Beware of Developers Who Do Negative Work
#4After reading the article, I feel like a code test and discussion and or whiteboard would have filtered the type of developer they mentioned who is a net negative on the code base.
Re: Beware of Developers Who Do Negative Work
#5Maybe these developers that produce "negative work" think your code sucks. Ever consider that?
What's your point exactly?
Re: Beware of Developers Who Do Negative Work
#6There's this magical process called continuous integration that internalizes the impact of bad (or, more likely, misguided) developers. Don't let them merge their branch until all tests pass. If their commit breaks something while all tests still pass, then direct them to write the missing tests.
Re: Beware of Developers Who Do Negative Work
#7After reading the article, I feel like a code test and discussion and or whiteboard would have filtered the type of developer they mentioned who is a net negative on the code base.
This is a good counter-argumnent to the frequent article decrying whiteboard tests.
Re: Beware of Developers Who Do Negative Work
#8After reading the article, I feel like a code test and discussion and or whiteboard would have filtered the type of developer they mentioned who is a net negative on the code base.
This is a good counter-argumnent to the frequent article decrying whiteboard tests.
I feel like whiteboarding is really essential when talking about how code should be written, but most whiteboard tests are about writing code on the whiteboard. There's a big difference between the two activities.
Re: Beware of Developers Who Do Negative Work
#9There's this magical process called continuous integration that internalizes the impact of bad (or, more likely, misguided) developers. Don't let them merge their branch until all tests pass. If their commit breaks something while all tests still pass, then direct them to write the missing tests.
Sometimes they are in politically privileged positions and you can't get rid of them, ask me how I know.
Re: Beware of Developers Who Do Negative Work
#10There's this magical process called continuous integration that internalizes the impact of bad (or, more likely, misguided) developers. Don't let them merge their branch until all tests pass. If their commit breaks something while all tests still pass, then direct them to write the missing tests.
CI does nothing to prevent bad developers checking in bad code. You just end up with equally poor unit tests.