Eduardo Ferro Aldama (eferro) personal blog...
Expanding my comfort zone. Agile mindset. Software Developer #Python #Go #FLOSS #agile #extremeprogramming https://github.com/eferro https://linktr.ee/eferro
Development, Agile, Software Crafter, and random tech and nontech stuff.
Opinions are my own.
These are the best podcast/talks I've seen/listen to recently:
Passion, Grace, & Fire - The Elements of High Performance(Josh Evans)[Engineering Career, Engineering Culture, Management, Teams]
Josh Evans talks about the elements of high performance: passion, grace, fire, and what matters when trying to build and shape teams for high performance. He focuses on a period at Netflix when demands on engineering to quickly deliver multiple, parallel, large-scale technical transformations was the norm. The transformations enabled a global, scalable, reliable, successful streaming platform.
Evolutionary Architecture as Product @ CircleCI(Robert Zuber)[Architecture, Design, Engineering Culture, Microservices, Product]
Robert Zuber discusses how the evolution of software development since 2011 has driven the evolution of CircleCI's architecture. From the explosive adoption of Docker to the steady rise of microservice architectures, the changing demands of software engineering teams have proven to be deeply coupled with the structure of their service–far more than they anticipated when they started the business.
The Foundations of Continuous Delivery(Dave Farley)[Continuous Delivery, Devops, Engineering Culture]
Fundamentals of continuous delivery and how it is helping companies produce better software, quicker.
If (domain logic) then CQRS, or Saga?(Udi Dahan)[Architecture, DDD, Design]
The “if” statement – the guard clause that makes sure that what shouldn’t happen, can’t happen. We see it all over our code base, especially in our domain logic. The thing is, when we use properties of domain objects in those if-statements, we don’t even realize that other agents may have just changed that data – or will change it just a second later. In essence, hiding behind those little “ifs”, are all kinds of race conditions and collaborative domains – the places where CQRS approaches are necessary. Join Udi for a different perspective on domain logic, CQRS, and long-running processes. It will be quite a saga.
Continuous Delivery and the Theory of Constraints(Steve Smith)[Architecture, Continuous Delivery, Engineering Culture, Technical Practices](⭐⭐⭐⭐⭐)
In this talk, Steve Smith will explain how easy it is for a Continuous Delivery programme to be unsuccessful, how the Theory Of Constraints works, how to apply the Five Focussing Steps to Continuous Delivery, and how to home in on the constrained activities that are your keys to success. It includes tales of glorious failures and ignominious successes when adopting Continuous Delivery.
Making Work Visible: How to Unmask Capacity Killing WIP(Dominica DeGrandis)[Agile, Company Culture, General, Lean, Management, inspirational, toc]
Are you scrambling to meet deadlines only to find more requests piling up in your inbox? Hidden WIP is a major contributor to clogged value streams and overloaded employees, burdened with too many meetings and frustrating work routines. Making work visible highlights the problems leading to low productivity across the organization. In this talk, Dominica shares how to unmask the things that are killing your team’s capacity and their ability to optimize workflow.
Full Cycle Developers @Netflix(Greg Burrell)[Architecture, Devops, Engineering Culture, Management, Operations](⭐⭐⭐⭐⭐)
Greg Burrell presents Netflix’s journey from siloed teams to their Full Cycle Developer model for building and operating their services at Netflix. He discusses the various approaches they’ve tried, the motivations that pushed them to keep evolving, and the lessons learned along the way.
Reminder, All these talks are interesting even just listening to them, without seeing them.