I'll add that many XD people (eXperience Design: people who try to make software easy and pleasant to use, and better meet business goals with that software) take one look at a Bloomberg Terminal and just about have a stroke. For them, it's a coarse tool from another age that must be "fixed".
Many modern UI experts only know how to use user stories. Thus, everything they touch becomes a clone of a Microsoft Wizard.
Experiments Show Potatoes Can Survive In Lunar Solar
I'm not a flat-earther, I'm not a moon hoaxer, but this headline really confused me.
But how do you cite references when the answer literally comes from 5000 documents all strung together?
Have a 5000 line citation. It's not hard, but not a common case.
In theory slippery slopes are a fallacy,
The fallacy is really just a lack of rigor. If you can't show that each step inevitably (or even probably) leads to the next, then it's a fallacy.
But if you can show that each stage along the slope leads to the next, then it's not a fallacy it's modus ponens. (If each step leads to the next with a certain probability, then you can calculate the probability of the final outcome).
If I read the book and use what I learned from it in my (paid) work, maybe even quoting from it, does that constitute a derivative work?
The modern approach is to use the abstraction/filtration/comparison test to figure out which parts are derived (including the quote) and which parts are original. Once the derived parts are determined, the defendant can assert a "fair use" defense if desired, and the courts will decide.
RTFA is alive and well.
Has right to read, doesn't use it. A true American. I salute him.
When given the choice of a good solution but they are at the mercy of some skilled employees, or a shitty solution that will likely lose in the market, but the employees are safely fungible, I've seen multiple companies repeatedly go for the 'fungible employee' strategy.
It's kind of sad because the skilled employees will generally do what the employer wants if the company is clear about what it wants/needs. Problems come up when the engineers don't understand the needs of the employer, not because of rebelliousness. There is no need for a compromise here.
Embedded dominates programming.
Is that really true? I would have thought it was website programming.
The reward of a thing well done is to have done it. -- Emerson