Shiny new object syndrome

September 23, 2020

Yesterday I talked to a candidate who was considering applying for a developer role at Legal Monster , he could not understand why we did not apply ML/AI to solve problems.

ML/AI is great for some things, but a lot of things can be solved with simpler technology. We should as an industry always try to solve problems with the right tool for the right job and for me simplicity is an important factor in picking the right tool.

Way too many developers have "shiny new object syndrome". The tech stack rarely changes the value of a product, solving a customers problem do, and customers rarely care about how the problem is solved behind the scenes.

We have thousands of users on our platform, not a single one have chosen not to use us due to our stack, but some choose not to use us when we don't solve their problems.

Related posts

  1. Choosing Ruby on Rails is not a technical decision

    You should just go with Rails.

  2. Make one customer happy

    Find one customer that is funny and motivating to work with, and learn about all their problems, select one and solve it. Simple.

  3. Poof and your product is gone

    Last week I talked with a startup that had struck a deal with a tech company, for a percentage of the startup the tech company would build their product.

Get an email when I publish a new post

I'm going to be writing about my experiences and thoughts on product leadership, entrepreneurship, and building software. My small corner of the interwebs that is not guided by algorithems. A strange mix of thoughts and feelings on our crazy industry.