The last couple of months I have found myself back at Kaiser and since my return we moved off of Lotus Notes (THANK GOD!) moving to Office 365. The addition of ChatBots and open APIs allowing services to feed information back into channels made us a very highly functioning team without needing a ton of staff.Īlright skip to today. I saw this a several places and the DevOps guys at Hart had pretty much mastered using Slack (or IRC or whatever) as the method of monitoring the environment and taking action on events. Namely with smaller companies that needed to communicate quickly and track things on the fly. Now that large enterprises are using its not cool anymore (sidenote: you ever notice with big companies pickup a term its like your parents using slang and doing it wrong?)Īnyway, when I was working outside of Kaiser, platforms like Slack and HipChat started to take off in the industry. I really can't wait for it all just to be called Operations again IMHO the marrying of words with "Ops" kind of played itself out before it started. This is really because of all of the DevOps and *Ops lingo that is being tossed around the industry. The term started showing interest in about 2012 then interest really took off in 2015 according to Google Trends. In the last couple of years the term has been floated around "ChatOps". I have friends that I almost consider family that I have only ever talked to over chat and not over any other kind of social network. Chat is always been very important to me. Over the years I have used IRC, Sametime, AOL IM, Slack and RocketChat to communicate with my fellow engineers/bosses. Maybe I have hit a turning point in my life, but I am really impressed with what Microsoft has done with Office 365 Teams.
ONENOTE SIDENOTES 2015 SOFTWARE
Those of you that know me, know that I can be one of the largest critics of Microsoft the company and lets not get started about their software (#linuxforlife).
0 kommentar(er)
