Seonglae ChoSystem Design
- To reduce coupling and increase cohesion, and to be flexible wherever possible to inject
- Any system depends on many things below it. Know what they are.
- Ability to change decisions outweigh the importance of the decisions
- Introduce only essential complexity
Software Designs
System Architecture Notion
Structuring your Infrastructure as Code | lbr.
If you’re thinking of migrating to another infrastructure as code tool (and why would you, everything is great in the IaC world now, right?!) you might find yourself asking yourself
https://leebriggs.co.uk/blog/2023/08/17/structuring-iac
Flexible systems | Organizing Chaos
Most decisions that you make are not nearly as important as your ability to change them in the future. When designing systems, it’s easy to get caught up in the minutia of each decision that has to be made along the way. Technical systems may raise concerns about choosing the appropriate logging framework or determining the most effective concurrency model. Human systems may instead be concerned with how many meetings to hold, with whom, and how often.
https://jordankaye.dev/posts/flexible-systems/
Software should be designed to last
adlrocha.substack.com
https://adlrocha.substack.com/p/adlrocha-software-should-be-designed?utm_campaign=Newsletter&utm_medium=email&_hsmi=90461945&_hsenc=p2ANqtz-9-QR0NFz20V-hb2e4QcOnKI-Flft1sCpHIJcdpdwXZJ_ReoTGgc8nj1_jSFaA1QlMp1GS-39ndbMzNQ2XFYnIMUopKDw&utm_content=90461945&utm_source=hs_email
As the scale grows, a system becomes stronger against external threats but more vulnerable to internal corruption and distortion. Before building a large system, first think about how you would prevent it from being corrupted or hijacked later.
Do not conquer what you cannot defend — LessWrong
Once upon a time there was a great king. He ruled his kingdom with wisdom and economically literate policies, and prosperity followed. Seeing this, t…
https://www.lesswrong.com/posts/jinzzbPHshif8nmnw/do-not-conquer-what-you-cannot-defend
