Knowing when to stop and launch.

As a dev turned founder I know all about this.

You need to draw a line in the sand. When these absolutely crucial features are done - its time to switch gears 100% and go into marketing mode. Launch, and setup a feedback loop with your users. Pencils down, no dev work, just talk to your users.

Understand that the development is never done. After launch, your work is just starting.

My bad habit as a dev is making assumptions - often times I'm right (the users will definitely want this) and sometimes I'm wrong. Those wrong times can waste a substantial amount of time and valuable energy on your part, and at worst steer your product down a path that no one wants to go.

So you gotta reel in the rush you get from dev work, and start to appreciate the other side of the process. Communication with your users and learning more about the pains that drives them your way becomes the priority. Ultimately that is going to be what brings you success

It happens a lot, especially to developers turned startup founders. If these feelings are powerful, you might want to do some soul searching and figure out if starting a business is really what you want.

Oftentimes, developers simply want to build stuff. Starting a business is more, way more, than just hacking away on a product idea. It's not for everyone. If building stuff excites you much more than the idea of talking to people about your product/idea, sales, marketing, business development, etc. you might be better off joining a team at a startup rather than starting something yourself.