Well-documented architecture with all sorts of models/diagrams which can bring you the real picture of construction, documents capturing all assumptions, constraints, code which is well-commented (and most importantly current), coding standards followed rigorously are all myth.
Reverse entropy software#
Mantras for software reverse engineering and re-engineering Working code is always the single source of truth In a product engineering, a great engineer’s attitude towards his manager should be "My way" - means that "Trust me to deliver excellence, or suffer negative consequences of quality, entropy"Īnd remember, this statement comes with great responsibility. In addition, when it comes to software product engineering (for the Endurance), it is always later which needed to be the choice. There are two ways of dealing with those defects - The typical way (Highway) or the “My way”. It takes years for the code to stabilize after running in various environments, data, circumstances, and use-cases. Most defects reported in software are typical of the same nature. However, a fever is never a disease! It is a symptom of some disorder in the body, indicating you with an increased body temperature, trying to protect itself, for which, root cause diagnosis must be done. Taking a classic example of a fever, one would do a self-medication of a paracetamol to get the body temperature back to normal. In my earlier article Design, Endurance and Entropy I have talked about, the importance of retaining/reducing the system entropy. It is not a high way, it is my way! It takes more effort but yields high-quality output and endurance to the software that we build. My way is unique, different and it is non-obvious. Here, I present the ‘My Way’ (every engineers' own way) of engineering that, I have learnt over close to two decades of being in the software industry. It not only about engineering skills but also important to understand and learn the Art of Reverse Engineering and Re-engineering. Software having up-to-date documentation is a myth in the software industry. This water was finding its way and traveling inside the wall, floor and adjacent wall before reaching the window of the floor below! With careful analysis of the behavior of seepage (it took 3 weeks!) by switching of various water lines, drainage lines at different point in time, it was a surprise to see that, it was just because of a tap which is fixed to wall connecting to the wash basin, not having fully threaded towards wall was causing a seepage inside the wall. I had asked them if they would guarantee that the problem will be solved with that.Īfter a clear no from them asked them to give me a week for my own analysis. Not for the quoted cost, but the cause that they have analyzed and the solution proposed. They concluded that we should remove the tiles from walls and floor of the bathroom to figure out the cause. There are standards that about the height at which water lines are placed inside the wall). Neither the plumbing is done as per the standards (e.g. They said, that plumbers changed every 3 months during the project, and the last guy who remained did not know the internals. With the help of engineers from builders, who were part of the construction and a month of analysis did not help figure out the issue. It is true! To take a practical example - In my residential apartment, seepage started on the walls of the floor below mine. Like any other industry, you will not always have an opportunity to start with a clean slate without the burden of legacy, the absence of knowledge/documentation of the current construction. There are various other skill sets required in order to survive in the software industry. When it comes to software engineering, it is not only about engineering.
0 kommentar(er)
