Working with Scott? Here's what to expect!
Caveats:
- I'm pretty aware of my faults - this document isn't my attempt at excusing them.
- This document also isn't an attempt to build trust. That happens as we work together.
- Small-town raised, lived-all-over, Millennial-leaning Gen-Xer (Xennial?) who loves music, cooking, dad jokes, and technology
- I'm pretty much down the middle blue/green. (Supporting or Observing Coordinator)
- I'm ISTP-ish
- Pragmatist - What will work for our team right now? People > process. Real agile
- When it comes to human interaction, boring is bad. Emojis, gifs and cool project names plz
- When it comes to technology boring is good. I love creating cool things with boring tech.
- Don't be a hero - problem prevention > problem solving / planning and pre-Mortems
- Success really comes from consistantly avoiding dumb mistakes rather than trying to be amazing
- Dig yourself (and others) a pit of success
- If it matters enough to be careful, it matters enough to build a system around it.
- We are not paid to write code. We are paid to solve problems and sometimes that means coding
- Continuous improvement - Little by little let's make things better - small improvements are ok if it's consistant
- Process is good - when it's just enough to ease the pain and no more
- Written communication - helps solidify your thoughts (see: https://basecamp.com/guides/how-we-communicate #6 and #7)
- Overcommunicate - No going dark - It's ok to say things more than once
- Data - Let's establish some metrics and start collecting data. Keep data in front of you. How do we measure what we care about? "If you can't make engineering decisions based on data, then make engineering decisions that result in data." - Kent Beck
- Be assertive - not passive aggressive or plain old aggressive. Tact and open communication go a long way