3 ms·
I think the major caveat here is that there is probably more subjectivity in day to day developer decisions than there is objectivity. And often times seeing t
by taeric 13y ago
I think the major caveat here is that there is probably more subjectivity in day to day developer decisions than there is objectivity. And often times seeing that distinction where it doesn't actually exist is a pain point.
- mpyne 13y ago> And often times seeing that distinction where it doesn't actually exist is a pain point. Indeed, one man's "objective fact" is another man's subjective opinion, especially once you introduce competing demands.
- leorocky 12y ago"Indeed, one man's "objective fact" is another man's subjective opinion" If it's objective, it's objective. It's not subjective. Objective facts can be measured with numbers in units of time, bits and money. If your objective facts don't involve numbers, then yeah they're probably actually subjective.
- leorocky 13y agoIf there isn't an easy way to find objective facts to cling to you're probably bikeshedding.
- taeric 13y agoI offer no objections to that assertion. I just currently feel that more decisions are of the nature than not. I am also in a place where the development team has managed to jump between upwards of four dependency management strategies and as many ways to communicate with the backend in the past few years. To say I am jaded on some of the decisions is an understatement.