Thread

I’ve been working on Pipes for six months, minimum, but I haven’t written a single line of code on it. Most hard and worthwhile engineering work is done in your head, and the code should feel easy and irrelevant once you’ve planned it out (minus obvious bugs and exceptions which happen).

Not sure when I’ll publish the full thing, but the basic idea is I’d like some help paying for the development and then the downstream effects are obvious and revenue generating. To make that less bullshit, once I create the core infrastructure I can then use the tool suite I’ve got to ship rapid prototypes (like 4-12 hours) for any use case. If I build Pipes, I’d love to sync up with homeschoolers, alternative medicine people, weirdos of all sorts. My goal is creating something that’s easy for you to use as a nontechnical person first, then I’ll back in to the programmatic stuff that supercharges it. I am also 99.9% sure I’ll be building revenue sharing into Pipes, so early adopters and use cases will potentially be able to earn a living by curating quality channels, ideas, or topics.