Please create an account to participate in the Slashdot moderation system


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Submission + - The JavaScript juggernaut rolls on (

JThaddeus writes: An article in TechWorld Australia summarizes the latest opinions on JavaScript from ThoughtWorks: "There is no end in sight to the rise of JavaScript... 'I think JavaScript has been seen as a serious language for the last two or three years; I think now increasingly we’re seeing JavaScript as a platform,' said Sam Newman, ThoughtWorks’ Global Innovation Lead." The article touches on new additions to JavaScript tools, techniques, and languages built on Javascript. As the fuller report (PDF) says, "The ecosystem around JavaScript as a serious application platform continues to evolve. Many interesting new tools for testing, building, and managing dependencies in both server- and client-side JavaScript applications have emerged recently."

Comment Expiration dates (Score 1) 384

Either date- or version-based. "Delete after dd-mmm-yyyy" or "Commented out in 5.1". (Note how cleverly I avoid anticipating future version numbers. Management tends to change those things.)

To all the people saying "version control": I've seen enough botched configuration-management system changes and moronic branch management to know it ain't the be-all people think it is.

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()"/>)."

Slashdot Top Deals

Live within your income, even if you have to borrow to do so. -- Josh Billings