In a previous post, I mentioned how I get notified of the restaurant menu via a Ruby script. Recently I’ve moved to a totally different product area and the main communication channel we use is Slack. Naturally enough, I ported the Ruby code I wrote, and it now posts the menu every day to our Slack channel. This also got me thinking of what other information would be handy to have.
In the last year and a half, I set up a Ruby based Dashing dashboard for my team and others in our product area. Here’s what a sample Dashing dashboard looks like: It’s been a huge success, but it was tough to gain traction along the way. Here I’ll summarise what I’ve learned (in no particular order): Don’t do dashboards for managers, do them for teams Use big text, have the minimum information as required Use colours (preferably like the traffic light system) to focus attention Link in all critical systems to daily work Make it a one stop shop and faster then all other methods of getting this information Reuse the work of others (steal with pride) Don’t bother with graphs Below I outline the reasons for each point:
I love trying to automate the world, it just feels like magic some of the time! I also really enjoy information coming to me, instead of having to seek it. As we are still only in 2016, we have no world killing Artificial Intelligence (yet). So we have to start small, ease the first world problems! So I decided to make my workplaces' restaurant menu come to me! I decided to write it in Ruby and use push notifications, rather than email or SMS.
Apologies to those visiting my site recently because: It hasn’t been updated recently I have been changing hosts with it Let me explain both of these! I have been searching for a good blogging engine ever since I have started blogging. I have yet to find the perfect one :) Some have come close in completeness (WordPress) or price and ease of use (blogger), but none has been all-encompassing.