News for hackers. Stuff that matters.

A comment on When Node.js is the wrong tool for the job. Parent comment

Re:When Node.js is the wrong tool for the job by ekidd on Friday January 06, 2017 @10:36AM (#13337054)
> Every project I've been brought in on, the qualifier was "must know tech X". And almost always (there were exceptions) I knew more about tech X and software dev in general than the original developers, and the crunch was not "how do I do XYZ in this tech?" it was "how do I get the other developers to actually use version control?" or "use version control sanely?" or "document anything?" or "write tests" or "have test data" or "have a repeatable build process"?

I've seen this so many times on consulting gigs and with the occasional new employer. I'm hired because I'm familiar with the technologies they're trying to use, but the first major value I bring to the organization is simply getting some kind of sane process: working version control, automatic builds, test suites, one-button deploys, and so on.

[ Parent | on HN ]
Re:When Node.js is the wrong tool for the job by mi100hael on Friday January 06, 2017 @12:06PM (#13337964)
> I've seen this so many times on consulting gigs and with the occasional new employer.

Same, and it's getting really fatiguing. Probably the #1 driver for me to get a side-project off the ground is to finally actually write code and not just play janitor for someone else's mess.

[ Parent | on HN ]