March 2016: Azer Koçulu breaks web deployments worldwide by unpublishing an 11 line module "left-pad" used for string expansion. yarn.cache was invented as a result.
996 karma · joined October 22, 2012
March 2016: Azer Koçulu breaks web deployments worldwide by unpublishing an 11 line module "left-pad" used for string expansion. yarn.cache was invented as a result.
> The Emotion API takes a facial expression in an image as an input, and returns the confidence across a set of emotions for each face in the image, as well as bounding box for the face, using the Face API.
https://twitter.com/sarah_edo/status/928270318229118976
> I used @Azure's Emotion API to make this fun emotion detector pen. Made with Vue, Three.js, emojis and ️
Documentation and infrastructure setup for this project aren't great at the moment, but will get a facelift shortly.
NFL has really creative Engineering and Product teams collaborating to deliver premium digital experiences for the growing online football fan-base. Checkout our growing open-source footprint at https://nfl.github.io/ for a deeper dive into our stack and engineering culture.
NFL is hiring for senior Web, Backend, Connected TV, and Mobile Engineering positions. If GraphQL, Java, Node (Backend/Web), JS/React/Mobx (Web), Swift/Java (Mobile), or C++ (CTV) are your things, then send us an email at [engineers @ nfl.com] with your resume and area of interest (CTV, Mobile, Web, Backend).
More to the point of the article, there is also a custom messaging channel, you can create your own interactive experience (the receiver is just a website displayed in a chrome tab). Here's an example of tic-tac-toe: https://github.com/googlecast/Cast-TicTacToe-chrome. You can already develop a custom receiver for an in-store search feature or something more interactive and playful. You can connect to it via the same wifi. I don't understand what additional value nfc provides in this case as you'd still need to maintain an open/persistent connection to the receiver from the sender, would nfc be able to provide that?
Department-channels (#backend, #web, #ios) can get pretty chaotic with multiple threads getting discussed concurrently. I can see how a topic-channel (#android-release-process) would help you swarm more efficiently. But, making it private and inviting only those you think should be there seems counter to the goal of transparency and "swarming". Maybe you could originate these topic-channels from a general channel with "@group, we're swarming on #android-release-process" and make it public.
Technically this is a prolly fill, but that is a great name!
1 BTC is 22,810.00 RUB (1)
1 BTC is $330.80 (2)
$330.80 is 22,982.67 RUB (3)
Arbitrage of 172.67 RUB
3. https://www.google.com/webhp?sourceid=chrome-instant&ion=1&e...