The Master Plan — Engineering

Okay, well the truth is it’s a really lousy plan. The reason being, it’s not much of a plan, but I can’t help that. I don’t know jack shit about how to make this thing. Seriously.

So, the way I see it, thehuman.directory has to be a web app. That way it won’t be constrained by any specific platform, and it should, in theory, posses scalability.

So I just build it right? Right. But it’s not that simple. I’m not a technical guy, something many people have been telling me over the years. Okay, so get a cofounder that can engineer this. That seems to be all the rage nowadays doesn’t it. Sure, I’ll do that….

Except I won’t. 2 problems. 1, its notoriously hard and I honestly don’t have the network or connections to make it happen. Or that’s what I tell myself, because of problem number 2.

2, I’m pretty mad that people think I can’t handle technical shit. So I’m gonna learn the whole mean stack in order to build this. Yup. Myself. From no experience.

I know, I know, that’s inefficient as hell. I also know that I may not even have the chops. But hey, if it works out, I will have an intimate understanding of that hot chick named web technologies. That would help me run thehuman.directory if it works out AND possibly be employable in case it doesn’t work it. So win, win.

Yes, it’s not the fastest move, which is contradictory to everything the Silicon Valley gurus say. And yes it sounds like I’m playing it safe, which never is supposed to work.

Let me flip that particular train of thought off its tracks. What I’m doing is OBSCENELY risky. I’m hinging everything on the fact that I will be able to do something 100000 times harder than anything I’ve ever attempted, while fulfilling schoolwork I already struggle with.

Okay, stay tuned for master plan part 2, distribution. Lemme give a minor spoiler.

I’m gonna do that alone too.