3 ms·
I agree that good code matters but I am not sure if it matters THAT much in some cases. I write average code but always seek to make improvements. I'm always t
by avgDev 8y ago
I agree that good code matters but I am not sure if it matters THAT much in some cases.
I write average code but always seek to make improvements. I'm always trying to improve my knowledge on OOP and learn about different approaches to architecture but at my company I could write garbage code and nobody would care. Recently, I tried to make an update to a legacy software and the code was quite bad, methods that were 15K lines long. Terrible variable names, UI elements named button1, button2 etc. However, nobody cared because it worked, it served it's purpose for the last 12 years, and yes it needs a complete rewrite, but it would probably need that anyway after 12 years as there are some major business changes.
I think every programmer should try to make things and try to improve. However, over-engineering and writing too many unit tests can also be a waste of time.
- mpweiher 8y ago> over-engineering Not sure why you think "great code" = "overengineering". Great code is not overengineered, by definition.