Skip to Content

Changes for page General Insights

Last modified by chrisby on 2024/09/19 10:56
From version 1.30
edited by chrisby
on 2023/12/04 20:53
Change comment: There is no comment for this version
To version 1.31
edited by chrisby
on 2023/12/18 10:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -24,7 +24,7 @@
24 24  
25 25  #### Miscellaneous
26 26  
27 -* **The sooner a problem is addressed, the cheaper it is.** For example, it is much cheaper to discover a problem in development than in production, where it could have caused real business damage. Or it is cheaper to refactor newly written code immediately, when you are familiar with it, than later, when you have forgotten it or someone else has to refactor it. So immediate refactoring, extensive testing, code reviews, and a focus on early feedback have become common practices.
27 +* **The sooner a problem is addressed, the cheaper it is.** For example, it is much cheaper to discover a problem in development than in production, where it could have caused real business damage. Or it is cheaper to refactor newly written code immediately, when you are familiar with it, than later, when you have forgotten the technical details and subtleties, or when someone else has to refactor it. This is why immediate refactoring, extensive testing, code reviews, and a focus on early feedback have become common practices.
28 28  * **Early Feedback Through Early Implementation.** Tasks like analysis, design, and specification don't provide feedback and therefore no correction mechanism. Without this, a lot of effort can be wasted on concepts that do not work. The first technical feedback comes during implementation. The first user feedback may come after implementation. This is why people use agile and work in iterations to start implementation as early as possible, get feedback as early as possible, and ultimately waste less resources.
29 29  * **Many small steps are cheaper than one big step.** It's more cost-effective to tackle a problem iteratively in small, simple, and safe steps than to tackle its full complexity all at once. That is why practices such as small-step refactoring, test-driven development, and continuous integration have prevailed.
30 30  * **Individual productivity is higher in a team than when working alone.** A collaborative environment encourages knowledge sharing, professional growth, constructive challenge of individual views, mutual support and feedback. In addition, or if you have no one to talk to about technical issues, I highly recommend discussing problems and code with [ChatGPT 4+](https://chat.openai.com/) .