# 2017 Published articles for 2017. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Great Python Refactor of 2017 And Also 2018 DevFeed: [The Great Python Refactor of 2017 And Also 2018]() Original publisher: [Read original article]() Author: Khan Academy Published: 2018-03-19T22:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Python](), [Refactoring](), [Code](), [Development](), [Tool]() Tags: [2017](), [blog-post](), [code](), [dev](), [engineering](), [infrastructure](), [news](), [python](), [refactor](), [refactoring]() ### AI overview This first article in a series describes Khan Academy's 2017-2018 Python refactoring effort. It explains how an overloaded codebase structure developed, the changes made to organize files and directories, and the difficulties of the work. ### Source excerpt By Craig Silverstein Our codebase was a mess. One day, we decided to do something about it: namely, ... Read more ## Cloud provider postmortems: volume vs depth DevFeed: [Cloud provider postmortems: volume vs depth]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-08-05T00:00:00Z Content type: opinion Language: en Sources: [Sridhar Rajarao]() Topics: [Cloud](), [incident](), [SRE](), [site-reliability-engineering](), [engineering-culture]() Tags: [2017](), [2025](), [2026](), [aws](), [azure](), [cloud](), [dynamodb](), [engineering-culture](), [gcp](), [incident](), [incident-management](), [postmortems](), [s3](), [sre](), [transparency](), [writeup]() ### AI overview The article compares public postmortem practices among Google Cloud, Azure, and AWS. It argues that Google Cloud emphasizes high volume and speed, Azure emphasizes detailed transparency and customer accountability, and AWS publishes fewer writeups with greater depth and industry influence. ### Source excerpt GCP publishes 100+ postmortems a year. AWS publishes almost none. Azure has become the transparency leader. What each posture reveals about engineering culture, and what SREs should steal from all three. ## Security Week 2619: особенности уязвимости Copy Fail в ядре Linux DevFeed: [Security Week 2619: особенности уязвимости Copy Fail в ядре Linux]() Original publisher: [Read original article]() Author: Kaspersky\_Lab ("Лаборатория Касперского") Published: 2026-05-04T18:24:46Z Content type: news Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [Linux](), [Security](), [Docker](), [Kubernetes](), [Python](), [Shell](), [mount](), [passwd]() Tags: [2017](), [2026](), [copy-fail](), [cve](), [docker](), [kubernetes](), [linux](), [mount](), [passwd](), [python](), [security](), [tag-9fe8963de219]() ### AI overview This article examines Copy Fail, a Linux kernel vulnerability identified as CVE-2026-31431 with a CVSS score of 7.8. The flaw in the algif_aead module can allow a local attacker to modify the cache of readable files and potentially gain superuser privileges. The article discusses risks to container environments, detection indicators, and mitigations including kernel updates or blocking the module. ### Source excerpt Важной новостью прошлой недели стало обнародование данных об опасной уязвимости в ядре Linux, получившей название Copy Fail (мини-сайт, новость на Хабре), которая открывает относительно простой способ локального повышения привилегий. Авторы оригинального исследования не стесняются рекламировать ИИ-ассистент для анализа кодовой базы, который нашел данную проблему в течение часа. Исследователи "Лаборатории Касперского" провели анализ уязвимости и предложили варианты обнаружения атак с ее использованием. Уязвимость получила идентификатор CVE-2026-31431 и рейтинг 7,8 балла по шкале CVSS. Ошибка была внесена в код модуля ядра algif_aead еще в 2017 году: тогда была внедрена поддержка оптимизаций in-place при работе системы шифрования AEAD. Это, в свою очередь, привело к дефекту обработки буферов, что дало потенциальному атакующему возможность контролируемо изменять содержимое кэша любого файла, доступного для чтения. Читать далее ## Chicory: A JVM-Native WebAssembly Runtime for Java Libraries DevFeed: [Chicory: A JVM-Native WebAssembly Runtime for Java Libraries]() Original publisher: [Read original article]() Author: Andrea Peruffo Published: 2025-12-23T03:03:36Z Content type: article Language: en Sources: [Java Advent Calendar]() Topics: [WebAssembly](), [Java]() Tags: [2017](), [java](), [java-libraries](), [jvm](), [native](), [webassembly]() ### AI overview This article explains how Chicory brings WebAssembly execution to Java applications through a JVM-native runtime with zero native dependencies or JNI. It describes portability, JVM sandbox integration, and execution modes, and discusses Chicory's use in Java libraries. ### Source excerpt Introduction: the promise of "embed once, run anywhere" reimagined What if you could embed native-level capabilities into your Java applications, think of database engines, scripting runtimes, policy interpreters, even compilers and still remain pure Java, with no JNI, no native binaries, no concerns about OS or architecture compatibility? That is the promise of combining [...] The post Bring WebAssembly to the JVM. How Chicory Is Powering a New Generation of Java Libraries appeared first on JVM Advent. ## How to really measure LLMs for JVM Code? A Benchmarking guide for late 2025 DevFeed: [How to really measure LLMs for JVM Code? A Benchmarking guide for late 2025]() Original publisher: [Read original article]() Author: Artur Skowronski Published: 2025-12-21T04:04:59Z Content type: tutorial Language: en Sources: [Java Advent Calendar]() Topics: [LLM evaluation / benchmarking](), [Large Language Model](), [coding](), [Java](), [Scala]() Tags: [2017](), [benchmark](), [benchmarking](), [benchmarks](), [coding](), [java](), [kotlin](), [llms](), [scala]() ### AI overview This guide explains how to evaluate large language models for coding, focusing on benchmarks relevant to JVM languages such as Java, Kotlin, and Scala. It describes the shift from testing isolated code generation to assessing software-engineering tasks, including HumanEval, MBPP, and SWE-bench. ### Source excerpt If you're reading this, you're probably already using some LLM for coding. Maybe it's Copilot, maybe Claude Code, maybe Cursor with Gemini enabled (or Cursor's own model). You know the drill. Do you truly expect the announcement "We are worst than competitors?" The problem is that when someone asks, "Which model is best for Java?", [...] The post How to really measure LLMs for JVM Code? A Benchmarking guide for late 2025 appeared first on JVM Advent. ## Beyond x86: Java on ARM in 2025 DevFeed: [Beyond x86: Java on ARM in 2025]() Original publisher: [Read original article]() Author: Artur Skowronski Published: 2025-12-05T02:02:36Z Content type: article Language: en Sources: [Java Advent Calendar]() Topics: [Arm](), [Java](), [x86](), [Cloud]() Tags: [2017](), [2025](), [architecture](), [arm](), [backend](), [cloud](), [java](), [processors](), [x86]() ### AI overview The article examines why Java on ARM is becoming more relevant for backend and server workloads in 2025. It discusses ARM's historical association with mobile and embedded devices, Apple's transition to ARM-based Macs, and the development of the Neoverse architecture for data centers, while noting the JVM ecosystem's gradual adaptation. ### Source excerpt We all know the mantra: "Write Once, Run Anywhere." But for most of Java's history, that "Anywhere" really meant "anywhere, as long as there's Intel or AMD underneath." When most of us were starting out with Java, ARM was something you associated with phones, a Raspberry Pi, or some mysterious "embedded" device - not with [...] The post Beyond x86: Java on ARM in 2025 appeared first on JVM Advent. ## On being a Freelance Full-Stack Developer DevFeed: [On being a Freelance Full-Stack Developer]() Original publisher: [Read original article]() Author: Robin Wieruch Published: 2024-11-20T11:50:46Z Content type: opinion Language: en Sources: [Robin Wieruch]() Topics: [web applications](), [Web Development](), [React](), [Node.js](), [React Native](), [JavaScript](), [Next.js]() Tags: [2017](), [apis](), [career](), [freelance](), [freelance-full-stack-developer](), [javascript](), [junior-developer](), [next-js](), [node-js](), [personal-experience](), [react](), [remote](), [side-projects](), [skills](), [team](), [web-applications]() ### AI overview A freelance full-stack developer reflects on working with companies to build and maintain web applications and APIs. The article describes the prior experience, collaboration, side projects, and technical skills the author considers important before starting freelance work. ### Source excerpt ... ## CSS and TailwindCSS Approaches to Styling Websites in 2024 DevFeed: [CSS and TailwindCSS Approaches to Styling Websites in 2024]() Original publisher: [Read original article]() Author: Mads Brodt Published: 2023-12-27T16:00:42Z Content type: opinion Language: en Sources: [Front-End Focus]() Topics: [CSS](), [Front end](), [Tailwind CSS](), [Web Development](), [Sass](), [Less](), [browsers](), [Design system]() Tags: [2017](), [browsers](), [css](), [design-system](), [flexbox](), [front-end](), [less](), [sass](), [tailwind]() ### AI overview This opinion article examines approaches to styling websites in 2024. It argues that vanilla CSS has become more capable through features such as custom properties, CSS Grid, and CSS nesting, while TailwindCSS remains popular for reducing style conflicts and discouraging arbitrary values. The article also emphasizes that TailwindCSS still requires knowledge of underlying CSS concepts such as Flexbox, Grid, and the box model. ### Source excerpt Hi again! ## MindOrks and AfterAcademy Announce Their Closure DevFeed: [MindOrks and AfterAcademy Announce Their Closure]() Original publisher: [Read original article]() Author: Janishar Ali Published: 2022-12-11T06:07:56Z Content type: news Language: en Sources: [Mindorks - Medium]() Topics: [Development](), [coding](), [android-development]() Tags: [2017](), [coding](), [community](), [developers](), [development](), [updates]() ### AI overview MindOrks announces that it is closing MindOrks and AfterAcademy. The founders say they have tried to preserve the platforms' learning resources and will keep paid services available for as long as needed. ### Source excerpt Dear Readers and Writers, Janishar Ali and Amit Shekhar started MindOrks in 2017 to share their love of coding with the community. It evolved from an Android development learning platform to a full-fledged company serving 3 million developers worldwide. Our learning resources helped students and developers get better at work. The love we received as part of the journey is overwhelming. Life moves on and so do we. Today we announce the closing of the MindOrks and AfterAcademy. We have tried to preserve the learning resources that benefitted the community. You can find the learning resources now at these places: https://janisharali.com https://amitshekhar.me https://www.youtube.com/@janisharali https://www.youtube.com/@amitshekhar https://blog.mindorks.com https://afteracademy.com The paid services will be available for the time it is needed. Please follow our founders for more updates: Janishar Ali: https://twitter.com/janisharali Amit Shekhar: https://twitter.com/amitiitbhu Thank You Saying Good Bye! was originally published in MindOrks on Medium, where people are continuing the conversation by highlighting and responding to this story. ## Record/Replay testing in Sorbet DevFeed: [Record/Replay testing in Sorbet]() Original publisher: [Read original article]() Author: Nelson Elhage Published: 2020-01-13T18:00:00Z Content type: article Language: en Sources: [Nelson Elhage]() Topics: [Testing](), [Ruby](), [stripe](), [Development](), [Open Source]() Tags: [2017](), [case-study](), [debugging](), [git](), [infrastructure](), [open-source](), [quality](), [ruby](), [stripe](), [testing](), [unit-test]() ### AI overview This article describes Sorbet's record/replay testing strategy. The framework records a typechecker's output for example Ruby programs, stores that output in Git, and replays the examples to compare later results. ### Source excerpt In 2017 and 2018, I (along with Paul Tarjan and Dmitry Petrashko) was a founding member of the Sorbet project at Stripe to build a gradual static typechecking system for Ruby, with the aim of enhancing productivity on Stripe's millions of lines of Ruby, and eventually producing a useful open-source tool. I'm very proud of the work we did (and that others continue to do!) on Sorbet; I think we were very successful, and it was one of the best teams I've worked on in a number of ways. ## Inside ReactOS Deutschland e.V. - Annual Report 2018 DevFeed: [Inside ReactOS Deutschland e.V. - Annual Report 2018]() Original publisher: [Read original article]() Published: 2019-06-23T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Development](), [Operating system](), [USB](), [Google]() Tags: [2017](), [free](), [google-summer-of-code](), [open-source](), [organization](), [os](), [project](), [react](), [reactos](), [report](), [transparency](), [usb](), [win32](), [winapi]() ### AI overview ReactOS Deutschland e.V. published its 2018 annual report on the main ReactOS website. The report covers the association's activities, outlook, finances, support for the ReactOS Project, the ReactOS Hackfest, Google Summer of Code participation, events, releases, donations, scholarships, and USB stack contract work. ### Source excerpt The Annual Report 2018 of ReactOS Deutschland e.V., the non-profit organization supporting the ReactOS Project, has just been finished. In the past, these reports have exclusively been published on the ReactOS Deutschland e.V. subsite, but only got little attention there. Hence, the latest report is now released on the main ReactOS website. In our quest for transparency, we hope that the report offers an insight into the foundation's activities in 2018 and the plans for 2019. ## Modern C++ for C Programmers: introduction DevFeed: [Modern C++ for C Programmers: introduction]() Original publisher: [Read original article]() Published: 2018-07-28T11:29:55Z Content type: article Language: en Sources: [Bert Hubert's writings]() Topics: [C++](), [C](), [Programming](), [Programming language](), [Go Language](), [Rust]() Tags: [2017](), [c](), [c-c-plus-plus](), [c-plus-plus](), [go](), [introduction](), [modern](), [programming](), [rust](), [swift]() ### AI overview This introductory article argues that modern C++ can offer C programmers useful capabilities without requiring them to learn the entire language. It presents C++ as powerful and expressive but complex, and outlines a series focused on a selected subset of practical C++ features, primarily targeting C++14 with occasional C++17 features. ### Source excerpt 2018 is an exciting time to be a programmer, with so many good "full service" programming languages to choose from: C, C++ 2017, Go, Python, Rust and who knows Swift too. Programming languages are complicated beasts - even the simplest languages have specifications that run (or would run) in the hundreds of pages, and once you include everything, no serious language is likely to clock in under a thousand. With this comes the fact that every programming language has good parts, and frequently even more bad parts. ## Success at Apache: Migrating Yahoo Jobs from Apache MapReduce to Apache Tez DevFeed: [Success at Apache: Migrating Yahoo Jobs from Apache MapReduce to Apache Tez]() Original publisher: [Read original article]() Author: mikesefanov Published: 2018-02-05T14:43:07Z Content type: article Language: en Sources: [Yahoo]() Topics: [Hadoop](), [Open Source](), [data](), [Apache Spark]() Tags: [2017](), [apache](), [blog](), [bug](), [data](), [distributed](), [hadoop](), [hdfs](), [oath](), [open-source](), [spark](), [tez](), [yahoo](), [yahoo-engineering]() ### AI overview Kuhu Shukla describes her experience contributing to Apache projects at Yahoo and migrating Yahoo jobs from Apache MapReduce to Apache Tez. The article also discusses Oath's Apache-based grid infrastructure and her early work with YARN, HDFS, and Hadoop. ### Source excerpt yahoodevelopers: Kuhu Shukla (bottom center) and team at the 2017 DataWorks Summit By Kuhu Shukla This post first appeared here on the Apache Software Foundation blog as part of ASF's "Success at Apache" monthly blog series. As I sit at my desk on a rather frosty morning with my coffee, looking up new JIRAs from the previous day in the Apache Tez project, I feel rather pleased. The latest community release vote is complete, the bug fixes that we so badly needed are in and the new release that we tested out internally on our many thousand strong cluster is looking good. Today I am looking at a new stack trace from a different Apache project process and it is hard to miss how much of the exceptional code I get to look at every day comes from people all around the globe. A contributor leaves a JIRA comment before he goes on to pick up his kid from soccer practice while someone else wakes up to find that her effort on a bug fix for the past two months has finally come to fruition through a binding +1. Yahoo - which joined AOL, HuffPost, Tumblr, Engadget, and many more brands to form the Verizon subsidiary Oath last year - has been at the frontier of open source adoption and contribution since before I was in high school. So while I have no historical trajectories to share, I do have a story on how I found myself in an epic journey of migrating all of Yahoo jobs from Apache MapReduce to Apache Tez, a then-new DAG based execution engine. Oath grid infrastructure is through and through driven by Apache technologies be it storage through HDFS, resource management through YARN, job execution frameworks with Tez and user interface engines such as Hive, Hue, Pig, Sqoop, Spark, Storm. Our grid solution is specifically tailored to Oath's business-critical data pipeline needs using the polymorphic technologies hosted, developed and maintained by the Apache community. On the third day of my job at Yahoo in 2015, I received a YouTube link on An Introduction to Apache Tez. I watched ## IP Spoofing at Packet Hacking Village DevFeed: [IP Spoofing at Packet Hacking Village]() Original publisher: [Read original article]() Author: Marek Published: 2018-01-25T23:00:00Z Content type: article Language: en Sources: [Marek Majkowski]() Topics: [spoofing](), [Hacking]() Tags: [2017](), [hacking](), [ip](), [spoofing](), [talk]() ### AI overview A brief account of giving a talk about IP spoofing at the Packet Hacking Village in July 2017. ### Source excerpt IP Spoofing at Packet Hacking Village 26 January 2018 Back in July 2017 I went to Vegas and gave a short talk at the Packet Hacking Village. I was talking about my favorite subject - IP Spoofing. ## 2017: The year in GraphQL DevFeed: [2017: The year in GraphQL]() Original publisher: [Read original article]() Author: Sashko Stubailo Published: 2018-01-03T22:12:00Z Content type: opinion Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [API](), [Open Source](), [Microservices]() Tags: [2017](), [api](), [apis](), [apollo](), [clojure](), [collaboration](), [community](), [graphql](), [ibm](), [microservices](), [open-source](), [releases]() ### AI overview An Apollo team retrospective describes GraphQL's growth in 2017, including adoption by established companies, use in production, specification changes, conferences, and open-source releases. ### Source excerpt GraphQL was announced and initially open-sourced in 2015, with relatively little fanfare. I think even Lee, Dan, and Nick, the creators of GraphQL, didn't expect that they had created a pivotal technology that would be a global phenomenon just two years later. On the Apollo team, our primary goal is the overall growth of GraphQL, which we see bringing transformative change to thousands of organizations. In 2017, we really saw GraphQL take off. ## 2017: another year in review DevFeed: [2017: another year in review]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2018-01-02T00:00:00Z Content type: opinion Language: en Sources: [Monica Dinculescu]() Topics: [Post Mortem](), [Redux](), [GitHub]() Tags: [2017](), [post-mortem](), [redux](), [year-in-review]() ### AI overview A personal review of 2017 that reassesses the author's year through projects, contributions, talks, conferences, side projects, time off, and involvement with the Unicode Emoji committee. The author concludes that fewer contributions or talks did not mean the year was unsuccessful. ### Source excerpt You can tell I hate writing year in reviews because this one is really, really late. I tend to hate bragging, and I definitely hate introspective and, in particular, I always think I am underperforming (and that's fine). However, that's usually not true, and writing a year in review forces me to see the awesome things I did, so even if I did end up underperforming, at least I can learn from that. That's the whole point of post-mortems, right? As usual, here's life as GitHub saw it. Red text is projects I've shipped, black text is conferences I've spoken at. Technically I didn't speak at Blinkon, but I spoke to people at it so hey, counting it. The reason why this post mortem is important to me is that before writing it, I literally thought this year was bad and I just "did fewer things". But that's not actually true! I wrote less code than in 2016 (2713 vs 3153 contributions), but that's totally irrelevant? GitHub contributions are a fake idea, and I'm the first one to tell you this, so I don't know why I get worked up about them every year. I contributed to weird branches (which don't get counted), and did a lot of weird explorations that obviously never got merged. I planned things. I wrote design documents. I reviewed design documents. I formed strong opinions. I learnt Redux. Eat it, contributions graph. I gave fewer talks than in 2016 (7 vs 8), but I enjoyed conferences more. I went to a conference where I only hung out with badass women. I went to Railscamp, where I had no wifi and canoed and wore a headlamp like a giant dork. I MC-ed Chrome Dev Summit with Mariko, which was scary, and intimidating and incredibly fun. I built more side projects (10 vs 9). One of them got featured in The Verge! I worked fewer weekends (16 vs 28 days. Goal: 0). And I don't mean on work-work, I mean, at all. On the weekends I play Stardew Valley, or make pottery, or knit, or watch an entire season of Riverdale because I can. Maybe this means I'll work on fewer side-things, and ma ## Year in review 2017 DevFeed: [Year in review 2017]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2018-01-01T00:00:00Z Content type: opinion Language: en Sources: [Jeroen Mols]() Topics: [Android](), [Google](), [data analytics](), [Website]() Tags: [2017](), [android](), [blogs](), [conferences](), [data-analytics](), [developer](), [google](), [kotlin](), [review](), [website](), [year-in-review]() ### AI overview A personal review of 2017 covering family changes, career milestones in Android development, community activities, website improvements, and plans to experiment with data analytics. ### Source excerpt For the first time ever I have my year in review ready in time. I'm sure I'll never forget 2017. Not only did we start building our dream house, but more importantly, our family grew to 4 people! ## Three new Angular Courses to celebrate end of the Year 2017 DevFeed: [Three new Angular Courses to celebrate end of the Year 2017]() Original publisher: [Read original article]() Published: 2017-12-26T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [HTTP](), [API](), [TypeScript](), [Forms](), [reactive](), [Testing]() Tags: [2017](), [angular](), [api](), [courses](), [forms](), [http](), [reactive-forms](), [testing](), [typescript](), [unit-testing]() ### AI overview The article announces three Angular courses covering HTTP requests, dynamic components, and dynamic forms. It highlights Angular's Http service, RxJS and TypeScript integration, HTTP interceptors, progress events, component definitions and dynamic instantiation, and template-driven versus reactive forms. ### Source excerpt Lorem ipsum dolor sit amet ## Time for accountability: Analysis of 2017 and goals for 2018 DevFeed: [Time for accountability: Analysis of 2017 and goals for 2018]() Original publisher: [Read original article]() Published: 2017-12-25T00:00:00Z Content type: opinion Language: en Sources: [Antonio Leiva]() Topics: [Kotlin](), [Android](), [android-apps]() Tags: [2017](), [analysis](), [android](), [kotlin](), [personal]() ### AI overview A personal review of the author's 2017 achievements and goals for 2018, including how Google's announcement of Kotlin as an official Android development language changed his plans for Kotlin books and courses. The article also discusses self-publishing and maintaining a balance between remote work and personal projects. ### Source excerpt Everything Android, Kotlin and other random topics ## Firebase featured in MightySignal's report on fastest growing SDKs DevFeed: [Firebase featured in MightySignal's report on fastest growing SDKs]() Original publisher: [Read original article]() Author: Annum Munir Published: 2017-12-19T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [SDKs](), [Android](), [Mobile](), [Google]() Tags: [2017](), [a-b-testing](), [android](), [community](), [firebase](), [google](), [mobile](), [news](), [realtime-database](), [remote-config](), [report](), [sdks]() ### AI overview Firebase highlights MightySignal's report on the fastest-growing Android SDKs of 2017, noting that eight of the top 20 SDKs were part of Firebase. The post also discusses Firebase improvements, including Cloud Firestore, Remote Config integrations with Predictions, and a new experiment layer for A/B testing. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Firebase Test Lab December 2017 Update DevFeed: [Firebase Test Lab December 2017 Update]() Original publisher: [Read original article]() Author: Doug Stevenson Published: 2017-12-12T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Android](), [Test coverage](), [test-coverage](), [Testing](), [Script](), [APK](), [App](), [JSON]() Tags: [2017](), [android](), [android-testing](), [apk](), [devices](), [espresso](), [firebase](), [huawei](), [json](), [news](), [screenshots](), [test-coverage](), [test-lab](), [testing](), [update]() ### AI overview Firebase Test Lab's December 2017 update introduces Robo scripts for guiding automated Android tests through specific actions and screens, clusters screenshots by display characteristics, and adds several test devices. ### Source excerpt News, tutorials, and updates from the Firebase team. ## A Primer on Optimal Transport #NIPS2017 DevFeed: [A Primer on Optimal Transport #NIPS2017]() Original publisher: [Read original article]() Published: 2017-12-04T08:00:00Z Content type: tutorial Language: en Sources: [Alex Korbonits]() Topics: [Tutorial](), [Machine learning](), [Algorithms](), [Deep learning](), [NeurIPS]() Tags: [2017](), [algorithm](), [applications](), [conference](), [deep-learning](), [ml](), [neurips](), [tutorial]() ### AI overview Lecture notes on optimal transport covering the Monge problem, Kantorovich relaxation, Wasserstein distance, Sinkhorn's algorithm, and applications in generative models and machine learning. ### Source excerpt Lecture notes from Marco Cuturi and Justin Solomon's NIPS 2017 tutorial on optimal transport -- Wasserstein distances, Sinkhorn's algorithm, and applications in generative models and ML. ## The Serverless guide to AWS re:Invent 2017 DevFeed: [The Serverless guide to AWS re:Invent 2017]() Original publisher: [Read original article]() Author: Andrea Passwater Published: 2017-11-09T00:00:00Z Content type: tutorial Language: en Sources: [Serverless Blog]() Topics: [Serverless](), [Amazon Web Services]() Tags: [2017](), [aws](), [aws-lambda](), [cloud-computing](), [faas](), [function-as-a-service](), [guide](), [infrastructure-as-code](), [lambda](), [news](), [re](), [serverless](), [serverless-architecture](), [serverless-framework]() ### AI overview A suggested track for attending AWS re:Invent 2017 and learning about serverless and Lambda. ### Source excerpt Going to re:Invent 2017? Here's our suggested track for getting the most info on serverless and Lambda. ## Serverless panel - the future of event-driven compute DevFeed: [Serverless panel - the future of event-driven compute]() Original publisher: [Read original article]() Author: Andrea Passwater Published: 2017-11-07T00:00:00Z Content type: article Language: en Sources: [Serverless Blog]() Topics: [event driven]() Tags: [2017](), [aws](), [aws-lambda](), [cloud-computing](), [event-driven](), [faas](), [function-as-a-service](), [future](), [infrastructure-as-code](), [insights](), [serverless](), [serverless-architecture](), [serverless-framework](), [transcripts](), [videos]() ### AI overview A post announces full videos and transcripts from Emit 2017, including a panel discussing the future of event-driven compute. ### Source excerpt We're posting the full videos and transcripts from Emit 2017! Here's our panel on the future of event-driven compute. [Next page]()