3 ms·
> I, personally, prefer simple. Simple systems takes more work up front, but are easier to read, reason about, extend, and maintain. I wish I could make people
by LandR 8y ago
> I, personally, prefer simple. Simple systems takes more work up front, but are easier to read, reason about, extend, and maintain.
I wish I could make people at work realise this.
IT's all about do what is easiest now, rather than put the work in up front to make sure it's easy later.
All our codebases devolve into a tire fire as every change is made in the way that it is easiest at that moment.
I think they assume this is the cheapest way to run, by just kicking the maintainability ball down the road continually. BUt that ends up building up drag on all of our code that eventually makes making even small changes so complicated, slow and error prone.
- austincheney 8y agoIn my mind the best way to make people realize this is to reward refactoring. To the opposite many organizations in my personal experience view it as a waste and a risk. This is often because they are only rewarding enhancement/defect user stories, testing the wrong things (if they are testing at all), and placing too much emphasis on weak diff tools as a substitute for an actual code review. When you are only rewarding user story completion those who complete the most stories (not how) are the most rewarded. If your team contains insecure people it means achievement by code style, otherwise it means to do what is fastest. If you are locked into stories by sprint cycle it means lots of time to stare out the window.