Every day, we do about 12 scheduled deploys. During each deploy, an engineer is designated as the deploy commander in charge of rolling out the new build to production. This is a multistep process that ensures builds are rolled out slowly so that we can detect errors before they affect everyone. These builds can be rolled back if there is a spike in errors and easily hotfixed if we detect a problem after release.
Deploys at Slack https://slack.engineering/deploys-at-slack-cd0d28c61701
This is an interesting look at how development is done at Slack. Weirdly, I’m pretty sure I couldn’t get away with this sort of iteration anymore because our community it’s relatively small and hesitant to change.
Once upon a time I did make changes on the fly to add new features or tweak the interface but now folks depends on us to maintain a certain level of stability as they learn about it teach the law. Of course it could be that as I get older I’m less tolerant of getting pinged about changes
Slack uses PHP for most of its server-side application logic, which is an unusual choice these days. Why did we choose to build a new project in this language? Should you?
PHP-the-language has many flaws, which undoubtedly have slowed these efforts down, but PHP-the-environment has virtues which more than compensate for those flaws. And the options for improving on PHP’s language-level flaws are pretty impressive. On the balance, PHP provides better support for building, changing, and operating a successful project than competing environments. I would start a new project in PHP today, with a reservation or two, but zero apologies.
by Keith Adams, Slack Engineering
Source: Taking PHP Seriously
Rather interesting to learn that the server side of Slack is written in PHP. I guess I assumed it was a Ruby or Go thing. I think it’s useful to hear about success stories for a mature language like PHP. It shows us that just because something has been around for awhile doesn’t mean it can’t do something cool.
By default, all members can add apps to a Slack team. Team Owners and Administrators have the option of limiting who can add and approve apps, and can manage which ones are accessible at the team level.
Source: Managing apps for your team – Slack Help Center
Google Calendar Reminders Come to Slack | Several People Are Typing http://slackhq.com/post/124767707715/googlecalendar
We’re a YC-backed indie video game company releasing an open source alternative to Slack.
It’s called “Mattermost” and it’s the team communication service our company’s run on since last year. Like Slack, you can send messages and files across channels, get notifications on unreads and mentions, and search history–all from your PC or smartphone.
Unlike Slack, Mattermost is open source. You can download the code, run it on your own servers, and modify it as you wish.
This was bound to happen sooner or later. Appears to be written in Go.