Berlin

November 4 & 5, 2024

New York

September 4 & 5, 2024

Technical direction

Technical direction

Making better technical and architectural decisions

On our Technical Direction playlist

Lutz Hühnken

Managing architecture

Lutz Hühnken talks about the importance of a strategic approach to software architecture, that prevents teams from becoming architecture firefighters, who spent an excessive amount of energy applying short-term fixes to architectural problems.

Jonathan Maltz

Technical Vision vs. Technical Strategy: The difference and why it matters

Jonathan Maltz digs into the nuts and bolts of setting a successful technical strategy. Startin by talking about the difference between technical vision and technical strategy.

Content sponsored by CoderPad

Writing your technical strategy

Bruce Wang talks about Writing your technical strategy (psst, it doesn’t have to feel like a Squid Game) at LeadDev Together in February 2022.

Jon Thornton

Good technical debt

Jon Thornton discusses how this framework was used to rapidly build and ship Squarespace’s Email Campaigns product in less than 15 months. Along the way, you’ll get several practical guidelines for how tech debt can supercharge your technical investments.

Creating, defining, and refining an effective tech strategy

Having a defined tech strategy creates alignment and keeps everyone on the same page. So how can you ensure yours is most effective? Panelists Anna Shipman, Randy Shoup, Papanii Nene Okai, Nimisha Asthagiri and Anand Mariappan share their tips.

LeadDev Berlin 2024 stage and crowd taken from an elevation showing a massive crowd and lit stage.

That’s a wrap Berlin!

Catch-up on all the Lead Berlin 2024 talks with a digital pass.

More about Technical Direction

Top Technical Direction videos

  • Best practice for seamless product integration

    How to achieve successful integration within existing infrastructure

  • Content sponsored by Rollbar

    Sourcing the perfect product for your team

    Avoid the quick-fix and find the best product for your needs

  • Content sponsored by Lohika

    Laying the foundations for a successful build

    How to ensure the build runs smoothly

  • Weighing up the pros and cons of build vs buy

    Off the shelf or build it yourself?

  • Forging the path to faster shipping in enterprise orgs

    Working for large corporates doesn’t mean you have to live with slower shipping times.

  • Carving a modern engineering org out of an enterprise

    Adopting best practices from tech-first companies

  • Universal Apps: Architecture for the Modern Web

    “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.”

  • Traps on the Path to Microservices

    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