3 ms·

The only tricks I'll buy from fellow developers are competent solutions focused on the problem at hand. Focus and competence. Often it is nought for us to decid

The only tricks I'll buy from fellow developers are competent solutions focused on the problem at hand. Focus and competence. Often it is nought for us to decide the product we work on, simply the approach. Whatever is optimal. I'm not saying what you're saying doesn't happen, it does, but I feel like I've wizened, and when you stick to objective facts, not subjective crap, even at the expense of making your friends unhappy with you, you'll have found a cure. In a good engineering department facts are a sharp sword that can cut through bullshit as if it were butter. Be careful though, that edge doesn't care who wields it, it'll cut down your own bullshit and errors too. Personally I welcome having bad ideas and incorrect knowledge slain from my mind.

taeric 12y 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 12y 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 12y ago
  If there isn't an easy way to find objective facts to cling to you're probably bikeshedding.
  - taeric 12y ago
    I 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.

taeric 12y 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 12y 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 12y ago
If there isn't an easy way to find objective facts to cling to you're probably bikeshedding.
- taeric 12y ago
  I 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.