Dr. Mik Kersten is an independent technology strategist and researcher best known as the creator of the Flow Framework and author of the bestselling book Project to Product. Mik founded Tasktop and led the company as CEO until its acquisition by Planview in 2022. He continues to support Planview as an Executive in Residence.
Mik started his career as a Research Scientist at Xerox PARC as part of the team that created the first aspect-oriented programming language. He then completed his PhD in Computer Science at the University of British Columbia, where he pioneered the integration of software development and collaboration tools. That work became the foundation for Tasktop and helped shape the emerging field of Value Stream Management. Before shifting his focus to flow, outcomes, and organizational modularity, Mik wrote more than one million lines of open-source code that are still in use today. His work now focuses on helping leaders transition from output-driven management to outcome-driven operating models, enabling organizations to harness the power of AI in a human-centric way. Mik lives in Vancouver, Canada, and enjoys skiing, biking, and surfing with family and friends.
I hope you enjoyed this show, please head over to Apple Podcasts and subscribe and leave me a rating and review, even one sentence will help spread the word. Thanks again!
The Angular ecosystem continues to deliver cutting-edge tools for interactive web apps, reactive form handling, and generative AI pipelines. This week, our global community experts share practical guides on fine-tuning inputs, mastering modern routing, and leveraging Google’s Veo model directly from Angular!
Dive into this week’s expert-led resources:
Signal Forms: Clean Value Transformations with transformedValue (French)
Modeste Assiongbon (@rblmdst) breaks down a critical form primitive in Angular v21. Learn how to use transformedValue to handle data formatting and parsing cleanly between your UI controls and reactive data models.
Better Numeric Inputs in Angular (Signal Forms + Angular 22)
Brian Treese (@brianmtreese) demonstrates how to build slick, robust numeric input controls. Discover how the latest updates in Angular 22 pair with Signal Forms to eliminate messy validation hacks and streamline data entry.
Mastering the Angular Router & The State of Modern Angular (Spanish)
Kevin Davila (@kevindaviladev) delivers two must-read articles! First, a comprehensive, practical guide covering everything you need to know about the Angular Router. Second, an inspiring breakdown of why Angular is in its best, most developer-friendly era yet.
Extending Videos with Veo 3.1 Lite, Angular & Firebase
Connie Leung (@connieleung404) shares a complete blueprint for multimodal generative AI! Learn how to extend video content dynamically using Angular, Veo 3.1 Lite, and Firebase (Cloud Functions + Cloud Storage) for seamless cloud-native processing.
Aristeidis Bampakos (@abampakos) has launched the brand-new 4th edition of Angular Projects! Master modern Angular by building 10 real-world enterprise applications, covering everything from AI pair-programming with Copilot to SSR/SSG, state management, and reliable UI architectures.
I remember being in the room at DEF CON 23 in Las Vegas, in 2015, listening to "Let's Encrypt – Minting Free Certificates to Encrypt the Entire Web". It was still months before Let's Encrypt would launch their public beta and begin cementing 90-day certificates as the new norm. More than a decade later, Let's Encrypt have just announced their first ever reduction to their default certificate lifetime, and it's coming soon.
The Dates
Here's what's happening and when:
Date
Change
14 Oct 2026
Staging starts issuing 64-day certificates
10 Feb 2027
Production default drops from 90 days to 64 days
10 Feb 2027
Authorisation reuse drops from 30 days to 10 days
11 May 2027
The last 90-day certificate expires
16 Feb 2028
Default drops again to 45 days, authorisation reuse to 7 hours
Any certificate issued on or after 10 Feb 2027 gets a 64-day validity period, unless you've already opted in to something shorter than that. Those options have been around for a while now, with the 6-day certificates available via the shortlived profile and 45-day certificates via the tlsserver profile. What changes in February is the validity period for certificates using the default profile, so this will impact everybody, including those that may not have been paying attention.
Why Now?
Let's Encrypt have been ahead of the curve for their entire existence, launching with 90-day certificates when 3-year certificates were the norm, and this change is a continuation of that trend.
Last year, Ballot SC-081 passed at the CA/Browser Forum, setting a schedule that takes the maximum certificate lifetime from 398 days down to 200 days (March 2026), then 100 days (March 2027), and finally 47 days in March 2029. The maximum period that domain validation data can be reused shrinks alongside it, down to just 10 days by 2029.
Let's Encrypt's 90-day certificates were already comfortably inside the 2026 and 2027 changes, so they didn't have to do anything until 2029. Instead, they're stepping down gradually, with a 64-day stop on the way to 45 days, and giving everyone the ability to test this out gradually.
As for why shorter is better, I've been banging this drum for a long time... Revocation is broken, and has been for as long as I've been writing about it, so the only reliable way to limit the damage of a compromised key or a mis-issued certificate is to make sure the certificate doesn't live very long. I wrote Why we need to do more to reduce certificate lifetimes back in 2018, watched Ballot SC22 fail in 2019, saw Apple force the issue with the 1-year cap in 2020, and then asked Are shorter certificates finally coming?! in 2024. They are, and this is what it looks like when they arrive.
What Might Break
If your ACME client supports ARI (ACME Renewal Information), Let's Encrypt will tell it when to renew, and you don't need to think about the lifetime of your certificates at all.
ARI is relatively new though, and I'd bet, given how long Let's Encrypt have been around, that many automation processes are run on a fixed schedule. For 90-day certificates, renewing at 60 days old would be quite typical. This means that for those who have a fixed 60-day renewal process, this first reduction to 64-day certificates will just catch the new certificates before they expire, an intentional choice from Let's Encrypt I'm sure. If that is the case, organisations won't see any negative impact from this first reduction, but the 47-day certificates coming in March 2029 will cause problems and Let's Encrypt are reducing their certificates to 45-day certificates in February 2028 ahead of the deadline.
What To Do Now
The best thing is to check if your ACME client supports ARI and use that wherever possible. If not, you need to check how your certificates renew and if it's a fixed schedule. If you're renewing on a fixed schedule, it ideally needs to change to be relative to the validity period of the certificate, and you should aim to renew your certificates when they're 2/3 of the way through their validity period. For your existing 90-day certificates that's at 60 days, but for these new 64-day certificates, I'd be renewing them at 42 days.
After more than a decade at 90 days, the default is finally moving, and in a little less than 18 months from now, every Let's Encrypt certificate will be valid for half as long as it is today! It's pretty crazy to look back over how the ecosystem has changed during that time, and it's fair to say that Let's Encrypt has played, and continues to play, an enormous part in that.
If you are building a B2B SaaS product multi-tenancy is a foundational requirement. Your customers are companies, and each company expects its own isolated space. Getting this right early saves enormous pain later.
Two phones in the same room, no server, no Wi-Fi, and nothing but Bluetooth between them. That should be easy, and it has never been. So I took the SignalR hub model and put it on the radio: one C# interface, generated proxies, request/response, streaming, events, groups and JSON, with every byte chunked, framed and reassembled for you.
Log in
Dr. Mik Kersten is an independent technology strategist and researcher best known as the creator of the Flow Framework and author of the bestselling book Project to Product. Mik founded Tasktop and led the company as CEO until its acquisition by Planview in 2022. He continues to support Planview as an Executive in Residence.
