The npm blog has been discontinued.
The second hire at npm, Inc. is none other than @ceejbot CJ Silverio.
When we first started casting about for a senior devops person for one of our early hires, CJ’s name came up in literally every conversation. It was a huge windfall when she agreed to join our team.
In her own words:
For me, npm is the heart of node.js. It’s the secret to node’s success: a package manager that learned from its predecessors and got an enormous number of things right. Using it was easy: edit a json file, type
npm install, and boom! You’re cooking with jet fuel, jet fuel provided in little modular canisters by hundreds of strangers who like to share their codefuel with everybody else.
NPM is what got me into open source. Publishing a package was as easy as writing one. My hands were shaking when I first typed
npm publish(which npm itself tells me was Fri Jan 6 2012, at 10:26). I was terrified that I’d published crap code (I had). I was terrified that I’d published bugs (I had). I was terrified that somebody would tell me I was doing it wrong. Nobody did, because I was doing it right. I was participating with the node community through npm! Nobody found the bugs I’d just published, except me, and getting a fixed package out was just as easy as typing
NPM lets me give back in some small way in response to all the code other node users have given me.
NPM is the secret advantage of node that I touted to my most recent employer, when I sold them on the wisdom of writing web services with node instead of the JVM. Look at the way it handles versions! Look how active the ecosystem is!
So I’m thrilled when I tell you that I’m joining isaacs, seldo, and rockbot at npm, Inc.
The only sad part is leaving the team at LyveMinds. The people are great people who have been joy to work with over the last year. I’m going to miss Kit Cambridge and Sean Zawicki terribly. The Valley’s small; we’ll see each other again, friends.
But thanks to Lyve, I’ve been out in the real world of node in the enterprise. I know where npm’s pain points are. I’ve lived them and pondered ways to fix them for my small team. Now I get to help fix them for everybody who uses node. It’s like sharing a little node module times a million. I’m stoked.
Come work with me. We need an ops person right now.