It's interesting to see how their expectations appear to have lined up well eleven years later.
1,246 karma · joined December 22, 2014
It's interesting to see how their expectations appear to have lined up well eleven years later.
I can get a bit defensive about this sort of thing, but that's not an excuse for implying that you were being "cavalier". I apologize for doing so. You seem to be thinking carefully about what you want to do and how to go about doing it.
I sincerely appreciate that you are approaching your work and your words with thoughtfulness. Good luck with your project.
This would likely fall under normal contract negotiation due diligence. You don't accept a contract to use a piece of software that you aren't legally allowed to use on that contract. Violating that would be ABC Inc.'s problem (though it would obviously affect the contractee). Thus, the status of your various software licenses needs to be tracked.
I worked with a vendor that had issues like this. They would need to "firewall off" not only data but also employees who were working on or with data or software that could not legally be used on another contract. This extended to seating assignments in their cubicle farm, where some people could not sit near other people who were working on conflicting contracts. The onus of staying legally compliant was taken very seriously.
1) The majority of the DoD struggles to get permission to use open source software. There are plenty of developers, DBAs, and IT technicians who would love to use some piece of software that they are not allowed to use specifically because it is open source. I once spent 11 months trying to get approval to use a single Google-produced library. I was unsuccessful.
2) Related to the above, agencies responsible for approving software for use are very concerned with licensing issues. After all, they are used to negotiating licensing terms for multi-million dollar contracts. The fact that OSS essentially guarantees that you have no one to call [2] when you have an issue (for the entire lifespan of the project) is a large part of why they will not approve OSS. Beyond that, compliance is a real concern. Popular opinion may be of heartless assholes, but these are real people working jobs. I would not be so cavalier in saying "they'll just use it anyway".
3) I am always disappointed, though never surprised, when people assume that the military works solely to execute war. I was specifically contracted to a (large) part of the military that works on exactly the kind of thing that prevents and reduces violence (sorry to be vague). The kind of domain that would probably translate improved computer vision into saving lives (domestic, foreign, combatant, and civilian). That is, if they could get approval.
[1] I have no idea how other countries' militaries operate.
[2] Literally call. On a phone.
Yes, weed and sugar are both addictive, but it is my understanding that the reduction in performance is not due to the addiction itself.
[1] http://neuro.hms.harvard.edu/harvard-mahoney-neuroscience-in...
Did you mean to say not in short supply of doubt? I thought this was something with little certainty. Or are you saying that little certainty translates to little doubt? Honest question.
I'm still curious about using it. The GitHub example [1] works as described, but I can't get a result from the 'he' example. Is it saying no match was found by returning an empty array?
EDIT: Okay, saw your edit. Might be nice to use an example that's not a stopword. ;) Nice work on the library and the blog post.
Running the following doesn't seem to work for me:
var Wade = require('wade');
var search = Wade(['Hey', 'Hello']);
search('he'); // returns [] [1, 1]
Is that supposed to be [0, 1]? If not, how does that correlate to ["Hey", "Hello"]?Thinking about it, the bicycle would only rotate about the center unless it had something to react against, as was pointed out by others.
Conservation of momentum applies when there are "no external forces", which wouldn't be the case here when you apply the brake.
EDIT: Yeah, my apologies. I didn't mean to write "momentum".
EDIT: I'm probably very wrong about the movement.
EDIT: The video: https://youtu.be/n_6p-1J551Y
- 76.87% of subjects accepted a 25% tax rate intended for redistribution.
- 44.80% of subjects accepted a 50% tax rate intended for redistribution.
It's hard to infer much beyond that.
Perhaps they need to test for a larger number or more fine-grained tax levels between 25% and 50% and see if there is indeed a step change (or other sharp decline) in acceptability when it "reverses social order". Or if there is a smooth distribution curve based on tax rate, not relative position.
---
Even if you take the results as intended, that subjects were considering social order and not tax rate, you still have to concede that this could be about "fairness" and not "rank". It shouldn't be surprising that a majority of people dislike redistributing more than is necessary to achieve equality. That helps explain the results with the children. Ages 6-10 is about where they start to understand "fairness" from the perspective of both parties [1].
Additionally, taking the tax perspective into account, "Person B" appears to be subject to a lower tax rate than "Person A" despite ending up with more money, which subjects would likely see as unfair.
[1] https://www.theatlantic.com/science/archive/2015/11/how-fair...
EDIT: I have no idea if LE's impact is of a "rising tide raises all boats" kind or a purely disruptive kind.
That it is a distinction is important to me. Having difficult discussions is made more difficult if we obscure facts or conflate terms.
> more acceptable
I applied no normative judgement.
[1] https://blog.pinboard.in/2017/06/pinboard_acquires_delicious...
The current link is just a poor summary of the data on that page.