phillyete

Philly ETE 2015 #26 – Soumith Chintala – The Deep Learning Revolution: Rethinking Machine Learning Pipelines

In the last decade, a class of machine learning algorithms popularly know as “deep learning” have produced state-of-the-art results on a wide variety of domains, including image recognition, speech recognition, natural language processing, genome sequencing, and financial data among others. What is deep learning? Why has it become so popular so quickly? How can one fit deep learning into existing pipelines?

Philly ETE 2015 #22 – Michael Toppa – Agile Contracts for Software Consultants

You’re ready to go with all the best Agile practices: you’ll develop incrementally and iteratively, you’ll have sprints and retrospectives, and you can’t wait to tell your clients about your velocity and show them your burndown charts. But all of your prospective clients are telling you they want firm quotes, and contracts with detailed specifications and delivery dates. How do you convince them a traditional contract is actually riskier than they think, and persuade them to instead sign an Agile (time and materials) contract?

Philly ETE 2015 #21 – Aaron Bedra – Rock ‘Em Sock ‘Em Robots: Bot Swatting Like the Pros

Join Aaron as he explores ways to identify and deal with bad robots. He will show you what to look for, how to sort good bots from bad, and what to do with the information once you have it. It will help you deal more efficiently with scrapers, crawlers, scanners, fraudsters, and general malicious activity on your systems and gain some much needed confidence and visibility into the types of traffic you actually get on a day to day basis.

Philly ETE 2015 #20 – Svetlana Isakova – Kotlin on Android

In this session we are going to talk a bit why JetBrains sees the potential in Kotlin comparing to other JVM languages. Then we’ll see how certain language constructs can be used to make Android more enjoyable. Also we’ll look at a DSL for type-safe dynamic layouts and a simple extension plugin that helps to avoid writing ‘findViewById()’ all the time.