|
|
|
|
|
by mortenjorck
5293 days ago
|
|
A startup blogger writes a polemic with a blatantly baiting headline. Within 24 hours, another startup blogger will write a rebuttal with an equally baiting headline. Both will incite winding debates on Hacker News. Meanwhile, other people will somehow manage to create value, ostensibly the goal of both bloggers, without writing confrontational screeds, perhaps even writing insightful blog posts intended to inspire and challenge rather than stir up conflict. Maybe it's writing polemics that is horseshit. |
|
It's pretty specific and clear: it argues that plenty of startups are successful with virtually no design at all, with interfaces as clunky as "clients call us on the phone" or "emailing spreadsheets back and forth". It implicitly argues, "early stage startups are continuously faced with a choice of spending energy on design† or on customer discovery", and "early stage startups should virtually always opt for customer discovery".
I can see how a reasonable person might disagree with that.
I don't see how a reasonable person could say that the question isn't a reasonable one to pose.
† Admittedly a synecdoche for lots of other things, like scalability, code quality, test coverage, &c