September 19–20, 2016: Training
September 20–22, 2016: Tutorials & Conference
New York, NY

Ignite Velocity (sponsored by Hewlett Packard Enterprise)

5:00pm–6:30pm Tuesday, 09/20/2016
Beekman
Average rating: ****.
(4.00, 2 ratings)

Sponsored by:
HPE

If you had five minutes on stage, what would you say? What if you only got 20 slides, and they rotated automatically after 15 seconds? Would you pitch a project? Launch a website? Teach a hack? We’ll find out some of the interesting things members of our community are working on and thinking about at Ignite Velocity 2016. Light appetizers and beverages will be served.

 

Your Ignite host

Mike Rembetsy (Bloomberg)Mike Rembetsy (Bloomberg) is the manager of systems engineering and systems administration at Bloomberg, where he oversees all systems-level engineering and infrastructure platform engineering within the Bloomberg infrastructure group and is fostering a culture of learning and mindfulness. Mike has worked in system operations for over 15 years in the web, healthcare, online media, and financial industries. He started out in the help desk area before moving to engineering and has been building and running engineering teams ever since. Previously, he worked for Etsy, iVillage, NBCUniversal, and McDonalds.

Presentations

Avoiding “monitorture”: A unit-testing approach solved our production network monitoring (Yoav Cohen)
Yoav offers a case study providing an inside look at the way Incapsula rethought monitoring and turned it on its head by making it easy for developers to write monitoring scripts in JavaScript and automatically manage DNS routing around the globe.

How Ironman has made me a better engineer (Tana Jackson)
Sports analogies are everywhere, from “knocking it out of the park” to “finish lines” and “sprints” in an Agile development team. The lessons learned in sport are applicable in all areas of life. . .even engineering. Tana discusses lessons learned from years of competing in Ironman triathlons that translate to excelling in the field of engineering.

One does not simply. . .become a software engineer (Renee Lung)
Renee’s journey to becoming a software engineer was about as convoluted as Frodo’s journey to Mordor. She explains how, along the way, she developed a diverse set of skills, met some amazing people, and learned that diving headfirst into the unknown has been the best career choice she ever made.

Avoid the seven sins to achieve amazing user experience (Alon Inditzky)
User experience isn’t everything; it’s the only thing. Alon explains why it’s also the key to building apps that people love to use—apps that are delivered to market faster, perform better, are informed by data, and work seamlessly across multiple platforms.

Programming: The ridiculous parts (Ben Halpern)
The software development industry is serious business and always complicated. It also moves fast and things break. Through the Twitter account @ThePracticalDev, Ben has parodied the iconic O’Reilly animal book covers in order to poke fun at some of our activities. Ben explores the hilarious, sad, and ridiculous truths of the profession and explains why these jokes resonated so well.

Reliably ensuring inclusion: Beyond unconscious bias (Liz Fong-Jones)
Making your team safe and inclusive doesn’t end with unconscious bias training and learning to defuse harmful interpersonal interactions. Your codebase, design documents, and technical communications are likely littered with pitfalls that prevent everyone from feeling included. Liz discusses common inclusivity anti-patterns in code and technical communication and how to avoid them.

So you want diversity, huh? (Tameika Reed)
Tameika explores how to change the mindset of those that are not involved in diversity. How can one want diversity and not show up? When you say there is a pipeline issue, that does not negatively reflect a failure of the schools; it reflects a failure of the tech community as whole.

Ignite karaoke
In Ignite Karaoke, volunteer participants must improvise a short talk based on slides they’ve never seen before and couldn’t possibly predict.