Podcasters Cut: Building in Public - Why I'm Making My Own Secure Communication Suite

I was a mentor to someone who never had development experience, never had engineering experience.

And he built something that I was advising for and I was unofficially consulting for.

And I was doing it because I believed in what he was building.

And I think what... think what gave me not only inspiration but just kind of hey you know you should be scratching an itch too was and and like that's why i said that most most of my creative phase and my creative period happens at the end of the year happens now i don't know if it's because uh you know birthdays coming up or whatever i look i don't i don't do the whole birthday celebration thing but i i don't know if that has something to do with it where um where I just, yeah, I just get in my creative zone.

And so working with this individual, I pretty much, I taught him the genetic coding.

I taught him everything he knows.

And I think something started kind of sparking, something started, you know, the creative fluids and in my mind started sparking when I saw that, wow, I think I've done a good job if I'm able to mentor someone who has no experience and just an idea and teach him agentic coding and teach him how to work on projects and see him build.

So from one builder to another, I think That was inspiring for me to want to, you know, after I saw what he was building, I kind of thought to myself, wow, you've come a long way from, you know, from not knowing anything to actually deploying for the first time to setting up infrastructure to by no means to deploy.

And so that I think showed me like, well, man, it inspired me.

Through that mentorship, I was inspired to build something on my own.

And that's what I'm gonna do.

And I don't want to really give details on it right now because it's still not V1, still not version one.

But I will say that it's going to borrow a lot of what I like from enterprise communication platforms and secure messengers.

And so I'm baking in the design philosophy around that.

And let's be real.

It just seems like now, what are billionaires and wealthy people doing? What are the most successful companies building? You look at Slack, you look at these messengers and it's like, oh no, another messenger.

Well, hold on.

If you build something that competes with Slack and that isn't the end goal, isn't the end goal of product design to be acquired? so i would like nothing more obviously right i want my i want my million dollar acquisition story right but the origin of that was seeing seeing what was being built that i know i could refine and make better and then having a disagreement in the design process of that with my uh ex-peer, ex-business partner.

And so I just feel like there is no excuse.

There is no excuse.

If you can take this guy, if you can take this guy with no experience and he's shipping stuff, right? And he's shipping stuff.

because of the help of coding assistance, then I think I'm at a point where it's like, now I just realized like, whoa, like what's my excuse? Like if I wanna build a communication suite that's secure and private, right? Why am I not building that? And if you look, Slack, it got acquired, you know, it became a company and whatever, et cetera.

If you look at all, if you look at the Telegram guys, the Telegram founders, right? The guys are, they're wealthy.

So it seems like you come out with a messenger, you push it, it gets big enough to where people identify some of the, you know, some of the qualities of it.

the design appeal and they don't want to go out and build it themselves.