-
-
-
@wpeterson@bdarfler or a "monorail" in the case of Groupon
End of conversation
New conversation -
-
-
.
@bascule the common thread is declaring technical bankruptcy and learning from your mistakes the second time around -
@languagehacker by rewriting everything in a soup of callbacks, promises, and streams! - 1 more reply
New conversation -
-
-
@bascule success is rarely a direct (or even indirect) result of tools used along the way, and much more about who was using them and how. -
@darkuncle for whatever reason Node took top billing in both stories -
@bascule people always like talking about the new cool tools; it's sexier than saying "success was due to hard work, timing and luck"
End of conversation
New conversation -
-
-
@bascule "we actually know more things now than we did 15 years ago, and it's all thanks to node.js"Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule sometimes i consider nodejs successfully stories considered harmful. here's a better story though: http://aosabook.org/en/posa/from-socialcalc-to-ethercalc.html …Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule In these cases I assume its 50% changed processes, 25% new people and 25% new language/frameworkThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule actually looks like Node.js is being used only as frontend in all of these stories . -
@guilleiguaran@bascule front-end? LOL -
@azat_co
@bascule sure, frontend servers ;) -
@guilleiguaran@bascule even if servers, it would be stupid and crazy to switch stacks all at once in such big COs
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.