3 ms·
That sort of minimalist looking webpage using a big round font for the headers really does make it hard to absorb the gist of the post - sorry, have I overreact
by munk-a 8y ago
That sort of minimalist looking webpage using a big round font for the headers really does make it hard to absorb the gist of the post - sorry, have I overreacted? Perhaps a less fleeting writing style could have set up a more concrete thesis that would deliver a conclusion to their statement.
That last bit is actually quite relevant - due to law of triviality and such there will always be bikeshedding, but the way to cut through that (in my opinion) is to clearly set a scenario, set an agenda, open with a problem and set the dialog up to resolve the problem. This is why I have begun (usually) refusing any meetings without a clearly outlined agenda, and when agendaless meetings get an agenda sometimes I'll duck out of the meeting and submit feedback in writing _to_ the agenda. This is also why I have a bit of an issue with this article, it is titled in such an irrelevant manner that it can't help but generate bikeshedding around it - the title is good and catchy sure, but I really don't understand how it relates to the actual meat of the article (which does raise some relevant points).
If the suggestion is that naming (adding a short descriptor) to... "stuff" makes it easier to keep discussions about that stuff on topic then please back it up with an example, provide some justification, instead the article reaches ~95% then doing a hard right to inject a catchy quote that seems unrelated to the rest of the verbiage.
- danabramov 8y agoI love the meta-ness of this comment. Not sure if it was intentional :-) One concrete example of naming a problem is “callback hell”. Example of “telling a story” to explain it: https://tirania.org/blog/archive/2013/Aug-15.html https://tirania.org/blog/archive/2013/Aug-15.html Once you have a few articles like this, the quality of discussions on the topic rapidly goes up. For React, David Nolen’s and James Long’s early posts did the same thing.
- munk-a 8y agoIt was, to my knowledge there isn't a great way to flag that sort of thing on the web (short of * WINK *)... I thought the fact that I apologized for having "overreacted" when discussing the blog post hosted on overreacted.io would be a bit of a give away. That callback hell story differs from the one above in that I think it delivers a much better summary statement at the end and way forward - I have some opinions on it's aim as I think it is eschewing power in terms of a more comfortable expression for imperative programmers - but the article is well sized, clear, humorous and suggests a solid remediation for the perceived problem.
- stonogo 8y ago> That sort of minimalist looking webpage using a big round font for the headers really does make it hard to absorb the gist of the post - sorry, have I overreacted? I agree, but fortunately for us the people who adopt this weird presentation format almost universally write in a very specific style. I find it easier to just read the headers (or, if they're really bad writers, the headers plus the sentences they felt necessary to typeset in bold), since that's usually the whole message. The rest is some kind of weird boilerplate, like the narrative version of lorem ipsum. If there were more consistency in HTML tag usage I'd write a browser extension to throw everything away except the useful text, but we haven't reached that design mecca yet.
- petercooper 8y agoI'm trying to figure out what both you and the grandparent poster are getting at. Usually on HN we're criticizing people for having too much crap on their pages, hard to decipher designs, tiny text, and what not.. not that their pages are clean and minimalist. What's "weird" about a clean page that's mostly text?
- nurettin 8y agoIt was bikeshedding. Possibly meant as irony.
- petercooper 8y agoThanks, OK, I'm glad there's at least a chance it was humor I didn't pick up on :-)