🔨 Simple, but not too simple

There is nice speech https://www.youtube.com/watch?v=ZSRHeXYDLko Preventing the Collapse of Civilization / Jonathan Blow (Thekla, Inc). My key takeaways:
- We are losing knowledge, instead of gaining it
- Software development is also affected. It's becoming too complex
- Many developers rely on frameworks and libraries without understanding how they work
- Ancient civilizations collapsed partly because they lost the ability to maintain critical knowledge. We may be repeating the same mistakes.
- Open-source and documentation aren't enough. Without real understanding and hands-on experience, it becomes useless over time.
- Short-term thinking leads to long-term problems & creating tech debt.
- We need to relearn simplicity. Instead of making systems more complex, we should focus on simplifying them so they can be understood by future generations.

As a sollution for the state problem there the answer https://aws.amazon.com/builders-library/reliability-and-constant-work/ :
- Simple systems fail less: The more complex a system, the more things can break.
- Avoid over-engineering: Adding unnecessary features or dependencies increases risk. Build only what’s needed.
- Automation should simplify, not overcomplicate: Automate repetitive tasks, but don’t create overly complex automation that’s harder to maintain than the problem it solves.
- Fewer Moving Parts = Fewer Failures
- Chaos Testing: If random failures cause unpredictable issues, the system is likely too complicated and it's time to review it.
- Learning from failures: After an outage, analyzing what went wrong and improving processes helps avoid similar failures in the future.

#refl