Today I'm thinking about how as soon as there is more than one person involved in writing code for a project, the codebase is automatically doomed to a slow slide into chaos, with a backlog of tickets for refactors that will never be completed.
How can I embrace this fact and make it work for me rather than fighting against it all the time? 🤔
@pixelpaperyarn Make refactor days/fests. Such as saying "Friday is cleanup day!"
@pixelpaperyarn Or embrace the red/green/purple (write breaking tests/fix tests/clean up) cycle.
@dmoonfire The joys of consulting mean that features inevitably get prioritized over refactoring. 😭
On my project we've made a whole committee to assess and prioritize tech debt. We have refactoring written into the contract so it does at least get attention.
And that's the best solution I've ever seen to the problem, despite features still being the driving force.
@pixelpaperyarn Yeah, I've suffered with the "value added" obsession. I get in a lot of fights with my management because I want a 20% maintenance to clean up code but the "you know, we were going to clean this up so we just didn't waste 100 hours on this" keeps being repeated, time and time again.
In my personal code, I embrace the refactor/cleanup as just a normal part of working.
@dmoonfire We have that mythical 20% time! It is not enough! It will never be enough! 😂
I think I just haven't had a chance to work on any personal code in a while and get that satisfaction of having pristine code.
A bunch of technomancers in the fediverse. Keep it fairly clean please. This arcology is for all who wash up upon it's digital shore.