3 ms·
Oddly, I would sum up both of those as bikeshedding problems. I agree it is a team issue. I know the world is sick of gardening metaphors, but I do feel like
by taeric 8y ago
Oddly, I would sum up both of those as bikeshedding problems. I agree it is a team issue.
I know the world is sick of gardening metaphors, but I do feel like there are lessons from community gardens. (Really any community thing.) You will usually have an owner that will paint broad strokes of what the rules are. Then, a bunch of spots that contributors are touching regularly. In their contributions, the rules are much more free form. But, you don't typically have people moving rapidly between contribution zones.
Which gets me to my favorite take on the answer. Solving the customer problem is not necessarily the same as solving any developer problem. If you are lucky, you can align them. However, as a developer brutal honest with self in "did this change actually provide any value to the customer" has to be constantly asked.