In our new episode, @stilkov talks with @simonbrown about software architecture: The importance for developers, its role in agile software development, documentation and tooling, and the importance (or lack of importance) of UML
https://t.co/Up3QWNI0KB
“We delivered twenty story points” really just means “we made the product more complex”. Like that quote from @gojkoadzic ‘s article https://t.co/rsMJObWX9h
🤩 BLOG ALERT 🤩
"Forward Compatibility for the Scala 3 Transition"
Scala 2.13.4 can use Scala 3 dependencies, find out how to:
😌 incrementally migrate a multi-module project to Scala 3
🥳 use Scala 3 libraries in a Scala 2.13 project
https://t.co/DEoHMSFsaa
@Kurt_Haeusler As any process, status meetings are training wheels that will eventually drop off or evolve as team matures. Their value is to aid forgetful and biased human brain, like reminders, checklists and alarms.
@ScalaWilliam@JeremyKorwin@ScalaAlgorithms Glad to hear that. My influence was practicing TDD code katas and discussing different approaches with the software craftsmanship community. Implementing algos is perfect for learning TDD.
X : I'm an expert in agile.
Me : Good on you. I'm sill learning.
X : Would you like me to teach you? Have you ever done any agile before?
Me : I started using XP around 2000, just before the agile manifesto came out. I think this graph will help you.
@BjoernRochel That resonates a lot lately. I find particularly inspiring how e.g. Dalio’s principles and Basecamp approach org design from evolutionary perspective with deliberation and guided by values