Latest
-
Why everyone’s suddenly talking about AI agents
What exactly are AI agents and how are they different from AI assistants?
-
Should JavaScript really be split in two?
A radical new proposal for JavaScript has divided opinion over who stands to benefit.
-
Learning to trust generative AI
Love it or loathe it, engineering leaders have to learn to live with generative AI, but can you ever really trust the model?
-
From cost to impact: Leading through infrastructure investment decisions
This session explores tools like SLOs, KPI Trees, and the FinOps culture to make cost management a shared responsibility across the organization.
Editor’s picks
That’s a wrap for LeadDev Berlin 2024!
Watch all of the talk videos from an incredible two days with a digital pass.
Essential reading
How to build an effective technical strategy
Building a tech strategy requires a lot of moving parts. Learn about what routes to take and whether decisions should be top-down.
On our Technical Direction playlist
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.
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.
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.
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.
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
-
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
-
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
-
Avoiding “shiny object” syndrome when building software
Technology is fast moving, and devops tools pop up like wildfire. Teams are desperate to solve their problems & often make implementation decisions based on word of mouth, “kick the tires” syndrome or superficial evaluations.
-
Avoiding the pitfalls of rebuilding software
If you think back to the work you were doing last year, it probably feels miles away – and that’s great! As engineers, we’re continually building and creating great new stuff – it’s what we do.
-
An intro to Nativescript
Mobile app development has always required learning each platform’s programming language and peculiarities. For developers coming from the web, where you write once and run anywhere, this is tough.
-
Practical web security
Computer security talks are too often filled with theoretical computer scientists telling us about how the end is nigh. Don’t get me wrong, I love knowing the nitty details of cryptographic algorithms, but a whole lot of web developers don’t.
