Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Re:I suspect (Score 1) 97

:) Ok, tiger, good one. Made me laugh (but quietly, since I'm in a cube farm).

I can guarantee you no one on my team (of developers, of varying ages) knows what mind maps are, except our BA, who got handed one by someone on ANOTHER team.

Comment Team Leads/Architects, not Mgrs, are the problem (Score 1) 545

It's not management. It's not lack of financial incentive. Mgmt doesn't have time/energy to scrutinize docs, and paying for docs is stupid because you'll get filler.

It's thought leaders on the team. You get some architect who wrote the system and fully understands it, PLUS he's smart, PLUS he's a git r done type (remember? remember? smart, gets things done? Thank you, Joel Spolsky). Result: the smart guy everybody looks to writes no docs. He doesn't need them. It doesn't occur to him that others might need docs, because it's not an immediate problem (fire, crisis) he can put out and be a hero. It's friction. No payoff for him to eliminate _that_.

So, everybody on the team follows his lead. There's no team culture of helping each other out by writing little love notes to each other that say such sweet things as "Returns the two highest priority items that are neither red nor flibbertygibbits (<see cref="isFlibbertyGibbit()"/>)."

Comment The first answer is not QA (Score 1) 213

tl;dr (yet)

But I do have something to say about the immediate response of "QA". These are design issues (as has been mentioned). QA is not where you test out that sort of thing. Up-front design (not necessarily Big) should be the first response. Now is not the time to slack off on design, just because a lot of the components have already been written.

Slashdot Top Deals

How often I found where I should be going only by setting out for somewhere else. -- R. Buckminster Fuller

Working...