Often that’s enough to cause the meeting not to happen.
(We are remote most dayssome have one unstructured morning meeting called “watercooler discussion. Not a standup!!”)
64,765 karma · joined June 19, 2010
Previous lives:
gnu hacker (e.g. co-founder of Cygnus back in '89) Pharma developer (Talima) Distributed solar thermal systems (Terrajoule) MIT AI Lab/PARC/MCC/Rodin consumer tabletop AR (CastAR) Etc...
remove-everything-up-through-last-dash-gumby@brachiate.org
Often that’s enough to cause the meeting not to happen.
(We are remote most dayssome have one unstructured morning meeting called “watercooler discussion. Not a standup!!”)
But in fact no salary range was provided for any job I looked at.
The US military procurement is the opposite of this.
One reason procurement is slow is to avoid fraud.* Ukrainse hasn’t managed to eliminate that. Perhaps there is a balance, when you’re under fire at least.
* in the US, procurement fraud looks quite different (e.g. having anpart for your weapon made in every congressional district, a tactic developed for the B-1)
I wonder how complex the prompt was to write this.
Iphone is novel though, but does a pencil work?
The only reason I even commented was because IP issues are popular and relevant on HN
West coast filmmakng started in the Bay Area (at the time the largest conurbation in the west) but moved south because of the year 'round weather.
But why the west? Because Edison controlled the filmmaking patents and demanded not just royalties but script oversight as well. By moving west, they could ignore the patents because they were simply too hard to enforce from such a long distance.
So ironically, given how things worked out, IP piracy is at the root of Hollywood.
Here’s a very brief example on the dime novel case: https://techlashed.org/panic/cheap-popular-fiction-penny-dre...
But it’s the fat part of the bell curve. There’s loads of even worse crap outside corporate code…and at the right end of the bell curve is deeply thought out and the result of long-term maintenance that tends towards as bulletproof as can be possible in this universe, parts of OSes, networking stacks, clocks, and the like.
It’s only because that stuff is so robust and sufficiently general that the rest of the world’s steaming pile of code works at all.
My point is that the people (the “drivers” of the car company) should bear the responsibility; it should not be absorbed by the company.
There are other liabilities that should still be assigned to companies. I’m not advocating throwing away the idea of limiting liability.