Skip to content

Instantly share code, notes, and snippets.

@anandthakker

anandthakker/derek-ssc.md

Created September 15, 2015 00:00
Show Gist options
  • Save anandthakker/165269e6ffb86683787f to your computer and use it in GitHub Desktop.
Save anandthakker/165269e6ffb86683787f to your computer and use it in GitHub Desktop.
Download ZIP
Raw
derek-ssc.md

Derek SSC

##Start

  1. Structured technical education for new and current team-members who are coders. Covers coding style, coding for readability and maintainability, and other best practices. Applies to anyone who joins us and is expected to code, more to those who are expected to code all/most of the time.

Right now we have a just-do-it approach where we throw them into the fire and call it teching up. We can't expect people to just osmosis this stuff. It can be more of a mentor/mentee approach or something else entirely, but we have to build time for it, by which I mean, if two people build something and one is expected to teach the other, it takes longer than if that first person just built it.

  1. Make someone the ZOD of communicating to the world what we're doing. This someone must not already be a fully-burdened team member.

  2. More infrastructure developers. We've been focusing on front-end and design lately, but we would be completely lost without good back-end development, and more of that greatly increases the complexity of the work we can take on.

  3. Create a ZOD for each and every BD proposal. Sometimes we do this, other times we crowd-source. Lack of ownership hurts. ZOD should also be person who will do main client comms IMO.

##Stop

  1. The weekly Friday morning meeting I do not find particularly useful for most of the team members involved, and should be more asynchronous. I know we do an asynchronous part where we measure out our time, but that should be the main thing.

  2. We have had trouble getting women to take part in our social events (see game night). Not sure if this is a problem culture-wise since we haven't had many women, but it might be.

##Continue

  1. Trying out new team-members with sprints and generally being thoughtful and thorough in our hiring.

  2. Being a team that values design.

  3. Being a team that values code quality and maintainability.

  4. Reaching for clients/projects that allow for long approaches, refactoring, reiterating, and generally having the chance to test and re-test assumptions.

  5. Automating as much of our build and development processes as possible.

  6. Sharing and communicating via open channels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment