DeveloperWeek New York 2020 DeveloperWeek New York 2020

Main Stage

Join on Hopin

Wednesday, December 9, 2020

- EST
Engaging Users with Content - Make a Personalized News App
David Gutierrez
David Gutierrez
Dow Jones, Developer Strategy & Relations

Personalized content is a great way to drive engagement in mobile apps. In this session we explore the structure of a news app with Flutter, Firebase, Python, Tensorflow and Dow Jones APIs.

- EST
Harnessing the Power of the Unbundled Database
Alex Silva
Alex Silva
Pluralsight, Data Platform Architect

Since the mid-1980s, relational databases have been standard for most applications needing to store and query structured data. As architectures became more complex, databases have generalized to fit a variety of use cases. Simplicity was key: databases encapsulate storage, indexing, caching, querying, and transaction management, all under a unified SQL view.

Alex Silva examines what could happen if microservices could “unbundle” the database into its separate constituents and distribute these concerns into different layers and be able to optimize them individually. He proposes a stream processing architecture that can be used to successfully “deconstruct” the database while analyzing the challenges and pitfalls.

You’ll approach subscription and replication protocols under a different light by exploring how relational databases have overcome these challenges and focusing on what works and what doesn’t while discussing the paradigm shift proposed by stream processing and the architectural differences between the two approaches.

- EST
Build a Full-Stack Serverless Application on Azure
Jason Specland
Jason Specland
Microsoft, Cloud Solution Architect

You want to build great cloud-native applications. You don’t want to bother with cumbersome server infrastructure. Microsoft Azure offers a host of serverless choices, but where to start? In this session, we will explore the “bread and butter” serverless offerings that form the building blocks of most applications. We’ll take a deep dive into an open source content management system that was built serverless from the ground up on Azure. We’ll start with Azure Functions and humble Storage Accounts, and we’ll progress all the way to worldwide Content Delivery Networks. Together, we’ll build a complete, full-stack application without provisioning a single server.

- EST
How to Become a Great Developer: Case Studies of How Individuals Rose from Nowhere to Become Experts
Wilson Mar
Wilson Mar
International consulting firm, DevSecOps leader

After mentoring many developers over the years, I summarized the advice into a trending article on LinkedIn. Here are case studies of how individuals rose from nowhere to become experts.

- EST
Seeing RED: Multi-Dimensional Monitoring for the Real World
Dave McAllister
Dave McAllister
Splunk, Technical Evangelist

RED (Rates, Errors, Duration) is a spinoff from Google’s Golden Signals designed for monitoring microservices. However, RED use has clearly demonstrated that the applicability is applicable to any services-based architecture.

With RED, unlike the modern belief in observability, your architecture is watched from aspects of multiple dimensions. You receive alerts and indications not just from anomalies, but also from headache alerts. By seeing multiple dimensions of concerns, be they failures in service or activity to close to the edge of capability, these combined monitors and deep-dive, focused access get you to your root cause faster, with less false positives and quicker resolution.

Join Dave McAllister as he explores a RED driven analysis of an active application environment.

- EST
Advancing by Open Source: How to Get to CI/CD
Tracy Miranda
Tracy Miranda
Continuous Delivery Foundation, Executive Director

The open source software community continuously supports and advances the adoption of CI/CD best practices and toolsets.

For example, the CD Foundation serves as a vendor-neutral home of many software projects within CI/CD space, such as:

1) Jenkins X, a Kubernetes-native continuous delivery solution for cloud applications. This project uses a completely new architecture and code base in comparison with the original Jenkins project.

2) Spinnaker, an open source, multi-cloud continuous delivery
platform.

3) The Tekton Pipelines project, which provides Kubernetes-style custom resources for declaring continuous integration and delivery pipelines. Spinnaker can use Tekton as its pipeline engine.

4) And more

What’s more is that the open source community is helping to define shared terminology, open standards, and abstractions for CI/CD to help enterprises increase performance and software delivery. These resources help to assist with interoperability between CI/CD components, and also promote innovation in the areas that can provide the most value to the business.

This talk outlines important initiatives taking place and ways to tap into community resources and get involved so we can all work together to accelerate CI/CD adoption around the world.

Attendees will learn:
- A brief overview of multiple open source projects and how the community is working toward interoperability between them to serve as a model for the future of software.
- Take a look at the goals of the open source community today and key initiatives such as CI/CD landscape, security, diversity and MPs.
- How to get involved in open source projects to drive forward the direction of CI/CD and make software delivery better for everyone.

- EST
DevOps for Developers (or Maybe against Them?!)
Baruch Sadogursky
Baruch Sadogursky
JFrog, Head of DevOps Advocacy

"DevOps" is the operations people’s crafty plan to make developers do other people's work, but we are smart enough to see right through this naive rebranding trick!

Baruch suggests you think about it: we, the developers, have written all the code. It passes all the tests; it obviously works, and works well (Are we a little proud? We are!); so we are DONE.

Now, out of the blue, a bunch of "thought leaders" (all with an operations background, mind you!) are trying to tell us that we have to learn YAML, Docker, Kubernetes and Terraform to deploy our software because suddenly it is our concern?!

In this talk, we'll discuss why developers do or don’t need DevOps. We'll consider arguments made by DevOps visionaries and see whether they hold water. Hopefully, by the end of the talk, we'll understand whether DevOps really helps developers to deploy better code to production more often, or if it is just another scam made up by marketing and evangelists.

- EST

Thursday, December 10, 2020

- EST
Debugging Engineering Velocity
Smruti Patel
Smruti Patel
Stripe, Engineering Manager

Have you felt frustrated by your team's speed of execution? Have you asked yourself, perhaps in the middle of a sprint planning session: Are we stuck?

Why do some teams seem to work faster than others? Why do some people perceive a team as too slow, while others consider the same team fast enough? And engineers on some teams appear to be more satisfied and more motivated than those on other teams; why?

Engineers don't lack motivation -- it is systems that fail to create an environment for engineers to make magic. In this talk, I’ll lay out a step-by-step guide for managers and ICs to ask the right questions towards this problem.

Alignment: Are the team’s goals and metrics aligned with the business? Is the team aware of broader priorities and constraints? Is there agreement around when to optimize for user-visible features vs technical debt? Is there alignment around what exactly the team owns?
Doing Too Much: Is the team keeping too many projects active at the same time? We’ll talk about how to identify if this is happening, and how to use metrics and models to choose what to prioritize.
Thrashing: Big and frequent changes in priority can make engineers take the priorities themselves less seriously— but such change is a reality in a fast-growing company. How do you reduce thrashing as well as increase adaptability to change?
Deep, slow projects: Some projects simply take a long time. This is especially true for infrastructure work. In this context, it’s important to demonstrate value early— engage with users, go deep before going broad.

As a manager or lead developer, this talk will give you a playbook to analyze and work on your team’s engineering velocity— and ultimately, to create an environment where people work together at their highest potential.

- EST
So You’ve Been Asked to Double Your Engineering Team…
Chris Stasonis
Chris Stasonis
Lola Travel, VP, Engineering

o your company just took a round of funding and you’ve been asked to rapidly grow your engineering team? Congratulations! This is an exciting challenge. It can also be daunting. You’re in for a lot of hard work, a lot of organizational changes, and the satisfaction of building an amazing new team. I’ll share some experience and advice from being given this challenge multiple times at both large and small companies.

Who is this for?

My advice will mostly focus on growing teams of ~10 to teams of ~40, but much of the advice applies to any serious hiring push regardless of current team size. The people who will get the most out of this are managers of multiple teams, VPEs/Director’s of engineering at smaller scale startups, but also people that are part of an interview panel on a fast growing team.

- EST
Observability at Brex: Leveraging Logs to Fight Fraud and More
Thomas Cesare-Herriau
Thomas Cesare-Herriau
Brex, Lead of Observability
Sherwood Callaway
Sherwood Callaway
Brex, Software Engineer

Logs are ubiquitous and indispensable. They are arguably the most important tool used by software engineers in our day-to-day work. In development, we use them to mark key points in our code, so we can peek into its execution (without using a debugger). In production, they serve as a way of understanding software execution in the real-world, providing immense value at both the macro and micro levels; they can be used to diagnose systemic problems, which affect your entire user base, but also to trace the journey of a single user, thus allowing you to provide individualized support.

Unfortunately, most companies are not taking full advantage of logs, because they fail to see what logs really are: a source of rich, real-time event data. In this session, we will explain how the Observability team at Brex unlocked the power of logs by allowing other teams to access and build on top of structured log streams. This was accomplished by (1) designing and implementing a super-powered logging infrastructure, which delivers log messages to multiple consumers in near-real-time, and (2) creating a strict log schema as well as a schema-adherent logging library to make the underlying data useful and coherent.

We will also deep dive into a particular use case: powering the alerts used by our Fraud team to identify suspicious behavior.

- EST
Managing Failure as a First-Time Manager
Junaid Warwani
Junaid Warwani
Jetty, Senior Engineering Manager

Your first time as a manager is not easy. You say some wrong things, make a few wrong decisions, and face lots of uncertainty. Being a great developer doesn't guarantee that you can help others be better developers.
This talk is about what I learned after going from a senior engineer in a team of three to managing a team of seven engineers. I will focus on the things you can do to prepare yourself if you are making the same transition, and the things a senior engineering leader can do to help someone in that transition.

- EST
Technically Speaking: Improve Your Code with Documentation
Alexandra White
Alexandra White
Google, Technical Writer

Well written instructions, informative comments throughout code, clearly scripted screencasts, and smart information architecture can take complex code and make it accessible to new developers. In the age of code sharing, this can be imperative to teaching the next generation of developers, passing along your code to successors, and help you better understand your own work.

When I was an engineer, helpful READMEs and other docs created by my colleagues were crucial to quick onboarding and coming back to old products. Now, as a full time technical writer, I rely on our engineers to be able to concisely explain how products work. From these experiences, I feel it is essential that everyone feel empowered to write documentation, not just the technical writers.

In this talk we’ll discuss:

+ Why writing docs is important for engineers
+ Understanding your audience
+ Optimizing for the deliverable: READMEs, code comments, tutorials, release notes, and more

We’ll also cover some tips for communicating about your past work to your future self.