I legit don’t understand what these blog posts hope to accomplish.
Just Launch the Damn Thing
21–26 of 26 posts
Re: Just Launch the Damn Thing
#22https://abc11.com/bear-chases-skier-romania-skiing-brown-cha...
Re: Just Launch the Damn Thing
#23Individual anecdotes are often charming and sometimes inspiring. But with so many decision points, a series of "succeed like me" single-example posts, all with different messages, start to blur.
Re: Just Launch the Damn Thing
#24While you don’t want to do something really dumb that’s hard to get out of from day 1, I can’t agree more. Last year I was asked to help with an open source medical devices project for Covid, and when the guy writing the infrastructure said he had a microservices design in place I took that as a queue to exit the project. They hadn’t even validated that people needed what they thought they should build, and here was a guy about to do a ton of work for scale that likely never came.
Re: Just Launch the Damn Thing
#25Ah yes this discussion. As always, I will chime in saying what I always say. While it's true that you need to begin the iteration process with real customers sooner rather than later, you still have to actually build something for them to use. This is still going to be very hard work. Yes, don't build features nobody has asked for yet, but do completely deliver on at least one core feature that actually makes people…
Re: Just Launch the Damn Thing
#26> Until sometime last year I'd been coding socii in the open because I bought into the MVP (minimal viable product) hoopla the tech community spouts. As a result, no one used it because it lacked features people expected or wanted. Turns out, if something is too minimal it ends up not being viable and well, no one will use your product.