>"Corollary: No one needs real-time" If you've ever run service where you're anticipating a large traffic spike and you need to monitor server stats, real-time statistics are invaluable.
Or you release a new version of a game and you notice your arpdau tanks. ;)
The laws of shitty dashboards
11–20 of 126 posts
Re: The laws of shitty dashboards
#12Most articles are shitty, this is an example of one. Most technical articles are written by someone blinkered by their specific experience which they feel is so wonderful that they should share with the world. Save the internet from such dross and write it on a piece of paper, roll it up and shove it up the ares your talking out of.
Writing in the public view is a great way to get feedback on your writing and the subjects you discuss—e.g. corrections, further education, etc. For some people, it also increase the pressure to improve.
Vanity is only one possible reason for writing in the public view, and it's an exercise with large potential gains. Your perspective is entirely off, and you've decided to take an opportunity to attack someone who was either brave enough or indifferent enough to risk being attacked in the first place.
Re: The laws of shitty dashboards
#13Re: The laws of shitty dashboards
#14Earlier quoted context omitted.
I can only agree. Especially real-time data. There are only a few cases where real-time might be usefull
If you have a site delivering real time content, such as news, its pretty important.
Of course if you are marketing an analytics product, give the customer a realtime dashboard. It's useless but it makes them feel powerful and in control. The news writers would certainly have thrown a fit if we tried to take away their useless chartbeat.
Re: The laws of shitty dashboards
#15>"Corollary: No one needs real-time" If you've ever run service where you're anticipating a large traffic spike and you need to monitor server stats, real-time statistics are invaluable.
"Will a decision be made in real-time based on this information?"
Re: The laws of shitty dashboards
#161) http://www.kaushik.net/avinash/digital-dashboards-strategic-...
2) Information Dashboard Design by Stephen Few - http://www.amazon.ca/Information-Dashboard-Design-Effective-...
Re: The laws of shitty dashboards
#17>"Corollary: No one needs real-time" If you've ever run service where you're anticipating a large traffic spike and you need to monitor server stats, real-time statistics are invaluable.
Re: The laws of shitty dashboards
#18Assuming the author meant car, this would be very dangerous (i.e. irreversible engine damage): http://en.wikipedia.org/wiki/Redline
Re: The laws of shitty dashboards
#19This annoyed me a little bit. A check engine light is the perfect component for what it does. If it's on it means that something may be seriously wrong and that you're probably too stupid or ill-equipped to fix it.
If it was something simple, easily detectable and fixable it would have its own light, ie the door is open, you're running out of gas.
Re: The laws of shitty dashboards
#20Most articles are shitty, this is an example of one. Most technical articles are written by someone blinkered by their specific experience which they feel is so wonderful that they should share with the world. Save the internet from such dross and write it on a piece of paper, roll it up and shove it up the ares your talking out of.
By the way, the correct word in this situation is "you're"