Skip to content

Instantly share code, notes, and snippets.

Created Feb 18, 2014
What would you like to do?
Talk: Why the next big thing sucks

This is a proposal for a talk that I'd love to give. If you'd love to have me present this at your conference, please get in touch. If you'd like to attend this talk, please +1 it in the comments.

Why the next big thing sucks

Versions of this talk have been presented at:


We're coders, not hipsters. We're here to change the world, not be swept up by change.


Each day, a new library, tool, framework, blog post, whatever comes out. The amount we sometimes feel expected to learn can be overwhelming at times. How on earth can we ever earn the big bucks and be an expert at something, when the somethings keep changing!?!

In this talk, I'll break down why getting caught up in the latest trends may be detrimental to your health. How slowing down, with a big idea, and a lot of effort over time, will bring amazing things.

It'll cover questions like:

  • What should I learn, am I learning the right stuff?
  • Why are there soo many similar projects, can't there just be one?
  • Why are more or less projects good or bad?
  • Why do some projects get insanely popular and then phaze out, while others continue to gain popularity over time?
  • Do I really need to learn the next great thing? What should I learn? Where should I even start?


Tissues, in case this breaks you out of the hipster mindset.

Speaker bio

Benjamin Lupton is the founder of Bevry, a Sydney based company dedicated to empowering developers everywhere. His open-source javascript and node.js projects are some of the most popular in the world, even 37Signals and Microsoft uses them. Besides work, he drives his family nuts with questions of life.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment