-
Building and scaling distributed teams
Remote work is the number one desired workplace setup for developers. As a lead dev, you’re able to hire from a global talent pool, and your team’s productivity, engagement and retention can soar as everyone works in the way that’s best for them.
-
A tour of Apache Pulsar
Apache Pulsar is a distributed pub/sub system develop at Yahoo! This talk covers Apache Pulsar's underlying design and protocol level semantics.
-
Creating learning workshops for developers
Interactive workshops are the best way to engage teams and individuals and help everyone remember lessons learned.
-
Building a data infrastructure
Your team needs data so they can make the right decisions. Unless they have the right data in the right place, they're left to act on intuition, opinions and hunches.
-
Planning, executing, and landing refactoring
Slack is the leading global collaboration hub that makes people’s working lives simpler, more pleasant and more productive.
-
Why GraphQL?
If you don’t know much about GraphQL, you probably just identify it as the hip, shiny new thing companies are adopting to replace their RESTful APIs.
-
Everything You Need to Know About OpenAPI 3.0 in Ten Minutes or Less
The OpenAPI spec (formerly known as Swagger Spec) is now in version 3.0 ... but what does that mean to you?
-
How to Design Systems and Processes Teams Actually Follow
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?
-
How to hold career path conversations with developers
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.
-
Strategies for reducing the fragility of your systems
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.