We all were quick to point out that they were selling cars with touchscreens. The HCI researchers said yes the company did, but their point still stood.
You want to be able to do things like adjust heat and defrost without looking (just with hands).
1,402 karma · joined August 1, 2011
Email: kevinconroy [at] gmail [dot] com
We all were quick to point out that they were selling cars with touchscreens. The HCI researchers said yes the company did, but their point still stood.
You want to be able to do things like adjust heat and defrost without looking (just with hands).
brew install gource"The current assessment concluded that glyphosate does not have oestrogen, androgen, thyroid and steroidogenesis (EATS)‐mediated endocrine disrupting properties based on the facts that no endocrine‐mediated adverse effects were identified in apical studies; the weak evidence seen in a limited number of supplementary in vitro studies was inconsistent with the findings of the acceptable OECD (Organisation for Economic Co‐operation and Development) tests and it was not expressed in vivo in the OECD Level 4 and 5 studies; and no EATS‐mediated endocrine mode of action was identified. Since the database available to reach this conclusion was quite comprehensive, it was concluded that the data gap identified in the previous EFSA conclusion (EFSA Journal 2015;13(11):4302) was adequately addressed."
Source: https://efsa.onlinelibrary.wiley.com/doi/full/10.2903/j.efsa...
Disclaimer: Not affiliated with Thron, just a fan after having worked with them at AWS re:Invent Nonprofit Hackathon.
If you are interested in making a similar switch, here are some resources:
* https://www.idealist.org/ * Look at career pages for any nonprofit listed here: https://www.ctosforgood.org/
(Disclaimer: I work at GlobalGiving.org, but we're not hiring. I'm just keen to get more talented people in the nonprofit sector! AMA!)
>> "If we want to proactively control outcomes, we would be far more effective if we knew which organizational, program, training, process, tool, and personnel factors actually caused the outcomes we care about. To know this information with any certainty, we must move beyond correlation and regression to the subject of causation. We also want to establish causation without the expense and challenge of conducting controlled experiments, the traditional approach to learning about causation within a domain. Establishing causation with observational data remains a vital need and a key technical challenge."
>> "Armed with this new approach, we are exploring causal factors driving software cost within DoD programs and systems. For example, vendor tools might identify anywhere between 25 and 45 inputs that are used to estimate software development. We believe that the great majority of these factors are not causal and thus distract program managers from identifying factors that should be controlled."
Since down, didn't read: Don't assume you know the answer. The point of the research is to prove what's actually a causal driver of costs, not just an unrelated correlation winking suggestively at it.
It's also great for ad-hoc usability testing to see how people are using your features, where they slow down to read, what elements they try to click on but can't, and other UX improvements that you'd pay consultants six figures to put in a report for you.
Still, you're right that many companies have a surprising lack of security. This vector of unintentional exfiltration may pale in comparison to the intentional mismanagement and lack of security focus internally. Equifax, anyone?
As someone who has integrated FullStory into a production site, I spent several days doing a careful audit of our forms and redacting fields from being tracked. FullStory has an excellent, universal account setting to automatically redact fields based on any CSS selector, so it's very, very easy to tell it to remove any sensitive information - or even all form fields! - if that's what the website publisher desires. Out of the box I found that it correctly blocked credit card fields and passwords correctly, and we were able to add additional fields that are sensitive.
Again, rightly so that a website publisher may want more information than you desire, but they could also store your info in plaintext in the database, making it easy for hackers to exfiltrate as well. Yes, this is another vector, but hardly the easiest one.
I'd suggest searching (non-profit + meaningful for-profit).
I used to say "Nonprofits? They aren't doing anything interesting with tech!!"
One day, my wife convinced me to try searching on Idealist just to see if there were any nonprofits doing anything interested with tech. I feel in love with the very first result, got the job, worked my way up the ranks, and am now Chief Product Officer at GlobalGiving.org and I couldn't be happier.
Looking for a shortlist of orgs that I'd recommend? Try any one of the orgs at https://www.ctosforgood.org
I'm fairly angry that someone would read that article and assume that if Boy Scouts decided to admit girls to help offset the decreasing memberships in Boy Scouts (noted in the article), that somehow that means Girl Scouts is to blame.
SERIOUSLY? This is exactly the kind of sexism that girls have to deal with day in and day out.
As someone who was a Boy Scout growing up, and now as a Girl Scout leader and Cub Scout leader, I find the Girl Scouts to be a much better run organization that provides a range of helpful, useful skills.
I'm in favor of letting girls and boys participate in these activities and having equal access to whichever experience is best for them. So far, the Girl Scouts have done an amazing job at making me feel welcome as an adult male leader and giving me the tools that I need to support the girls in my troop. They know what they are doing, they know how to create girl-oriented programming, and they are training the next generation of female leaders.
My rage as the apparent sexism aside, I also think that an individual scout's experience (girl or boy) will depend heavily on the adult leadership in their location (both district, troop/pack, and den/group). It's truly a YMMV situation.
I'm CPO/CTO/CMO at GlobalGiving. I know there are other members of CTOs for Good lurking here (https://www.ctosforgood.org/), but I'll let them call themselves out.
https://aws.amazon.com/compliance/data-privacy-faq/
The reason AWS is successful is because Amazon takes privacy and security seriously. Why does Netflix trust AWS when there's Prime Video? Because Netflix knows that they have legal recourse against Amazon if they tried to do anything underhanded. I suspect Amazon would quickly fire anyone who breached customer data.
(Seriously, though, you'll need to square the power source as you double the distance.)
Helpful links: https://github.com/swagger-api/swagger-spec/blob/master/vers...
Powerful array of tools to enable wrappers for Go, Scala, Flash, Java, Objc, PHP, Python, Python3, Ruby, Node, and more. https://github.com/swagger-api/swagger-codegen
The back and forth reading that you have to do results in errors because you lose your place, skip a step, add an ingredient in the wrong order, etc. That really impacts the results. In this vein, I've been working on a format that lets you just go top to bottom with much better results. Would love to hear your thoughts.
First, you could send an email to existing customers telling them that you are raising prices but that you are grandfathering them in and their rate won't change. Danger here is that you then go on record and may never want/be able to raise prices without losing them. YMMV.
Second, change their monthly invoices to show that they WOULD be charged a higher rate if they weren't grandfathered in. Loyalty discount. If you don't want to show a discount on the invoice, just rename their pricing tier to "Loyal Customer - Pro Edition" (or whatever). This lets you do it stealth and leaves options open for price changes in the future.
A tl:dr; Earthquakes and rain.
A: If you bury drums of radioactive material you want to make sure that they stay sealed. However, on a 10,000 year time span, you cannot assume much. A very strong drum right now could be very weak in 5,000 years. Or, with one strong earthquake 2,000 years from now, it could crush the drums you've buried deep in the desert. As rainfall seems from the surface and into the water table, it will pull the radioactive material with it, then making the water supply unsafe.
Yucca Mountain was a popular site for a long time because it's a deep salt mine. Salt mines are interesting because it means that it's been impossible for water to flow thru them for millennia, which is the time scale you're concerned about here. From an engineering stand point, Yucca Mountain was just about the perfect solution, but it got killed politically because being 100 miles away from Las Vegas was "too close" for elected officials to stomach.
http://en.wikipedia.org/wiki/Yucca_Mountain_nuclear_waste_re...
Although the design questions are fascinating, the bigger issue that we need somewhere to store all of the nuclear waste. It's actually sitting in a variety of temporary facilities right now that aren't as safe as WIPP or Yucca mountain simply because it's very hard to get politicians to agree whose backyard gets to be the forever home for our spent fuel rods.
Source: My father has spent the last 20 years of his career with the Department of Transportation and Department of Energy working with transportation of hazardous and nuclear waste and took trips out to Yucca Mountain and WIPP.
http://www.globalgiving.org/projects/help-stop-the-ebola-epi...