Skip to content

Instantly share code, notes, and snippets.

@pfeilbr

pfeilbr/thinking-architecturally.md

Last active May 22, 2024 07:02
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save pfeilbr/927c470897c97b354f59c8122d095672 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save pfeilbr/927c470897c97b354f59c8122d095672 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. pfeilbr revised this gist May 13, 2021. 1 changed file with 0 additions and 1 deletion.
    1 change: 0 additions & 1 deletion thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -71,5 +71,4 @@
    * need to be visible to team
    * need to be reviewed on regular basis
    * just because you can measure it doesn't mean it matters
    * SLO
    * avoid resume driven design
  2. pfeilbr revised this gist May 13, 2021. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -6,7 +6,7 @@
    * [Thinking Architecturally: Lead Technical Change Within Your Engineering Team](https://learning.oreilly.com/library/view/thinking-architecturally/9781492034421/) - oreilly book
    * [Infrastructure & Ops Superstream Series: CI/CD](https://learning.oreilly.com/videos/infrastructure-ops/0636920531654/) - oreilly video
    * [Building Evolutionary Architectures](https://learning.oreilly.com/library/view/building-evolutionary-architectures/9781491986356/) - oreilly book
    ### Notes
    ### Notes ([Thinking Architecturally - Nathaniel Schutta](https://www.youtube.com/watch?v=d5bNZX8tpiI) youtube video)

    * AaaS - Architecture-as-a-Service
    * many competing agendas
  3. pfeilbr revised this gist May 13, 2021. 1 changed file with 8 additions and 0 deletions.
    8 changes: 8 additions & 0 deletions thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -65,3 +65,11 @@
    * *"evolutionary arch supports guided, incremental change across multiple dimensions"*
    * `[arch]`fitness functions
    * `0: make arch change, 1: eval result, 2: closer to goal? yes -> keep, no -> trash, 3: -> goto 0` *(basic regression iterations as in stats/ML)*
    * set of tests we exec to validate arch. *(arch unit tests)*
    * reminds everyone on the team what's important for your arch
    * informs discussions around tradeoffs
    * need to be visible to team
    * need to be reviewed on regular basis
    * just because you can measure it doesn't mean it matters
    * SLO
    * avoid resume driven design
  4. pfeilbr revised this gist May 13, 2021. 1 changed file with 3 additions and 2 deletions.
    5 changes: 3 additions & 2 deletions thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -59,8 +59,9 @@
    <img src="https://www.evernote.com/l/AAHMoUYQ7Y1Jyq7b1-9Czp1FbEVI4zr0-NQB/image.png" alt="" width="50%" />
    * nobody tells you which criteria to use, up to you, need to make with incomplete information
    * architects spread thin, need to scale with principles, north stars, etc.
    * fitness functions
    * arch agile backlash.
    * chose tech that can evolve - evolutionary arch
    * create arch with expectation of change. à la werner *"everything fails, all the time"*
    * *"evolutionary arch supports guided, incremental change across multiple dimensions"*
    * *"evolutionary arch supports guided, incremental change across multiple dimensions"*
    * `[arch]`fitness functions
    * `0: make arch change, 1: eval result, 2: closer to goal? yes -> keep, no -> trash, 3: -> goto 0` *(basic regression iterations as in stats/ML)*
  5. pfeilbr revised this gist May 13, 2021. 1 changed file with 0 additions and 1 deletion.
    1 change: 0 additions & 1 deletion thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -18,7 +18,6 @@
    * computer science - lifetime learning
    * education doesn't end. lifetime of learning.
    * developers have strong opinions
    * Is this your game plan :) https://youtu.be/d5bNZX8tpiI?t=598 (retirement countdown comment)
    * new and old tech https://youtu.be/d5bNZX8tpiI?t=681
    * new - unfinished, unbuggy, unproven
    * old - refined, stable, tested
  6. pfeilbr revised this gist May 13, 2021. 1 changed file with 1 addition and 0 deletions.
    1 change: 1 addition & 0 deletions thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -64,3 +64,4 @@
    * arch agile backlash.
    * chose tech that can evolve - evolutionary arch
    * create arch with expectation of change. à la werner *"everything fails, all the time"*
    * *"evolutionary arch supports guided, incremental change across multiple dimensions"*
  7. pfeilbr revised this gist May 13, 2021. 1 changed file with 2 additions and 1 deletion.
    3 changes: 2 additions & 1 deletion thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -5,6 +5,7 @@
    * [Thinking Architecturally - Nathaniel Schutta](https://www.youtube.com/watch?v=d5bNZX8tpiI) - youtube
    * [Thinking Architecturally: Lead Technical Change Within Your Engineering Team](https://learning.oreilly.com/library/view/thinking-architecturally/9781492034421/) - oreilly book
    * [Infrastructure & Ops Superstream Series: CI/CD](https://learning.oreilly.com/videos/infrastructure-ops/0636920531654/) - oreilly video
    * [Building Evolutionary Architectures](https://learning.oreilly.com/library/view/building-evolutionary-architectures/9781491986356/) - oreilly book
    ### Notes

    * AaaS - Architecture-as-a-Service
    @@ -62,4 +63,4 @@
    * fitness functions
    * arch agile backlash.
    * chose tech that can evolve - evolutionary arch
    * create arch with expectation of change. à la werner *"everything fails, all the time"*
    * create arch with expectation of change. à la werner *"everything fails, all the time"*
  8. pfeilbr revised this gist May 13, 2021. 1 changed file with 6 additions and 0 deletions.
    6 changes: 6 additions & 0 deletions thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -57,3 +57,9 @@
    * what is the appropriate scale for evaluation. e.g. 1-5
    * harvey balls. images to remove the *"hard number"* focus effect
    <img src="https://www.evernote.com/l/AAHMoUYQ7Y1Jyq7b1-9Czp1FbEVI4zr0-NQB/image.png" alt="" width="50%" />
    * nobody tells you which criteria to use, up to you, need to make with incomplete information
    * architects spread thin, need to scale with principles, north stars, etc.
    * fitness functions
    * arch agile backlash.
    * chose tech that can evolve - evolutionary arch
    * create arch with expectation of change. à la werner *"everything fails, all the time"*
  9. pfeilbr revised this gist May 13, 2021. 1 changed file with 4 additions and 1 deletion.
    5 changes: 4 additions & 1 deletion thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -53,4 +53,7 @@
    * pros and cons - always trade-offs
    * "it depends" means -> tell me more. not a stopper.
    * ack the negatives. the most insight is learned from this question
    * "You haven't mastered a tool until you understand when it should not be used" - *Kelsey*
    * "You haven't mastered a tool until you understand when it should not be used" - *Kelsey*
    * what is the appropriate scale for evaluation. e.g. 1-5
    * harvey balls. images to remove the *"hard number"* focus effect
    <img src="https://www.evernote.com/l/AAHMoUYQ7Y1Jyq7b1-9Czp1FbEVI4zr0-NQB/image.png" alt="" width="50%" />
  10. pfeilbr revised this gist May 13, 2021. 1 changed file with 3 additions and 1 deletion.
    4 changes: 3 additions & 1 deletion thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -51,4 +51,6 @@
    * security - want to stay safe, need to go fast. time feeds black hats
    * policy needed. measure and enforce, hard part
    * pros and cons - always trade-offs

    * "it depends" means -> tell me more. not a stopper.
    * ack the negatives. the most insight is learned from this question
    * "You haven't mastered a tool until you understand when it should not be used" - *Kelsey*
  11. pfeilbr revised this gist May 13, 2021. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -4,6 +4,7 @@

    * [Thinking Architecturally - Nathaniel Schutta](https://www.youtube.com/watch?v=d5bNZX8tpiI) - youtube
    * [Thinking Architecturally: Lead Technical Change Within Your Engineering Team](https://learning.oreilly.com/library/view/thinking-architecturally/9781492034421/) - oreilly book
    * [Infrastructure & Ops Superstream Series: CI/CD](https://learning.oreilly.com/videos/infrastructure-ops/0636920531654/) - oreilly video
    ### Notes

    * AaaS - Architecture-as-a-Service
    @@ -50,3 +51,4 @@
    * security - want to stay safe, need to go fast. time feeds black hats
    * policy needed. measure and enforce, hard part
    * pros and cons - always trade-offs

  12. pfeilbr revised this gist May 13, 2021. 1 changed file with 4 additions and 2 deletions.
    6 changes: 4 additions & 2 deletions thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -2,7 +2,7 @@
    ## [Thinking Architecturally](https://www.youtube.com/watch?v=d5bNZX8tpiI)
    ### Source Resources

    * [Thinking Architecturally](https://www.youtube.com/watch?v=d5bNZX8tpiI) - youtube
    * [Thinking Architecturally - Nathaniel Schutta](https://www.youtube.com/watch?v=d5bNZX8tpiI) - youtube
    * [Thinking Architecturally: Lead Technical Change Within Your Engineering Team](https://learning.oreilly.com/library/view/thinking-architecturally/9781492034421/) - oreilly book
    ### Notes

    @@ -47,4 +47,6 @@
    * briefing pans out -> workshop/invest more in it
    * greenfield always works. need to use in target env to understand constraints
    * start with low risk capability / not company core

    * security - want to stay safe, need to go fast. time feeds black hats
    * policy needed. measure and enforce, hard part
    * pros and cons - always trade-offs
  13. pfeilbr revised this gist May 13, 2021. 1 changed file with 4 additions and 2 deletions.
    6 changes: 4 additions & 2 deletions thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,7 +1,8 @@

    ## [Thinking Architecturally](https://www.youtube.com/watch?v=d5bNZX8tpiI)
    ### Source Resources

    * [Thinking Architecturally](https://www.youtube.com/watch?v=d5bNZX8tpiI)
    * [Thinking Architecturally](https://www.youtube.com/watch?v=d5bNZX8tpiI) - youtube
    * [Thinking Architecturally: Lead Technical Change Within Your Engineering Team](https://learning.oreilly.com/library/view/thinking-architecturally/9781492034421/) - oreilly book
    ### Notes

    @@ -45,4 +46,5 @@
    * architectural briefing - one person does research, presents back to team. short ~45min
    * briefing pans out -> workshop/invest more in it
    * greenfield always works. need to use in target env to understand constraints
    * start with low risk capability / not company core
    * start with low risk capability / not company core

  14. pfeilbr created this gist May 13, 2021.
    48 changes: 48 additions & 0 deletions thinking-architecturally.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,48 @@
    ## [Thinking Architecturally](https://www.youtube.com/watch?v=d5bNZX8tpiI)
    ### Source Resources

    * [Thinking Architecturally](https://www.youtube.com/watch?v=d5bNZX8tpiI)
    * [Thinking Architecturally: Lead Technical Change Within Your Engineering Team](https://learning.oreilly.com/library/view/thinking-architecturally/9781492034421/) - oreilly book
    ### Notes

    * AaaS - Architecture-as-a-Service
    * many competing agendas
    * technology change is a constant
    * nobody wants to be on legacy platform
    * java foundational tech for aws, google, twitter, netflix, etc.
    * how to evaluate technology
    * chasing the new things
    * computer science - lifetime learning
    * education doesn't end. lifetime of learning.
    * developers have strong opinions
    * Is this your game plan :) https://youtu.be/d5bNZX8tpiI?t=598 (retirement countdown comment)
    * new and old tech https://youtu.be/d5bNZX8tpiI?t=681
    * new - unfinished, unbuggy, unproven
    * old - refined, stable, tested
    * predictable hype cycle
    * how do we know where not to use tech. takes trial and error.
    * asked to build something never built before, using tools we got a few weeks ago, shocked we don't know how long it takes
    * developer get bored quickly
    * learning keeps it fresh
    * commit at some point. can't constantly experiment
    * bleeding edge ... means you will bleed
    * pioneers ... ones with arrows in back
    * hope is not a strategy
    * need to be deliberate when it comes to technology choices
    * challenge is how to keep up (*"technology merry go round"*)
    * make it part of routine to learn
    * "morning coffee" - peruse the tech news
    * attention is most precious resource you have
    * attention is a resource. it doesn't scale.
    * don't waste your attention. have to be selective.
    * if its a big enough deal, you will hear about it.
    * how do we know where to invest our time?
    * be aware of bias
    * skating to where the puck was
    * thoughtworks technology radar
    * 20% projects are good space, but fallen out of favor in some circles
    * innovation fridays
    * architectural briefing - one person does research, presents back to team. short ~45min
    * briefing pans out -> workshop/invest more in it
    * greenfield always works. need to use in target env to understand constraints
    * start with low risk capability / not company core