Re:Kicking the tires: A trial month at 37signals
by cydonian_monk on Friday January 13, 2012 @03:59PM
(#3462382)
It can be worse than that.
Unfortunately adding issue 124,436 into the tracker puts the manager responsible for $SYSTEM over quota for exceptions. Most likely that item or one similar will be placed on a completed project just to get back under quota. Nobody needs issue 98,402 fixed if issue 124,436 prevents you from reaching it, right?
I wish this wasn't the world we lived in, but such management tactics will never really die.
Re:Kicking the tires: A trial month at 37signals
by ceejayoz on Friday January 13, 2012 @03:59PM
(#3462381)
There's an enormous middle ground between the two extremes you're portraying, though.
Re:Kicking the tires: A trial month at 37signals
by patio11 on Friday January 13, 2012 @04:08PM
(#3462411)
True. If, for example, you're a consulting company, you could have an intermediate developer sit down and watch every junior developer as he codes. The intermediate developer could then say "Oh, dude, nice try but stripping all HTML will probably bork at least some customers' sites. Here, let me open a console on prod and fire a quick SQL query that would get me fired at TPS Reports Inc. Ahh yes, it appears customers do indeed embed HTML. OK, let's do this the long way."
This would allow you to bill, ballpark, $10,000 for "Enhancement: forgetting to close a tag in a todo no longer borks site."
But, while not being TPS Reports Inc, that is still a pretty different environment than what 37Signals operates in.
Re:Kicking the tires: A trial month at 37signals
by ceejayoz on Friday January 13, 2012 @04:37PM
(#3462511)
@qrush is a far, far better programmer than I. Still, "let's find out how many todo items this is going to affect first" seems like a fairly logical checkpoint on a large production system.
Re:Kicking the tires: A trial month at 37signals
by weaksauce on Saturday January 14, 2012 @01:09AM
(#3463607)
what's wrong with adding tags at the end of the user editable areas that are unmatched so the rest of the page does not break when they add unbalanced html? I think they should parse it and make sure it's legit html before blindly saving it(xss possibilities if anything is public facing et. al.).
Basecamp would be a very different product if it was made that way, though.
There are non-zero costs associated with giving people the authority to do productive work. On the plus side, this enables them to do productive work.
P.S. Having worked at an organization which did development that way, I can tell you that having copious documentation does not mean requirement 1,735 will be implemented, but it guarantees requirement 1,735 will be written about somewhere, which is what that organization type ends up optimizing for.