Re:Recombine to avoid naming when naming is hard
by bunderbunder on Monday July 06, 2015 @01:16PM
(#9840612)
I doubt it. And even if they did, I don't think you should expect their results to generalize.
There's some evidence to suggest that the reason why studies like this so often produce seemingly conflicting results is that there aren't very many universal rules. The same practice can be helpful for one team and harmful for another based on any number of circumstances.
Re:Recombine to avoid naming when naming is hard
by tetha on Monday July 06, 2015 @02:28PM
(#9841128)
It's even in the same company. My team has very few common problems with our product teams. In fact, some of our experiences are just contrary to the product teams experiences.
Overall, software development is looking more and more like a journey to me. And a journey in the polar sea is different from the journey in the sahara. Just don't leave jenkins at home in either case.
Re:Recombine to avoid naming when naming is hard
by lsc on Tuesday July 07, 2015 @02:34AM
(#9843919)
eh, I think that there is a lot of value to standardization. Your average programmer is gonna spend more time reading code than writing it; there's something to be said for getting used to one standard style.
Hm. I wonder if some of the larger companies are doing that sort of thing and keeping it internal-only or using it for internal coding standards without publishing it in an attempt to gain competitive advantage?