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

  • Handling security issues as an engineering team

    We live in a world of technology and engineering. Almost everything around us requires software. Unfortunately, the software we use or build has bugs. While most bugs can be fixed, there are these other types of bugs, called vulnerabilities, that cause headaches and haunt us at night.

  • Using an ‘architectural North Star’ to align your engineering team with your organization

    In a fast-growing, agile organization, teams are usually encouraged to self-organize. Equipped with the guiding principles such as fast iteration and frequent feedback loop with the customers, we entrust the most valuable asset, people, to make informed decisions.

  • Splitting the monolith

    After years—even decades—on the existing legacy mainframe, we pitched a plan to migrate a company to a new, microservices-based architecture. Convincing management seemed easy, but now we have to deliver: Take the years-old legacy system and break it apart into smaller services and systems we can actually maintain.

  • The race to Mach 2.0 at scale

    When Chuck Yeager became the first pilot to fly faster than the speed of sound, he set off a race around the world to do the same with a plane full of paying passengers. The United States, Russia, the UK, and France all wanted a piece of the inevitable fortune to be made building aircraft to cross oceans faster than sound itself.

  • Creating an effective process for on-call engineering teams

    Uptime matters, but so do your people. At Intercom, keeping our product online and working well at all times is critical to the success of our business.

  • Mobile development 10 years on: native vs. cross-platform

    We’re 10 years into Android and iOS development and there are more ways to build an app than ever before.

  • Building a culture of security for your infrastructure teams

    Security is an increasingly important aspect of software development, especially for services that process and store sensitive data.

  • Shor’s algorithm and how to avoid oncoming catastrophes

    Quantum computers are real and are starting to be used for some interesting applications. As well as many applications in finance, organic chemistry and complex dynamical systems there is an ugly elephant in the room. That elephant is Shor’s algorithm.