Slashdot stories can be listened to in audio form via an RSS feed, as read by our own robotic overlord.

 



Forgot your password?
typodupeerror

+ - The JavaScript juggernaut rolls on->

Submitted by JThaddeus
JThaddeus (531998) 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.""
Link to Original Source

Comment: Expiration dates (Score 1) 384

by jlusk4 (#42504761) Attached to: What Are the Unwritten Rules of Deleting Code?

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: Team Leads/Architects, not Mgrs, are the problem (Score 1) 545

by jlusk4 (#38685432) Attached to: How To Get Developers To Document Code

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

Never try to teach a pig to sing. It wastes your time and annoys the pig. -- Lazarus Long, "Time Enough for Love"

Working...