We're really excited to welcome such a great lineup of speakers to The Lead Developer New York 2018, delivering talks on topics ranging from company culture and teams to microservices and incident management.
Teams that write code together should be able to debug issues together. But while we think a lot about engineering collaboratively, we rarely develop processes for debugging collaboratively. Often, debugging is the hardest part of the job. What does an engineer do when the logs have expired, she can’t reproduce the issue, and she's tested five different hypotheses? I’ll talk about a workflow that allows teams to collaboratively debug issues without repeating work or losing progress and why it makes sense.
The product and engineering teams at every company size have the same goals: positive team health, high-velocity shipping, and strategic execution. Yet we often get in our own way -- from ill-defined roles and responsibilities to toxic communication patterns, to well-meaning but under-equipped managers.
Lara Hogan and Deepa Subramaniam will candidly share the approaches they took to revitalizing a cross-functional product organization in 9 months. As Engineering and Product leaders, they worked together to diagnose and treat issues holding back design, engineering and product management teams in order to ensure communication flowed better, inter and intra-team dynamics improved and the organization shipped more (and better!) software. As two VP’s who faced these specific challenges and more, Lara and Deepa will cover evidence-based tactics for improving the overall health of your product organization when time is of the essence.
Reliability is a critical feature of most software, and maintenance rather than initial development predominates the cost of software. Yet, a large number of development teams treat operations as an afterthought instead of integrating operations into their development processes.
Error budgets and Site Reliability Engineering practices can improve the reliability, maintainability, and, yes, feature velocity, of products. This talk is an introduction to the basics of bringing SRE practices into your organization -- who to hire, how to organize, what projects to work on, how to measure reliability, and how to assess reliability risks.
This talk is based on a series of experiences I had working with my interns, sharing their experiences on other internships and improving my methods so we could take most of our 12 weeks together. The biggest highlights are related to fast and focused technical bootstrap, connecting with a trusted network of experts inside the company and building up confidence on public speaking and presentation skills.
In this talk we'll walk through a hypothetical worst case scenario for a new manager and then walk through specifics on how you can avoid the Spiral.
After Netflix helped popularize microservices, you probably heard the architectural pattern labelled a boon. However, if your team is tasked with implementing the pattern it is too easy to find yourself in a place where you've significantly increased your architectural complexity without deriving any of the benefits that microservices purport to bring, especially if implemented without proper organizational maturity or careful foresight and follow-through.
ThoughtWorks has led many teams and organizations along the path from monoliths to microservices and this presentation covers three of the major traps that we’ve experienced (as well as how to avoid them). The traps covered are, underestimating the cost of a microservice, overcentralization, and neglecting the monolith.
In today's web environment, performance and Search Engine Optimization (SEO) are important to successful apps. Universal architecture provides a hybrid approach to building web apps that combines server-side rendered applications and Single-Page Applications (SPA). This architectural approach improves the user experience and makes it easier for your site to serve content to search and social bots.
This talk will explain the methodology and benefits of the universal approach. It will explore some of the tradeoffs and challenges that come with universal architecture. Finally, we will cover the various implementation options available today. At the end of this talk, you'll be able to evaluate if universal architecture is a good choice for your projects.
More rapidly then ever, companies are adopting new technologies, tooling and practices, that allow them to be so agile that it changes their culture overnight. Disruptors are being disrupted within the year. Fast movers are overhauled quickly due to instant response of competitors. Longterm strategies, roadmaps and plans appear useless.
During this inspiring talk Kim van Wilgen shows you how moving towards continuous delivery and DevOps changes the DNA of your company. Learn how continuous delivery will speed up your company at all levels. How your thinking changes through the presence of fast feedback, short cycles and data-driven decision making. It’s time to move to the continuous culture.
A skilled Incident Commander can improve time to resolution and reduce everyone's stress. An IC needs more than technical savvy to excel in this challenging role. We'll explore how to build strong incident management skills in individuals and how we've developed organizational processes to drive down MTTR and make both our customers and our engineers happier.
Facebook, Google, Uber, LinkedIn, and friends are the rarefied heights of software engineering. They encounter and solve problems at scales shared by few others, and as a result, their priorities in production engineering and architecture are just a bit different from the rest of us down here in the other 99% of services. Through deconstructing a few blog posts from these giants, we’ll evaluate just what is it that they’re thinking about when they build systems and whether any of their choices are relevant to those of us operating at high scale yet still something less than millions of requests per second.
This talk will go into depth on how to make technological decisions to meet your customers’ requirements without requiring a small army of engineers to answer 2 AM pages, and how to set realistic goals for your team around operations, uptime, communications, and disaster recovery.
Give a developer readable code and they can code for a day, teach a developer best practices and coding standards and they can be a valuable addition to any engineering team. But just as we depend on code standards so that we can all work in a shared codebase, we need a standard for psychological safety on our engineering teams, especially when it comes to underrepresented minorities.
In this talk we will break down our unconscious biases, learn how to level up from allies to accomplices, and practice techniques for building an intersectional support system so that our teams can be just as performant as our code.
Have you ever worked on a computer system that was so fragile it was frightening to make changes to? Maybe it was challenging to deploy, difficult to delete code, or changing one piece would cause surprising cascading failures.
This talk will focus on ways our tools, systems design, and processes can enable a team to do high velocity, confident work, and yes, reduce the fear of the computer.
Our industry is not the best at preparing developers to grow their careers when they reach the critical point when they have to decide between continuing to work as an individual contributor or moving into management. Stories of great developers being nearly forced into management are all too common, and developers that want to become managers aren’t given the proper guidance on that transition.
For those that follow what turns out to be the wrong path for them, they may feel the only way to switch paths is to switch companies, which is a loss for both the company and the developer.
As technical leads and managers, it is our duty to mentor developers as they approach this point in their career. This talk will help you to guide that conversation with insight from someone who has had first-hand experience on both paths.
When we work alone, it’s easy to make sure things come out the way we think is best. But what happens when we need to get an entire team to agree on — and actually _use_ — best practices? What if we have to convince an entire _company_?
In this talk, we’ll learn how IBM is working to get huge, distributed teams to not only agree on a set of best practices but to actually follow them, leading to:
Learn battle-tested strategies and techniques that will benefit companies of any size, helping create teams that are more engaged, more effective, and more cohesive.
The OpenAPI spec (formerly known as Swagger Spec) is now in version 3.0 ... but what does that mean to you? If you're creating or consuming APIs, come find out what's new in the spec, what's new in the world of OpenAPI tooling for development, documentation, and testing, and how OpenAPI can help you get the most out of your APIs!
Even if you've used OpenAPI or Swagger before, a lot has changed in 3.0! You'll also learn how you can keep up-to-date on the spec, how you can persuade your team to embrace the spec, and how you can contribute!
Please get in touch with Daisy Wort, Sponsorship Manager, to request a sponsor pack.