-
Anybody who agrees with this statement was not part of the team, is completely ignoring the parts of the team that weren't "Big Personalities" (most of the company), and is outright just plain _wrong_. t.co/w4NPEtsAM4Permalink On twitter.com
♻️ 4 Retweets ❤️ 28 Favorites 2020 May 6 Mood 0
-
…in reply to @jefflembeck
npm failed for a load of reasons and _most_ of them are cookie cutter normal shit that startups fail for. It's a textbook sized case of "wavering product direction" mixed with "missing strategic focus" mixed with massively underfunding the work force.On twitter.com
-
…in reply to @jefflembeck
We once had a C-level person give a presentation about how we were in "starvation mode." Which meant that all of us had been busting our asses for months to try to handle things like, scale, new features that weren't fully thought out, etc. and would continuePermalink On twitter.com
-
…in reply to @jefflembeck
npm was able to hold on as long as it was because it had the team that it had. That extremely includes our support and marketing folks, who were absolute gold and the reason why npm is such a well-known name (and was so well-loved).Permalink On twitter.com
-
…in reply to @jefflembeck
Otherwise, it was a burnout factory. We sprinted non-stop toward moving goal posts and then had a leadership change that took away all of the parts that kept us alive. We were too little, too late, all of the time. As a relatively early employee, this is partially my fault.Permalink On twitter.com
-
…in reply to @jefflembeck
Permalink
On twitter.com