91–100 of 126 posts
>"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.
I don't believe it is possible, but it seems like an extremely useful feature.
Tableau is an awesome data aggregate and dashboard program.
The final key with Tableau is the possibility of endlessly refining the data. So you can star with basic dashboard view, but you can narrow it down to the things that really do matter. It's not a dashboard, it's a data discovery tool when used by experienced analyst and great fun for not so experienced guys too. If we compare it to other popular similar tools like QlikView.
Btw. Many of QlivView dashboards are just those top results of Google Dashboard search.
>They also employ UX techniques that dates from a time where the only UI component you can use was a light bulb. If that red thing is critical, can’t you tell me right away what it means? This 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 somethi…
Nothing real time, no dashboards, static data, but customers love it.
This is so arrogant. If your customers are not interested in target demographics then ok. Generalising this to everyone is not ok.
Am I the only one that doesn't get the joke about what's wrong with "Last 14 days" and "Last 12 months"?
14 days = 2 weeks 3 months = a quarter 12 months = a year
>"Most KPIs (traffic, revenue) are too volatile on a daily basis to be useful. Yet “last 30 days daily” is more or less the default option." YES! If you're building a dashboard, don't answer the question "what data do I have?" or "what does the brass say this should be?" But instead, get out and talk to users, find out what data is most important to them, think outside the box, throw some different ideas out there an…
Earlier quoted context omitted.
No, automation is always the answer. When you are forced to formalize processes with code you invariably find all sorts of hidden assumptions. This has happened to me every single time I've tried to automate legacy manual processes. There are always hidden assumptions that are unearthed. Unearthing hidden assumptions is always worth the effort.
A hidden assumption behind what you wrote is that all automation is like the scripts you've written to automate your processes. There are things which automating them would take lots of man-months and tens of thousands of dollars, so much that the effort is not worth it from the savings -- or from any "hidden assumptions" you discover.