Fork me on GitHub
#bof-arch-engineering-ops
<
2020-10-14
>
Dan Greenberg21:10:00

Friendly reminder we are operating today's discussion using Chatham House Rules - When a meeting, or part thereof, is held under the Chatham House Rule, participants are free to use the information received, but neither the identity nor the affiliation of the speaker(s), nor that of any other participant, may be revealed. If you'd like to post your thoughts in this Slack channel… remember they should be non-attributable (per the Chatham House Rule).

Dan Greenberg22:10:13

Thanks all for another great session! As always, notes below and keep up the chatter on Slack!

• CI/CD
        o Initial setup can take lots of time – is that a one-time setup at the beginning of a 
          project or throughout the lifecycle?
        o Automation is critical
             Generate github repos by automated process
        o Standardization by teams thinking what another team is doing is really cool rather than by 
          mandate
             Showcases at end of each sprint
• Test-driven development
    o It seems to be a common struggle – everyone understands the benefits
    o It is a difficult habit to get into because as a developer, I want to sit down and write
      something that I see work, I want to dive into the problem
    o It's rare to find a team with a strong TDD champion
    o For the most part, testing "culture" is not bad per se it's just not best practice
• Product Teams
    o Should have resources you need during the Sprint when you need them
    o Cross-functionality – core product team but rotate in other members as needed and they can roll
      back off when sprint is done
• Experimentation – keep what works and throw out what doesn't

Nick Jenkins (Director, Mech Rock DevOps, Perth, Oz)22:10:37

Ugh! You said "best practice" - yuk.

😁 1
Nick Jenkins (Director, Mech Rock DevOps, Perth, Oz)22:10:16

Pet peeve of mine. Some people use the term to win an argument... "but this is best practice" etc. Also denies continuous improvement. If your following 'best' practice why would you change?

jeff.gallimore (CTIO - Excella, he/him)23:10:27

agreed. i’ve eliminated the use of “best practice” from my vernacular. all practices are context-dependent and YMMV.

Nick Jenkins (Director, Mech Rock DevOps, Perth, Oz)23:10:17

if I must I will substitute "industry leading practice" but only through gritted teeth.

Dan Greenberg22:10:34

Agreed! One reason why I really liked where our discussion ended - experiment, try things for a Sprint or two, throw out what doesn't work and keep what does