Niklas Stephenson
Founder led product About
LinkedIn X RSS

Thoughts on code

April 08, 2019

  • Code should add value
  • Everybody should be able to read the code
  • Code should be easy to make scalable on a later stage
  • Code should not create too many edge cases
  • Code must be reviewed
  • Code should not attract too much attention when running in production
  • Code should be easy to test
  • Code must be pleasing to the eye
  • Code should be fun to write
  • You should never think too much about how you write code

Related posts

  1. Shiny new object syndrome

    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.

  2. Break process

    When writing about product leadership, it’s easy to write about the process—the stuff that is easy to visualise and express. But the truth is that we only have processes to facilitate the lowest denominator of creativity in a team. We would have no processes if we had better ways to innovate as a team.

  3. 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.

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.