this repo has no description
:art:
+3
-3
+3
-3
Programming.md
+3
-3
Programming.md
···
25
25
- Writing program code is a good way of debugging your thinking.
26
26
- Apply small improvements at each iteration. Running the program will make it more resilient and robust as more errors get fixed.
27
27
- Premature optimization is the root of all evil. Abstraction is a form of optimization and shouldn't be done before the space has been properly explored to know what abstractions should be built. Standardization is a form of optimization and shouldn't be proposed until there's a body of evidence to support what's being standardized.
28
-
- [Increased efficiency can sometimes, counterintuitively, lead to worse outcomes](https://sohl-dickstein.github.io/2022/11/06/strong-Goodhart.html).
29
-
- You should be able to "punch through" your abstraction layer and get to the code behind it in cases you need that.
28
+
- [Increased efficiency can sometimes, counterintuitively, lead to worse outcomes](https://sohl-dickstein.github.io/2022/11/06/strong-Goodhart.html).
29
+
- You should be able to "punch through" your abstraction layer and get to the code behind it in cases you need that.
30
30
- Sometimes you have to stop sharpening the saw, and just start cutting.
31
31
- Software which is broken because there is no incentive to ship good software is going to stay broken until the incentives change.
32
32
- **Choose portability over efficiency**.
···
54
54
- Handle the 80% and let the 20% fend for themselves.
55
55
- [[Pareto Principle |80% of the impact comes from 20% of the work]].
56
56
- [Software is never finished, only abandoned](https://stackoverflow.blog/2020/02/20/requirements-volatility-is-the-core-problem-of-software-engineering/).
57
-
- **Treat all the data as an event log**.
57
+
- **Treat all the data as an append only event log**.
58
58
- Use a central log where consumers can subscribe to the relevant events.
59
59
- Having a central place ([the log](https://engineering.linkedin.com/distributed-systems/log-what-every-software-engineer-should-know-about-real-time-datas-unifying)) for continuous events make easy to create a stream of data to process and sets a source of truth.
60
60
- **There is no silver bullet**.