|
|
|
|
|
by pydry
1915 days ago
|
|
shrug I think every time I've ever seen a disagreement about code quality it's boiled down to both developers thinking "I know it when I see it" about their separate approach. If a set of principles lets them both think they're both correct and the other one is wrong, what exactly is the point of those principles? This isn't just a coding thing. It's also, say, why society follows a body of laws rather than something like the 10 commandments. |
|
That's why, if I am on a team project, I much prefer working in opinionated frameworks with strong idioms. It actually doesn't matter if I think I could do it better, the framework has chosen a different way and that is fine. We all have to do it that way, and we can all compromise and collaborate. No one bickers about best, and we can get real work done.
Different when it is a project of my own, but if it requires teamwork you need a framework of collaboration as much as a framework of code.