The problem with fighting fires, day after day, is that there’s no time for anything else.
Sometimes, you just have to step back and observe.
To think; to plan; to conquer.
That’s not going to happen while you’re fighting fires.
Sometimes, you have to lose the battle to win the war.
They took our data, ran it through their software, and they got the answers that eluded us for so long.
I was told they were a big consulting company, which meant they probably had great, restrictively expensive software that could do the job. That’s why.
But I don’t buy that argument.
Great software needn’t be expensive.
I’ve lived and breathed great open-source, free technologies growing up. Linux; Apache; PHP; MySQL; WordPress; Python; R.
Are any of these free technologies inferior to their paid counterparts? In development (including data science) work, I don’t think so.
So why were they “successful”? Why could they come up with an answer we couldn’t?
My guess: they were a consulting company with less vested interest.
They came up with an answer. But would it have been better than the one we would have come up with if we were in their shoes? I don’t know.
As a consultant I’d have been much more liberal with my analyses. No matter how badly I mess up, the worst that would happen would be that my company would lose a contract. And chances are good I could push the blame to the data that was provided, or having been provided the wrong context, or information that was withheld.
When you’re part of the company, you have far more vested interest. Not just in your job, but your network, both social and professional. Consequences extend far beyond they would if you were an external consultant working on “just another project”. I’d be far more meticulous ensuring everything was covered and analyses properly done.