> What I think should be common in these two cases is the attitude of a professional towards their work. I think everyone would not deny this fact. Engineering

> What I think should be common in these two cases is the attitude of a professional towards their work. I think everyone would not deny this fact. Engineering is more of a discipline. But if you see things practically, this issue of "bad" code may not happen for various number of cases. For example, unclear project requirements, use cases etc., That is where 'context' of what happened helps to better understand the situation. Building bridges are not done agile and it has a learnings from decades or even centuries. Computer Engineering is mostly agile where you push changes based on changing requirements.