Polina Giralt talks about how some of the most impactful technical work is about unwinding a humungous mess. This talk is about lessons learned over my career about executing challenging projects. The types of projects with politics, drama, tech debt, or past failed attempts. How do we know if the project is worth doing? Why has it failed before? Who’s blocking it? How do we know when to cut our losses and pause or cancel the project?
Being a good software engineer is not necessarily the same as being an effective one. Here, Google’s Addy Osmani identifies the ten key traits of effective software engineers.
Francisco Trindade discusses how to achieve a balance between being proactive enough to drive positive change while avoiding micromanaging by using systemic thinking and talking about how an EM can be a positive leader for their team.
Jason Blanchard explores the idea that we can model and de-risk change by thinking of everything as a migration from a current state to a desired state and what that means for our architecture and teams
Hila Fish covers useful best practices, pitfalls to avoid and major obstacles to anticipate so that you can scale them across many teams, avoid refactoring, and get a flying start now -- AND optimize for the future.
Pablo Jablonski shares key learnings from building and shipping Spaces within Twitter, and how those learnings can be applied to any new team looking to move quickly within a larger organization.
David LaMothe discusses a model much like the DORA4 model, except instead of focusing on metrics like time to merge and rate of recovery, focusing on personally developed metrics for feedback that ensures he is giving it early and often.