1. I'm scratching my own itch. I wanted a privacy friendly alternative to Google Photos to store and organize my memories, I couldn't find any that were as convenient, so I'm building one.
2. I have a clear path towards a public release, so I'm not worried about it being a "zombie" forever. Some projects take longer to see the light of day, and I'm okay with the delayed gratification.
I am always quite surprised that many people think "yea, you always can build a software in a few weeks. If not bah, not good'.
I think SOME softwares requires month if not years of building. Because there are difficult technically. Those complicated softwares can be a game changer in the field, because well, the technical entry is so hard. So let's see more those softwares like perhaps future BIG success. Not just future 'obvious failures'.
I think this makes sence.
To reiterate, this really is the happiest I've been.
The initial few months were not smooth (as indicated by the article). Mostly because was an expectation mismatch with respect to how comfortable I believed/was made to believe life would be for an "ex-FAANG engineer" starting up.
Also, the loneliness I felt was more about not having someone to rant to about roadblocks or share small achievements with. This was something I had taken for granted at work.
I wrote down this essay now after I felt that I was in a comfortable place, and that there were learnings that could possibly benefit someone going through a similar journey.
> a zombie startup
That's definitely the case now, and will be for a few more months. I've never been a fan of "ship fast, apologize later". So while it's less exciting to work on a product that's not live, it's something I'm okay with.
But thanks for your thoughts, I can see where you are coming from.