Skip to content
Gilad Gressel edited this page Feb 16, 2017 · 23 revisions

Welcome!

This document is meant to act as a comprehensive tour of our team, so you can jump right in with everyone right away.

Please have a look at our community guidelines when you have a chance. Also have a look at the tips and tricks compiled by previous students.

Active Team Admins:

  • Devon (@geekman2)
  • Nash (@nash)
  • Gilad (@giladgressel)
  • Matt (@mattzhou)
  • Thomas (@tmhughes)
  • Chris (@chrisl)
  • Jon (@solinvicta)
  • Alex (@axlbert)

Please understand we are mostly alumni, but we see ourselves as students just like you!

If you have any questions, comments or concerns about Slack team, or just about how something works feel free to ping us either individually or in #to_admin, one of us is active almost 24/7

ALERT! You are ONLINE and communication is easily confused!

Please keep in mind that our words are not always read the way we intend them to be. example: "It's perfectly obvious that model validation is the most important step" This sentence creates a situation in which your opinion (it is an opinion) is being stated as a fact.

A better way to express this, would be: “It is my opinion that model validation is one of the most important parts of any system” This allows for the possibility that you’re wrong, without implying that anyone who disagrees must be ignorant.

Some Slack tips:

  • You can write single-line code in a message by wrapping it in backticks ` , and multi-line code with three, like this ```
  • Snippets, which can be created by hitting the plus sign on the left, are for large code blocks
  • Make sure to set your notifications, slack allows great customization, you can set notifications by specific words, and by specific channels.
  • You can @mention someone and it will notify them.

Inactive Admins:

  • Mikel (@anokas)
  • Josh (@joshuacook)
  • Mikael (@Mikael)
  • Bharat (@param.bharat)