Some of my fascination with micro-ISVs is rooted in my wonderings about the path of my career over the long term.

When I was 22, I believed that I could write code until age 65. I saw no reason why I could not be a software developer for my entire professional career. Some folks told me that being a coder is a burnout job, but I didn't believe them.

I am 36 now, and I think I have a better understanding of things. I am starting to realize that someday I may actually want to make a career change. I am trying to picture myself running an ISV when I am 55, but I just don't see it. Running a company can be awfully stressful sometimes. Will I still want to be doing this in two more decades?

My prospects for a second career are bleak. The cold reality is that I only know how to do one thing. Instead of looking for a second career, maybe I should be looking for a way to stay in software.

This is one of the things I like about micro-ISVs. The lifestyle looks very different. The workflow looks like it might be a lot less stressful. Running a micro-ISV looks more like a marathon and less like a sprint.

At my recent lunch with Thomas Warfield (Pretty Good Solitaire), I asked him if he thought he could still be running his micro-ISV at age 50. He said yes. Warfield is 40 now, so this is not the perspective of a naive young person just getting started. I believe him, and his answer makes me wonder if somebody I will be running some sort of a micro-ISV as my full-time job.

Choose a task to be accomplishedSet the Pomodoro to 25 minutes (the Pomodoro is the timer)Work on the task until the Pomodoro rings, then put a check on your sheet of paperTake a short break (5 minutes is OK)Every 4 Pomodoros take a longer break - http://www.pomodorotechnique.com/

Most of product development is the middle part: the messy, weird, unintuitive place where you and your team are making hundreds of small decisions. If you are not looking to real people by continuously conducting user research and running hypothesis-driven tests, you’ll slowly (and with growing confidence) get far away from your actual goal: Making a product for real people. - https://medium.com[..]-things-come-to-think-of-it-42fa3d7cb415

No meeting should ever be more than an hour, under penalty of death.Every meeting should have a clearly defined mission statement.Do your homework before the meeting.Make it optional.Summarize to-dos at the end of the meeting.