Live data from Hacker News

Bleeding-edge tech will kill your startup

contrast.app

161–170 of 196 posts

Re: Bleeding-edge tech will kill your startup

#161

Earlier quoted context omitted.

I’m sensing some attitude issues just reading this, to be completely honest. If your reaction to your library/product/whatever not taking off on HN is to get on HN and complain about it, you’re probably building whatever it is you’re building for the wrong reasons. > I can see the problem, and some of the solutions - but other developers are simply not interested. Developers are constantly marketed all kinds of solut…

Web accessibility is a legitimate issue that every front-end developer needs to care about.

For everything you think someone else needs to care about, there are probably a 1000 other things as well.

It's not necessarily if people care but what they care more.

Re: Bleeding-edge tech will kill your startup

#162

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 :) )

Is this actually someone just testing what % of people read the article before commenting?

It does make me wonder, given the deceptive nature of the title and obviously emotive topic of whether devs should use bleeding-edge tech...

Re: Bleeding-edge tech will kill your startup

#164
post #147

Earlier quoted context omitted.

> I, too, have developed a software product that attempts to address a key failing in one of the (more under-utilized) DOM elements we have at our disposal when building websites Link?

https://github.com/KaliedaRik/Scrawl-canvas

Dealing with Canvas is painful. I recently ran into a weird image distortion issue on Samsung Internet Browser 12 (I guess it's based on the Chrome engine) when drawing a video frame to a canvas context using `drawImage`.

Since you've made Canvas your focus, I'm curious if you've seen this or have any ideas. Here are a couple reports I found online.

This one shows exactly what I see (note: this is not my post), and I was able to "fix" it using the technique in the question. I'm not particularly happy with that solution so I'm still working to understand what's going on.

https://stackoverflow.com/questions/63911732/javascript-canv...

Here's another report that seems related, although there's no mention of interaction with the video element.

https://forum.playcanvas.com/t/samsung-internet-browser-canv...

Re: Bleeding-edge tech will kill your startup

#165
post #147

Earlier quoted context omitted.

> I, too, have developed a software product that attempts to address a key failing in one of the (more under-utilized) DOM elements we have at our disposal when building websites Link?

https://github.com/KaliedaRik/Scrawl-canvas

jQuery community has lots of different extensions. I searched 'jquery canvas' and this popped up: https://projects.calebevans.me/jcanvas/docs/text/

I'm not sure you have a 'product' you just have a library.

Re: Bleeding-edge tech will kill your startup

#166
> 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. Huzzah! we thought. We should build a tool that tells you the adoption rate of every component in your design system—across your product. Chefs kiss.

This article has nothing to do with bleeding-edge tech. It's about launching a product around which zero validation work has been done.

The quote above is the entire description of the alleged "bleeding-edge tech." I still don't know what the problem is. "Design system" is vague enough to me at least to be meaningless. There's a screenshot that looks like web analytics.

Web analytics have been done to death. This isn't bleeding-edge tech. It's me-too products desperately fighting for market share by going ever deeper. Big difference.

You've got to be an excellent communicator to play this game. Given the mismatched title and fluff in the article, I can see why the team had a hard time connecting with prospective customers.

Re: Bleeding-edge tech will kill your startup

#167
One frequent exercise that I do with my colleagues who work with startups at ideation stage is to imagine how the value proposition could be challenged by a popular IM such as WhatsApp or WeChat.

We would ask ourselves: "Could process A be replaced by WhatsApp in this or that way?"

If the answer is Yes, then we would advise stakeholders to rethink that process or functionality to make it unchallengeable by the IM in the short run.

Re: Bleeding-edge tech will kill your startup

#168
post #166

> 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. Huzzah! we thought. We should build a tool that tells you the adoption rate of every component in your design system—across your product. Chefs kiss. This article has nothing to do with bleeding-edge tech. It's about launching…

The entirety of this article (and their startup's failure) can be summed up by this one line:

> prospects didn't know [...] the problem we were solving

If "prospects" don't know what problem you're solving, 99% of the time that means they don't have the problem your product solves. And if that's true, they're not actually a prospect. Seems like a classic case of being a solution looking for a problem.

Also the author's nonsensical "circle of death" reminds me of the "Conjoined Triangles of Success" from Silicon Valley[1]. Except Silicon Valley is a parody, and I don't think this article is meant to be.

[1] https://www.youtube.com/watch?v=cB7dInljmO4

Re: Bleeding-edge tech will kill your startup

#169

One frequent exercise that I do with my colleagues who work with startups at ideation stage is to imagine how the value proposition could be challenged by a popular IM such as WhatsApp or WeChat. We would ask ourselves: "Could process A be replaced by WhatsApp in this or that way?" If the answer is Yes, then we would advise stakeholders to rethink that process or functionality to make it unchallengeable by the IM in…

could you give an example?
Post reply on HN