If you are consistently restarting a project, starting a class over, wiping your IDE to start afresh page of code the problem might be in not understanding what you’re actually trying to deliver.

When we don’t know what someone wants at the end, we keep adding stuff until it looks like something no one would want – so we REBOOT – and start again.

And then we start doing a whole bunch of work, much better this time, maybe a bit more cleaner, but still not exactly what we intended to build – so we consider REBOOTING one more time.

The problem isn’t the work you are doing, it’s where you are starting from and if you and your team are constantly rebooting, it could be a signal that you need to figure out what it is you’re doing before you start again one more time.

Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US).  I’m also the co-host of the Remotely Prepared podcast.


Write A Comment