The benefits of having a clean, error free codebase. Earlier today I posted a tweet, here's the results I got back and a bit more context.
So, earlier today I posted this:
Benefits of having a clean, error free codebase are… * more productive to work with. * easier to debug. Please reply with your reasons!— Simon Owen (@s10wen) January 27, 2016
Thanks very much for the replies:
- more productive to work with.
- easier to debug.
- reduces the mental load involved with working out what the code does.
- better for morale.
- easier to transfer developers between projects.
- better for performance
- potentially reusable code
- easier to understand for newcomers/yourself in 6 months' time.
- easier to write new, non-breaking code.
- more confidence (esp. when tested) = quicker to respond to changes in organisational needs.
- it makes conversations sane, as you all have the same reference points.
- easier to get more people involved.
- easier to implement new features.
- shorter training times.
- benefits to developers ~= benefits to users.
- quicker dev time.
- fewer errors introduced.
- faster delivery of new features.
- a happy developer is a productive developer.
- staff retention.
- things businesses can do talks on and increase reach.
- being proud of your code.
- keeping up to date with best practices.
- easier to automate quality testing.
- easier to enforce quality.
Show this to anyone who argues about whether that refactoring effort is worth the investment. pic.twitter.com/vxw5PvDXq0— David Whittaker (@rundavidrun) January 22, 2016
To give it a bit more context, I'm working on a large codebase with lots of legacy code. I'm looking to tidy the code up for all the reasons above. If you think of any more, please let me know and I'll add them in.
Like this post? Hire Me!