I think Rails developers, as a community, spend too much time on "What is the right way to do this" questions when they could spend 40% of the time on "Does thi

I think Rails developers, as a community, spend too much time on "What is the right way to do this" questions when they could spend 40% of the time on "Does this way make sense?" and 60% on implementing more features for paying customers. I do not self-identify as a Rails Programmer, so I can't speak for what they do and why. But I will say that taking the time to decide on the "right" way to do X is a win if X ever comes up again. That is very nearly the definition of "right" as opposed to "convenient" or "pragmatic:" What way makes sense now and in the future, what way is a general pattern we can apply when the same situation and forces arise? We often think that this won't come up in this app again, so why invest the extra energy? But in a blogging environment, when you share and discuss your idea of the right way with others, the community benefits from your work. Likewise, you benefit from others taking the time to navel-gaze over the right way to do stuff you haven't encountered yet. Summary of my suggestion: Investing extra energy in thinking about the "right" way to do things is beneficial in a broadly collaborative and highly communicative environment like the blogosphere.