We recently decided it was time for a major update to the public side of Scout. We’d start with a more polished homepage. Since we’re both developers, the obvious next step seemed like hiring a designer. However, working with an outside designer isn’t a hire-and-forget experience:
- Good designers are difficult to find. Design doesn’t scale like a product business.
- Good designers are busy. It could take 30-60 days to start work, then another 30 days for it to come together. This means we could be looking at a 90 day timeline. We wanted to launch it faster.
Instead of starting work with a designer on a blank slate, we decided to start firming up what we wanted the homepage to look like. We’d end up with one of the following outcomes:
- We’re terrible at design, but we’ve at least thought it through. Hire a designer.
- We can get 80% of the way there, but we’ll need a designer for touchups.
- If we iterate enough, we can launch something we’ll be happy with.
Startup Lessions from CCP - EVE Online Style:
Another great example was the formation of “Team Best Friends Forever” (“BFF” is an inside EVE joke). This team is a group of CCP developers whose sole mission is not to work on major features and improvements, but rather to fix all those annoying “little things” that bother their customers. Too many times, product managers and development teams are focused on the big-ticket items – and that’s fine, but TBFF is a great approach that again proves that CCP listens to their customers.
On Jan 15th, all Scout accounts will be switched over to notification groups. Notification groups are designed to make notifiation management easier and more flexible:
- instead of managing notifications per-plugin/per-user, you will assign users to notification groups, and apply notification groups to triggers.
- you can have multiple PagerDuty integrations and webhook endpoints and assign those to notification groups as well. PagerDuty and webhooks are now first-class notification channels; they are no longer all-or-nothing settings.
- you get much finer control over threshold-to-notification channel mappings. You can configure (for example) three triggers on one metric, with the lowest trigger sending you email, the middle trigger sending you SMS, and the high trigger alerting PagerDuty.
If 2011 was the year of fine-tuning, 2012 was the year of major feature enhancements at Scout. Some stats on what’s been a fun year:
Naomi Pomeroy, a Food & Wine Best New Chef, on starting an underground, self-funded restaurant:
When major chefs hear about the way I run Beast, they say, ‘You’ve created a chef’s dream restaurant, because you don’t have to compromise,’ ” she told me. “What happens when you do a million-dollar build-out is that you have to be open seven days a week, be really high end, and have a million choices, and that may not work in today’s economy.
Read more in the New Yorker.
In the Colorado Front Range area? I’ll be talking about the realtime web at the Fort Collins Ruby Meetup this Wednesday.
I’ll show how adding realtime functionality is the easy: in less than 30 minutes, we’ll build a Sinatra app that uses Pusher for realtime functionality.
See the demo Sinatra app, a Ruby Meetup Realtime Heckle Board on Github.
Our navigation header was packed-full of links (and let’s be honest, looked a little stale). We’ve elected a new, fresher, nav header:
What you need to know
- We’ve emphasized the primary pieces of Scout (servers, applications, charts, and dashboards). The less-accessed config-related bits are inside a pulldown in the upper right (people, notifications, billing, etc).
- Hotkeys plus keyboard navigation is the best way to play. Each of the primary areas has an associated pulldown. Reveal each pulldown with a hotkey (the underlined letter in the nav). For example, hit the “s” key to reveal the servers pulldown. Once the pulldown is open, use your up/down keys + enter to navigate.
- We’ve dropped the recently accessed server tabs. These frequently created confusion: how the initial set of tabs was chosen, how they reacted when a new server was picked that shuffled a previously accessed tab off the list, etc. Using the “s” hotkey is the fastest way to travel to your servers within Scout.
The hotkeys for each pulldown (the first letter of each word):
- s – Servers
- a – Applications
- c – Charts
- d – Dashboards
Once a pulldown is open:
- up/down arrow keys – navigate through the list of items
- enter – show the current item
- esc – close the pulldown
If you see any issues, let us know!
The Scout gang (including founders and co-dictators-for-life Derek and Andre) will be at Rocky Mountain Ruby Conference in beautiful Boulder, Colorado next week.
If you’re going to be there, let us know. We’d love to take our relationship beyond our support email address (if you’re ready for that).
Gavin Stark and the Real Digital Media team are Campfire power users. Back in April, Gavin created a Hubot script to send Scout alerts to their chatroom. Now, they needed visuals:
We wanted to grab some of the graphics that Scout’s in-app page offers to users to provide us with visual feedback on historical norms for each metric without leaving the chat room. A call to Scout support got graphics ported into the API in less than a day, and we were off and running.
His sparkline update hasn’t been merged into the Hubot repo yet, but you can view his fork
Every man has their breaking point when it comes to deadweight code. Andre and I hit ours recently and decided to spend all of last week focusing soley on cleaning up Scout (a Rails app). Our goals:
- Faster tests – our tests took 8 minutes to complete. While it’s the perfect amount of time to catchup on Daily Show clips, it really tested our patience making application-wide changes.
- Removing deadweight – unused CSS rules, database tables + columns, views, and assets. It’s good having certainty that modifying code will change something in the application.
Here’s how we went about it: