tag:blogger.com,1999:blog-3615332969083650973.post8617450094838617918..comments2024-03-23T07:59:04.047-04:00Comments on sysadvent: Day 7 - Change and Proximity of CommunicationJordan Sisselhttp://www.blogger.com/profile/13694925032675599790noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3615332969083650973.post-19564023204196567692011-12-07T19:09:04.833-05:002011-12-07T19:09:04.833-05:00asq: Agreed, the more you can make a change visibl...asq: Agreed, the more you can make a change visible as you do it, the better. The examples I gave were mostly focused on when folks are working with a change made in the past where they may not have seen, or may have forgotten about, anything they got via email/twitter/etc.Aaron Nicholshttps://www.blogger.com/profile/05289960213483312797noreply@blogger.comtag:blogger.com,1999:blog-3615332969083650973.post-25613480179975424322011-12-07T09:44:35.138-05:002011-12-07T09:44:35.138-05:00i'd add a local instant comm server (like irc,...i'd add a local instant comm server (like irc, xmpp conference, or - prefered by me - identica instance) which is being followed be all interested parties, and can be accessed by variety of devices. email may be overlooked, jabber too, user may never logout to see updated motd, and with twitter clone everyone can define how they wish to receive updates - mobile client, sms, email, xmpp, and what is the scope of their interest - by deploying hashtags. ie.<br /><br />!production !portal deploy in 5, don't touch puppet, please.asqnoreply@blogger.com