101–110 of 196 posts
For https://expose.sh I use TypeScript for the back end and the client so I get the benefit of one language for the whole service. TypeScript has been around for a few years but it is still pretty new compared to say Java.
By using Docker for the dev environment of the PHP ecommerce platform, it saved me from having to build one myself.
> Market Type changes how you evaluate customer needs, customer adoption rate, how the customer understands his needs and how you should position the product to the customer. Market Type also affects the market size as well as how you launch the product into the market. [0]
Incorrectly identifying market type can certainly kill your company, or make the process of working on it really painful.
However, I do think building a new market is a different kind of bet. Much more uncertain, much riskier, and larger upside potential (but I think that upside is harder to capture, especially if you're early in the space).
FWIW, I do like the pivot. We're using 1:1 component mapping between our designs in Figma and React front-end, it's something I can imagine using.
[0] https://steveblank.com/2009/09/10/customer-development-manif...
Has any of commenters read the article? Looks like everyone talks about using bleeding edge tech in startup and how its bad, but this article is about building a bleeding edge product and how difficult is to sell such product (probably because everyone know that using bleeding edge products is dangerous :) )
Not even about bleeding edge products. It's a lengthy article about the pitfalls of entering a market with no market validation, which the author slapped lipstick on and gave this sexy title.
Making something nobody wants is a classic startup mistake. I resolved not to make it again and read a great deal about market validation and building products.
I have one recommendation for those reading this thread: Steve Blank's "Four Steps to the Epiphany". It contrasts Product Development (focusing on a product with no customers) vs Customer Development (focusing on customer problems and building software around those). Honestly you don't even need the whole book, there's a PDF with the first couple chapters floating around [1]. I had a bunch of "holy shit, that's exactly what I did wrong" moments while reading it.
Eric Ries' "Lean Startup" is also an excellent book on this topic.
[1] http://web.stanford.edu/group/e145/cgi-bin/winter/drupal/upl...
Just want to say this website is what I think a modern website should look like! Loads in under 1 second, has a simple but very cool design, no needlessly heavy JS framework in sight, due to the images it's a bit heavy at around 2.7MB, but still pretty good.
Earlier quoted context omitted.
Not even about bleeding edge products. It's a lengthy article about the pitfalls of entering a market with no market validation, which the author slapped lipstick on and gave this sexy title.
I had my first startup fail in the late 2000s because we built a sales prediction software that sounded cool, but nobody actually wanted. We even had a large paid pilot with a major auto manufacturer, but they didn't renew when it turned out that none of their employees had actually used the software. Making something nobody wants is a classic startup mistake. I resolved not to make it again and read a great deal abo…
Earlier quoted context omitted.
It's such a difficult line to toe. Especially because people like working with new technology and it does seem to help with recruiting even if it makes actually operating the business harder.
Some people like working with new tech; in my experience most do it not because they like it but because of their resume. I like how I can get really good, cheap and experienced devs for ‘non hip’ tech because they do not want to work with new tech, they want to improve their skill on what they know; java/spring, c#/asp, django etc with jquery/bootstrap. Resume driven/recruiting forces them into all the new stuff but…
but yeah my mindset always was being the jack of all trades, which is very good for small startups and not a good mindset for corporations which I avoid..
Has any of commenters read the article? Looks like everyone talks about using bleeding edge tech in startup and how its bad, but this article is about building a bleeding edge product and how difficult is to sell such product (probably because everyone know that using bleeding edge products is dangerous :) )
Also the "bleeding edge product" in the article is some kind if analytics system that tells you the adoption rate of "components" (web widgets? Not sure) in your system. This might not exactly be what you think of when you hear bleeding edge, so take this article with a grain of salt.
"As designers and engineers, we knew of a rather niche problem: if your company has a design system, it's practically impossible to know the adoption rate of those components in your product."
Yeah, and I've never met anyone who cared to be honest. And if you do care, your answer is usually a quick "git grep" away.
Has any of commenters read the article? Looks like everyone talks about using bleeding edge tech in startup and how its bad, but this article is about building a bleeding edge product and how difficult is to sell such product (probably because everyone know that using bleeding edge products is dangerous :) )
> Please don't comment on whether someone read an article.
I don't think that is really true. Most start-ups fail, whether they build a bleeding edge product or try to compete on an existing market with smaller enhancements. After they fail if it's easy to pick the reason. Very few start-ups succeed whatever they do. Skype was pretty bleeding edge at the time, the internet speeds wheren't really there at the time. Spotify or Tesla didn't enter a market with real competitors.…
Has any of commenters read the article? Looks like everyone talks about using bleeding edge tech in startup and how its bad, but this article is about building a bleeding edge product and how difficult is to sell such product (probably because everyone know that using bleeding edge products is dangerous :) )
It's actually hilarious. So many people enjoy sharing their opinion on the headline rather than the content of the article.