Skip to Content

Changes for page General Insights

Last modified by chrisby on 2024/09/19 10:56
From version 1.49
edited by chrisby
on 2024/09/19 10:54
Change comment: There is no comment for this version
To version 1.50
edited by chrisby
on 2024/09/19 10:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,7 +6,7 @@
6 6   * Minimum principle example: When implementing a feature - which represents a fixed goal - the most time-efficient approach is chosen to get it done.
7 7   * Maximum principle example: The agile team tries to solve as many stories as possible in the time allotted for a fixed length iteration.
8 8  * **Sustainability**: Economic development is too often misinterpreted as short-term decisions, when the real goal is to achieve maximum profitability within a legal and ethical framework that must include long-term considerations. In this way, time spent on maintaining high code quality through rigorous testing and refactoring are well spent investments that pay off in the long run.
9 -* **Opportunity Costs**: Spend your time creating the most business value while considering all alternatives. An example is the decision whether or not to optimize performance. Implementing a new feature usually generates high business value. Tedious performance tuning, on the other hand, is often not necessary when the features are "fast enough". So the better alternative is often to spend time working on new features and only optimize performance when it is really necessary. Also, in many use cases, most popular programming languages are fast enough and good developability is more important than resource-efficient languages. So use languages that provide native execution speed, such as C/C++/Rust, only when absolutely necessary, and prefer languages that m.
9 +* **Opportunity Costs**: Spend your time creating the most business value while considering all alternatives. An example is the decision whether or not to optimize performance. Implementing a new feature usually generates high business value. Tedious performance tuning, on the other hand, is often not necessary when the features are "fast enough". So the better alternative is often to spend time working on new features and only optimize performance when it is really necessary. Also, in many use cases, most popular programming languages are fast enough and good developability is more important than resource-efficient languages. So use languages that provide native execution speed, such as C/C++/Rust, only when absolutely necessary, and prefer languages that make it easy to develop software, such as Go or Java.
10 10  * **Hobby Projects**: The main driver in a hobby project is usually having fun. Overly strict adherence to maximizing business value generation is contrary to the purpose of a hobby, which is to lightheartedly experiment, discover, or try new things. On the other hand, completely ignoring economics, e.g., not refactoring code, not testing, etc., will lead to development problems. The time it takes to make progress on a bad codebase becomes unnecessarily long, which is not a fun experience. This means that you should have fun with a hobby project, but my recommendation is to balance it with economic development so as not to lose the joy over time.
11 11  
12 12  #### Cost Considerations