443 karma · joined May 18, 2021
- email me at samroseahmed at gmail dot com
> Balance your early engineering and infrastructure with achieving Product Market Fit
No, not really, you should focus way more on the latter really. We devs love the first tho. e.g. comment from your original post 12mo ago: "Super stoked to see you launching after working on it for so long!" -> how much of the code you've written was necessary to come to the realization you eventually came to? Based on the way you described your trouble selling, seems like very little to none.
- Azure seems like a bad choice (running out of capacity lolwut)
- corollary to above: don't get too attached to where you worked. Seems like your original idea was heavily based on something u saw internally. Just because something works well at one (usually large) company you worked at doesn't mean it serves a widespread market need (I've been burned by this).
Just some thoughts, hopefully your pivot is successful!
Another issue is it's completely mobile incompatible, which is kinda sad but usually not practically a big deal for the usecases it's used for.
Blueprint (https://blueprintjs.com) made by Palantir has been my go-to otherwise but it misses some common things (like a table).
Elastic's recently open sourced framework (https://eui.elastic.co/) looks pretty good too, though I haven't tried it.
But, this raises some important questions. You're essentially outsourcing your entire company. Think about it, especially for an open source project, the main way you make money is build a cloud version of you product. If someone else is doing that for you, what are you left doing? It's a dangerous place to be in.
What's to stop the owner of this service to realize he can cut you out from the middle, and just build a service out of your product himself?
E.g. that's a lot of AWS's M.O. recently; they have really robust internal infrastructure to spin up managed services for any project, and they make a lot of money doing that.