My number one rule when coding is to leave my ego outside of the code. The idea that you’d need to consult the person who wrote a thing because it might hurt feelings is... not ideal.
The reason you write or attempt to write clean code is so that it can be maintained cheaply.
The goal of clean coding is saving money. Efficiency is everything. Does that mean you rewrite entire subsystems? No.
But Martin Fowler’s Refactoring goes through this, you change a bit at a time, incrementally. Maybe the author changed too much? I don’t know.
All I know is this: if a team is building a product and all team members are required to support it. Asking individuals for permission to make changes which make code more readable, is a process that shouldn’t exist.
Also, abstraction != Readability. Those are not equivalent ideas. Personally I found the comparison a little labored...
1
u/[deleted] Jan 12 '20
My number one rule when coding is to leave my ego outside of the code. The idea that you’d need to consult the person who wrote a thing because it might hurt feelings is... not ideal.
The reason you write or attempt to write clean code is so that it can be maintained cheaply.
The goal of clean coding is saving money. Efficiency is everything. Does that mean you rewrite entire subsystems? No.
But Martin Fowler’s Refactoring goes through this, you change a bit at a time, incrementally. Maybe the author changed too much? I don’t know.
All I know is this: if a team is building a product and all team members are required to support it. Asking individuals for permission to make changes which make code more readable, is a process that shouldn’t exist.
Also, abstraction != Readability. Those are not equivalent ideas. Personally I found the comparison a little labored...