3 ms·
This is intriguing, and I'd love to hear more context about the team, code, management, and business/product. I really want it to be true and possible in genera
by dahart 10y ago
This is intriguing, and I'd love to hear more context about the team, code, management, and business/product. I really want it to be true and possible in general...
I'm going to admit what conclusions I jumped to reading this. I'm admitting my bias, and that I might be wrong, not arguing with you or challenging your experience.
My (biased possibly wrong) instinct is to wonder to what degree that was a real world situation. What I mean is that the only times I've had no deadlines and the ability to ruthlessly refactor are the times I've had no managers and no customers. I can see that being easy to pull off in school projects, and on research teams, and in free open source projects, but I have a hard time seeing (and haven't personally witnessed) how that works long term in a healthy functioning business that has revenue where the code is directly related to the product. There are stories of places where this stuff happens, but often you can find people who were there saying the stories are exaggerated or lacking the proper context.
So anyway -- any context you want to share that might make it easier to be ruthless and keep code clean under less ideal conditions than yours? Thoughts about how to do it when there are deadlines, since most people (I speculate) do have deadlines?
- BurningFrog 10y agoThese projects were explicitly set up to be XP/Agile projects, and were staffed with people with that experience and expertise. The way the experts say you can turn your environment around to that, is by explaining and showing the advantages of a deadline free process. Your management will - not unreasonably - suspect you're just trying to work less hard. The way out of that is to build trust by constantly delivering quality software. If this sounds hard, it probably is. I've certainly never done it. The easier way is to join a team that already works this way :) It's also worth noting that constant refactoring towards a good design is a difficult skill that not everyone has! It takes a effort and experience to get good at it. For a group of random programmers, it may not be the best way to work.
- dahart 10y agoThanks! Yes, it's hard to do well even under ideal conditions. That fact is what makes me think that usually my biggest obstacle is probably me, even when I'm certain my deadlines are holding me back, and what in turn causes me to project that onto others who complain about deadlines and management.