Like I said, it doesn’t win me fans, in this community.

> How do you know that it does address their needs and how do you know that they care?

Let’s just say that I know the target demographic fairly well, having been a member of it for over 40 years, and having written a major, worldwide, infrastructure for it (over a period of ten years -also, on a volunteer basis).

I eat my own dog food. I use the software I’ve written, pretty much daily, along with thousands of others, worldwide. In fact, this app uses that infrastructure, and integrates it with a simple social graph, so you could say the app is actually the result of over a dozen years of work.

Also, the development process I use is highly testable. TestFlight[0] is, for all intents and purposes, a “mini App Store.” The app is a full-fat release, and is constantly being vetted by Apple. It’s not some crappy lash-up, like so many MVPs. It’s quite amazing, that it has been used constantly, since one month after I started coding.

I can write a lot of really good code, really quickly. What I released to TestFlight, in October 2020, could have easily been considered “The heck with it, let’s ship” by many corporations. Even six months later, when we originally thought we had our first “shippable” app, it was still pretty pathetic. What we have now, is something we are all quite happy with. We still have some months of testing and preparation to go, before we have our first public beta.

Brand damage is something that many geeks don’t understand, but is absolutely devastating, and almost impossible to repair. Even if there are some initial stumbles and hiccups (almost guaranteed), it won’t be an E.L.E. for the project or the team, and it won’t destroy our credibility. Even if it’s a complete flop (which it won’t be -I guarantee), people will still take our team seriously, so we will still be able to keep trying. I fully expect it to take several months (or longer) to mature, after we release it, but it is designed to be “infrastructure-level,” daily use, software. Good things take time. We have no problem with a “slow burn.”

Also, the software that I write Serves a fairly sensitive demographic. Security, Privacy, and Accessibility are of paramount importance. Failure in these areas could have severe and detrimental impact on people’s lives. It’s not hyperbole, at all, to say people’s lives depend on the Quality of my work. I can’t afford to “move fast and break things,” as said “things” could be people’s lives.

There’s a reason that I’ve repeated “people’s lives,” so often, above. I think it needs to be driven home.

> And what makes doing it worth two years of your life?

Two years is nothing (see 40 years, and 10 years, above). I’ve written software, professionally, and personally, that has lasted decades. I’m fairly adept at playing the long game (not particularly valued, in today’s tech industry).

Also, the software that I have written personally, has the potential to make a major impact on people’s lives. It’s pretty important stuff; not some “leisure/entertainment” app for bored yuppies. I take my job pretty seriously.

Some things are worth that kind of effort. If I had to explain, you wouldn’t understand.

[0] https://developer.apple.com/testflight/