Hacker Newsnew | past | comments | ask | show | jobs | submit | adamveld12's commentslogin

We use it for general search and similar items results on www.liveauctioneers.com


I'm a big fan of Jocko's podcast, there are great episodes that talk about Unit 731 (https://www.youtube.com/watch?v=mizmXTWDf-4) and the Rape of Nanjing (https://www.youtube.com/watch?v=uylTcj5yDOM) that are worth the time if you're interested in learning about the darker side of history.

The Rape of Nanjing episode is particularly interesting since he goes over the book "The Rape of Nanking: The Forgotten Holocaust of World War II" by Iris Chang in the first part, following that up with readings from "The Woman Who Could Not Forget" by, Dr. Ying Ying Chang which goes over how researching the Nanjing Massacre affected her daughter Iris deeply enough to the point of ending her own life.

Usually this is stuff that people avoid, but I feel that knowing what people are capable of doing gives some perspective in my life.


We should never forget.

Any speculative fiction about the horrors of runaway AI or the supernatural or some form of extraterrestrial life pale in comparison to what our species has done to itself over the years.

Any horror you could possibly imagine, some wanker has probably already done it to someone else for real.


Where is that "Show HN" that will let me check if a site is affected by an S3 outtage?


Funny, I just tried making an alexa skill the other day so this is appropriate. How did you get around the restriction on the types of utterances you can do? It seems like with this type of app you would need to use AMAZON.Literal but they took that out for (security?) reasons. I saw that you effectively have placeholder text in your slot definitions, is alexa 'loose' enough with utterances to let you say almost any phrase?


I hope that my post can help you then! It seems as if with the custom slot type, I was able to create my own slot type for each of the things I needed. Then I gave it some sample inputs for that type and I tried making it general but covering different types of inputs (ones with numbers, symbols etc). Here is a link to my IntentSchema.json file to see how I made the intents: https://github.com/acucciniello/alexa-open-doc/blob/master/s.... Here is a link to folder containing the slot type definition files: https://github.com/acucciniello/alexa-open-doc/tree/master/s....


I had quite a memorable experience where a Google recruiter accidentally CC'd their post interview survey email instead of BCC. After the initial "haha" moment we discovered that almost all of the ~2k people in the email list were African American. A private LinkedIn group was started after that, although I haven't followed up with it lately.

Also for that particular interview, I waited for an hour and a half in the lobby before a recruiter finally showed up. It turned out that my recruiter was let go the day before and my interview time fell between the cracks. Pretty much the worst experience I've ever had interviewing.


Where was this workaround mentioned?

edit:

Found a tweet about it: https://twitter.com/GoogleforWork/status/776078668212953090

Seems like people are having some success with it and there isn't data loss.


yeah, but having the option to run 'terraform plan' really helps you know what you're getting yourself into.


We've had Terraform take action that wasn't in the plan, in production.

I call it "pray and apply".

https://news.ycombinator.com/item?id=12214879


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: