The Two Pillars of JavaScript: Part 1: How to Escape the 7th Circle of Hell

Re:The Two Pillars of JavaScript: Part 1: How to Escape the ... by Spearchucker on Saturday December 13, 2014 @09:30AM (#8745233)

"planning ahead"

Whoa, that's fighting talk. Next we'll be doing big design up front and (god forbid) beginning with the end in mind.

That was tongue-in-cheek, only because everywhere I go these days I see people bowing down at the altar of refactoring, rather than doing a bit of planning and getting it right first time.

[ Parent | on HN ]

Re:The Two Pillars of JavaScript: Part 1: How to Escape the ... by robmccoll on Saturday December 13, 2014 @10:03AM (#8745296)

Of course - planning is anti-"agile". You're supposed to run around in a constant state of chaos beating on everything with a hammer until a usable product magically pops out.

[ Parent | on HN ]

Re:The Two Pillars of JavaScript: Part 1: How to Escape the ... by calinet6 on Saturday December 13, 2014 @10:02AM (#8745284)

Refactoring happens when you don't get it right the first time, though, and that tends to happen often even with planning; so it's still a useful and necessary process.

You are correct about emphasizing more planning up front, of course. If anything deserves bowing at an altar, it's designing before you write code.

[ Parent | on HN ]

Re:The Two Pillars of JavaScript: Part 1: How to Escape the ... by h_r on Sunday December 14, 2014 @11:49AM (#8748720)

To be fair, planning ahead and getting it right requires a relatively stable specification of the requirements. This is not often found in a typical business environment.

[ Parent | on HN ]