the list is questionable. I was very hopeful to see if there was a tinder for gamers (say, to find people to play coop games) but there's some sort of tinder inspired incremental game in that spot, so I wonder how much is it really curated and how much is a proxy to a Google 'feeling lucky' search
it concerns mostly around not doing things that don't scale, consider it a rough draft because I've never shared it, only tested around a bit, it's not like it's the final truth about the argument or anything.
there are many alternative path to a successful strap, some that overlaps and some that are exclusive, this checklist seem geared toward ideas suitable for vc funding which isn't wrong per se but if you optimize for funding you end up with a diametrically different path that is usually not easy to bootstrap. it's something one has to decide early and influences the very shape of your startup, so that each one of those question would be invalid for the other path. corollary: I've got a checklist for bootstrapped startup, concerning the idea itself, and the line of questioning is really different
duh, this is only a technicality, but since you need to be anal about it, I'll have the detail obsessive version so you can follow the discussion too:
"RSS doesn't define support active content, which is what's used on other channel to build in depth analytical tool that go beyond page view. without active content, analytic is in control of the reading software, a big step back from other content delivery protocol. even email could be used to track engagement using unique links for each recipient, but most reader software has an incentive to cache reads and not to forward unique links, letting content provider with the only option of syndicating link and summaries, causing a natural bias for clickbaiting titles, because driving user to the producer is the only way to get back analytical data. this has caused a steep decline in the availability of rss content and viability of rss for consumers."
that's kind of an ivory tower argument. "let's people don't have nice thing, we know what's best for them." meanwhile, most normal use don't gives a damn if the site track their behavior and post relevant ads, as long as they get quality content and ads aren't abusive they believe it's a fair bargain.
Ars technica only provides a blurb trough rss and iirc no topic filtered rss, hardly a good or usable solution if one has to get out and find content outside the reader
yeah feedly has been my alternative since google reader died. but the issue is that even if some sources still have feeds, many sources strip feed of all the content and only give you a list of titles and links. that quite sad to witness if one lived trough the rss golden age
RSS has no analytics. that's the big weakness. RSS has been stripped of content even in most other blogs, substituting it for links back to the main sites, which is a workable compromise for webmaster but not one that helps readers. yahoo pipes where a stopgap for a while, until yahoo pulled the plug.
I think what's needed is an intrusive format that delivers metrics and tracking. sure it'd be another tool for control and manipulation, but we'd at least have back the ability to read our news centralized.
> operating systems and hardware all move at lightning pace
not really, last big leap was the ability to unlock gpu for stream processing, and that's it.
it's quite faster today as ten or one year ago, but at it's core it's still a von neumann machine and not much has been discovered ever since, mostly we're repackaging under a new name things that have been discovered in the 70s', like the thick vs thin client debate, which played more or less the same over and over again as the bottleneck switched from bandwidth to latency to client performances, the last iteration of which was ember and angular precompilation.
problem decomposition is maybe not the central skill, but the one that helped me most so far.