- They display a “list” of something.
- They show you a more complete “view” of one thing on the list.
- Filter: works on a list to limit entries on the list. For example: when you type “cute cat videos” into Google, the “list” returned is pretty much filter to the 116,000,000 relevant results.
- Sort: changes the sequence of the list. For example, you can sort you mail by date or by the from email address.
- Add: you are creative and are going to use the “C” from CRUD to add a new entry to the list
- Delete: OK, your creation wasn’t so good or maybe if you delete the bagel from your diet app, it will delete it from your belly, too.
- View: this one is easy, send me to the “view” for this list entry (the R in CRUD)
- Categorize: Think folders in email, or subreddits, meals in your food tracker, bookmarks or favorites in your browser
- Refresh: in case your “list” of tweets is getting stale
- Copy: Hmmm, maybe. But isn’t “Copy” just a “View” tied to an “Add”
- Update: you changed something and want to save or update (the U in CRUD) some data
- Delete: this action is shared with the list
- Add (Copy): again shared with the list.
Slack has become a very popular platform for internal business communications. For those that aren’t familiar, Slack is a messaging platform with some extended features that make it very useful for teams. My favorite feature is the concept of “channels” where you can combine messages related to a particular topic.
So back to why we decided to use Slack. Quick answer, system outages. When systems are unavailable for any reason, we end up texting, emailing, and calling. As the response grows, we typically need to add people to the effort. So now there are multiple threads on multiple platforms that they need to catch up on. Slack solves that.
Now they can jump on our #system_outage channel, and the entire effort from every member of the team is right there. It also becomes a historical record of who did what and when to resolve the issue. This can be searched later if we have similar problems.
What’s next? We look to expand the use of Slack to cover all sorts of team communication and collaboration. We are looking at a #change_management channel to consolidate communication and track approval of changes to the production environment. We’ve started a #support channel for our helpdesk team to work with the application and infrastructure teams to solve problems. Next we plan to see how it works for projects where, for example, we could hold virtual daily stand-ups.