Post by rubina9898 on Dec 24, 2023 9:30:56 GMT 1
Short tactical programming has been defined as solving problems quickly at the expense of the quality of the designed solution. When describing the tactical approach the author also presented the phenomenon of tactical tornado i.e. a programmer characterized by an incredibly fast pace of solution delivery working entirely in a tactical approach. While reading this description I had the reflection that sometimes I fit this description myself which I am not entirely satisfied with. I had several such reflective moments throughout the book. In opposition to tactical programming a strategic approach was presented.
An approach that takes into account the quality of the delivered software and takes into account its long term development and maintenance is promoted here. This is the approach preferred and recommended Phone Number List by the author as evidenced by the name of one of the chapters Design it Twice. In the next few chapters John Ousterhout presents ways to simplify your software architecture. The author focuses on code modularization separation of layers and the correct definition of abstraction in the code . The chapters on modularization discuss what the module interface should look like and how to divide responsibilities into modules. In this part I experienced a second reflection.
The phenomenon of pass through methods caught my attention . This is a phenomenon where subsequent layers of abstraction do not bring any added value and the only task of such methods is to call another method. I would definitely find several such methods in my code. The last issue described by the author related to software complexity is correct error handling. The author shows how incorrect error handling can lead to an increase in system complexity. What apart from complexity The second part of the book covers other no less important issues related to design and software development. This part of the book focuses a lot on code comments.
An approach that takes into account the quality of the delivered software and takes into account its long term development and maintenance is promoted here. This is the approach preferred and recommended Phone Number List by the author as evidenced by the name of one of the chapters Design it Twice. In the next few chapters John Ousterhout presents ways to simplify your software architecture. The author focuses on code modularization separation of layers and the correct definition of abstraction in the code . The chapters on modularization discuss what the module interface should look like and how to divide responsibilities into modules. In this part I experienced a second reflection.
The phenomenon of pass through methods caught my attention . This is a phenomenon where subsequent layers of abstraction do not bring any added value and the only task of such methods is to call another method. I would definitely find several such methods in my code. The last issue described by the author related to software complexity is correct error handling. The author shows how incorrect error handling can lead to an increase in system complexity. What apart from complexity The second part of the book covers other no less important issues related to design and software development. This part of the book focuses a lot on code comments.