Skip to Content

Changes for page General Insights

Last modified by chrisby on 2024/09/19 10:56
From version 1.11
edited by chrisby
on 2023/10/14 16:02
Change comment: There is no comment for this version
To version 1.9
edited by chrisby
on 2023/10/14 15:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -General Insights
1 +Personal Insights
Content
... ... @@ -1,6 +1,6 @@
1 1  While reading the software engineering literature, I noticed that there are a few high-level principles that run through many technical topics and are the driving force behind many developed best practices, workflows, and models. Since I found them useful, I would like to summarize them here in a short and clear form.
2 2  
3 -* **The ultimate goal of any software engineering effort is resource minimization.** In a business context, resources primarily mean money/costs. That is, whether the topic is clean code, testing, architecture, agile, or even personal behavior as a professional, the goal is always to make everything related to software as cheap as possible. The goal is economic, the means to achieve it are technical. This means that the software engineer must think about the resources used for every technical decision, including typical business considerations such as cost-benefit and risk estimates. This is a valid expectation for business to have of software developers.
3 +* **The ultimate goal of any software engineering effort is resource minimization.** In a business context, resources primarily mean money/costs. That is, whether the topic is clean code, testing, architecture, agile, or even personal behavior as a professional, the goal is always to make everything related to software as cheap as possible. The goal is economic, the means to achieve it are technical. This means that the software engineer must think about the resources used for every technical decision, including typical business considerations such as cost-benefit and risk estimates. This thinking is a valid business expectation for software developers.
4 4  * **Cost Considerations**
5 5   * **Most costs are caused by maintenance, not development.** Quick and dirty development never pays off, neither short term and even less in the long-term.
6 6   * **Hardware is cheap.** When software is deployed on a single server, hardware costs can usually be neglected. However, the importance of hardware costs may increase when the same software is deployed on a large number of servers.