Responsive Design
The Limited Red Society
Sandi Metz - Talk Session: Polly Want a Message
Alistair in the "Hexagone" 1/3
TDD: Balancing Progress with Stability
Experience report: first week of 2 x 5 mobs going remote
The story about how we do Agile Technical Coaching
Why unit testing is not enough when it comes to microservices
Episode 180: Extreme Programming & 3X Explained with Kent Beck
Really Simple CQRS
On the Criteria To Be Used in Decomposing Systems into Modules
ITkonekt 2019 | Robert C. Martin, Clean Architecture and Design
A Second Conversation with Werner Vogels
Approval Testing: Agile Testing that Scales
Message Obsession
Domain-Driven Design in 2020
Evolutionary Design: Techniques and Example
John Doerr on OKRs and Measuring What Matters
How to Set Good OKRs With Examples
Startup Lab workshop: How Google sets goals: OKRs
What is an OKR?
Michael Feathers - the deep synergy between testability and good design
Refactoring and Generalization in TDD
Gee Paw Hill & Alex Bolboacă: XP, Change Harvesting and Camerata
YOW! Perth 2019 - Kent Beck - 3X: Explore / Expand / Extract
REST API Design - Resource Modeling
Matteo Baglini "Onion Architecture with Functional Programming sauce"
Slicing Functionality: Alternate Paths
Teams are immutable structures
Ready for changes with Hexagonal Architecture
Test-driven development: Write better code in less time by Evan Dorn
Chapter 5 of Understanding Design Thinking, Lean and Agile
Chapter 4 of Understanding Design Thinking, Lean and Agile
Chapter 3 of Understanding Design Thinking, Lean and Agile
Chapter 2 of Understanding Design Thinking, Lean and Agile
Chapter 1 of Understanding Design Thinking, Lean and Agile
The story about how we do Agile Technical Coaching
The Beginning of Extreme Programming
Understanding the Four Rules of Simple Design
What is an aggregate with Thomas Ploch
Martin Fowler and Toby Clemson - Experimentation Using Event-based Systems
The Barbarians are at the Gates
Clean Architecture
Agile and architecture, finally friends after 15 years
Simple Hickey
Screaming Architecture
Bringing Balance to the Force
What Software Craftsmanship is about
Squad Health Check model - visualizing what to improve
Advocating Against Advocating Against
How Developers Stop Learning: Rise of the Expert Beginner
Sooner, Not Faster Revisited
How to Plan your Week the Right Way
How to Plan Your Week | The Art of Manliness
Monolith Decomposition Patterns - Sam Newman
Sooner, Not Faster
Organic Software Architecture
The Brand Called You
Alberto Brandolini: The Gordian Knot - SCL Conf 2019
Understanding Legacy Code with TCR (test && commit || revert)
Why Event Sourcing is a microservice communication anti-pattern
Practical DDD: Bounded Contexts + Events = Microservices
Endo-Testing: Unit Testing with Mock Objects
Event Sourcing after launch - Michiel Overeem - DDD Europe 2018
SunDDDay discussion: CQRS & Event Sourcing systems with Alexey and Marco
Building an Event Storage
The Thing of Software Development
The Path Already Taken
Programming is not a craft
What Software Craftsmanship is about
A Conversation with Werner Vogels
TDD on Punch Cards
Keith Harrison - Creating a Culture of Software Craftsmanship
The Principles of Clean Architecture by Uncle Bob Martin
Simplicity, Please - A Manifesto for Software Development
Code Refactoring: Learn Code Smells And Level Up Your Game!
Opening Keynote: Greg Young - Stop Over-Engenering
Part 2/3 - Refactoring item logic using 'lift up conditional', Emily Bache
Part 1/3 - Introducing the Gilded Rose kata and writing test cases using Approval Tests, Emily Bache
Feature Branching is Evil (Thierry de Pauw, Belgium)
substring, TCR style
Refactor your language knowledge portfolio - we are what we can code in
Kent Beck - 3X Explore/Expand/Extract
The NoEstimates Movement
A Critical Step towards #NoEstimates
Agility ≠ Speed - Kevlin Henney
RailsConf 2014 - All the Little Things by Sandi Metz
Post-REST
Panel Discussion: Technical Practices - SCLConf 2018
Emily Bache: Effective Technical Agile - SCLConf 2018
Chapter 7 of The Agile Samurai: Estimation: The Fine Art of Guessing
Chapter 6 of The Agile Samurai: Gathering User Stories
Developers should abandon Agile
TDD for those who don't need it - GopherCon SG 2017
Chapter 5 of The Agile Samurai: Making it real
Chapter 4 of The Agile Samurai: Seeing the Big Picture
Coaching Technical Practices
Chapter 3 of The Agile Samurai: How to get Everyone on the Bus
A craftsman's guide to designing a clean architecture, Marcus Biel
Chapter 2 of The Agile Samurai: Meet your Agile team
Chapter 1 of The Agile Samurai: Agile in a Nutshell
Chapter 19 and 20 of Extreme Programming Explained: TPS and Applying XP
Chapter 18 of Extreme Programming Explained: Taylorism and Software
Chapter 17 of Extreme Programming Explained: Creation Story
What do you mean by "Event-Driven"?
Chapter 13 and 14 of Extreme Programming Explained
Chapter 12 of Extreme Programming Explained: Planning: Managing Scope
Should we always use TDD to design?
Chapter 11 of Extreme Programming Explained: The theory of constraints
Chapter 8 and 9 of Extreme Programming Explained
Chapter 7 of Extreme Programming Explained: Primary Practices
Chapter 5 of Extreme Programming Explained: Principles
Event-driven architectures in Elixir - Maciej Kaszubowski - ElixirConf EU 2018
Chapter 4 of Extreme Programming Explained: Values
Chapter 2 and 3 of Extreme Programming Explained
José Valim - Idioms for building distributed fault-tolerant applications with Elixir
Chapter 1 of Extreme Programming Explained: What is XP?
GenStage and Flow - José Valim (Lambda Days 2017)
Chapter 13 of Software Craftsmanship: Journeymen Developers
Chapter 12 of Software Craftsmanship: Apprentice Developers
Chapter 11 of Software Craftsmanship: Mastering the craft
Chapter 10 of Software Craftsmanship: How to become a craftsman
Chapter 9 of Software Craftsmanship: Managing craftsmen
Chapter 8 of Software Craftsmanship: Customers have a different relationship with craftsmen
GOTO 2014 • Event Sourcing • Greg Young
Chapter 7 of Software Craftsmanship: How craftsmanship affects the users of systems
Using sagas to maintain data consistency in a microservice architecture
Chapter 6 of Software Craftsmanship: Craftsmanship is the opposite of licensing
Chapter 5 of Software Craftsmanship: Putting people back into software development
Chapter 4 of Software Craftsmanship: Finding a better metaphor than software engineering
Chapter 3 of Software Craftsmanship: Understanding Software Development
SC London 2017: TDD, As If You Meant It by Alex Bolboaca
Chapter 2 of Software Craftsmanship: The Problems with Software Engineering
SC London 2017: Software Craftsmanship - 8 Years by Sandro Mancuso
Umbrella Apps-Winter is coming by Luis Ferreira at FnConf17
Chapter 1 of Software Craftsmanship: Understanding Software Engineering
Chapter 14 of Beyond Legacy Code: Learning from our Legacy
Chapter 13 of Beyond Legacy Code: Refactor Legacy Code
Developing Transactional Microservices Using Aggregates, Event Sourcing and CQRS - Part 2
Developing Transactional Microservices Using Aggregates, Event Sourcing and CQRS - Part 1
Chapter 12 of Beyond Legacy Code: Implement the Design Last
Chapter 9 of Beyond Legacy Code: Create CLEAN Code
Chapter 8 of Beyond Legacy Code: Collaborate
Chapter 7 of Beyond Legacy Code: Integrate Continuously
Chapter 6 of Beyond Legacy Code: Build in Small Batches
Chapter 5 of Beyond Legacy Code: Say What, Why, and for Whom Before How
Chapter 4 of Beyond Legacy Code: The Nine Practices
Chapter 3 of Beyond Legacy Code: New people, Smart ideas
Chapter 2 of Beyond Legacy Code: Out of the CHAOS
Chapter 1 of Beyond Legacy Code: Something's wrong
Why waterfall was a big misunderstanding from the beginning
Extreme Programming 20 years later by Kent Beck
GOTO 2016 • Software, Faster • Dan North
Managing Data in Microservices
Continuous Delivery Sounds Great But It Won’t Work Here by Jez Humble
Greg Young - A Decade of DDD, CQRS, Event Sourcing
Zombie Scrum – Symptoms, Causes and Treatment
Integration Tests are a Scam
Core Design Principles for Software Developers by Venkat Subramaniam
Chapter 5: Service Design
Chapter 4: Establishing a Foundation
Chapter 3: Designing Microservice Systems
Chapter 2: The Microservices Value Proposition
Chapter 1: The Microservices Way
Book Reading Club: "Building Microservices" - part III
Book Reading Club: "Building Microservices" - part II
Production-Ready Microservices
Book Reading Club: "Building Microservices" - part I
TDD and Software Design
How Do I Test?
Journey Two of: Decomposing the Domain
Journey One of: Exploring CQRS and Event Sourcing
Outside In TDD part III
Chapter 10 of: XP Explained 2nd Ed. - The whole XP team
Outside In TDD part II
Outside In TDD part I
Jez Humble | Continuous Delivery
How to write a repository
Chapter 8 of: XP Explained 2nd Ed. - Getting Started
Chapter 7 of: XP Explained 2nd Ed. - Primary Practices
Chapter 5 of: XP Explained 2nd Ed. - Principles
Chapter 4 of: XP Explained 2nd Ed. - Values
The Passionate Programmer
Implementing Domain-Driven Design: Event Sourcing
Implementing Domain-Driven Design: Command processors
8 Lines of Code
Chapter 3 of: Developing Reactive Microservices
Chapter 2 of: Developing Reactive Microservices
Chapter 1 of: Developing Reactive Microservices
Chapter 13 of "Programming Erlang" - Errors in Concurrent Programming
Chapter 3 of: Reactive Microservices Architecture
Chapter 1 and 2 of: Reactive Microservices Architecture
Chapter 12 of "Programming Erlang" - Concurrent Programming
Continuous Deployment with Containers
DDD Quickly: DDD Matters today: An interview with Eric Evans
Ian Cooper: TDD, where did it all go wrong
DDD Quickly: Preserving model integrity
DDD Quickly: Refactoring toward deeper insight
How to write a git commit message
DDD Quickly: The Building Blocks of a Model-Driven Design
DDD Quickly: Model-Driven Design
DDD Quickly: The ubiquitous language
DDD Quickly: What is domain-driven design
Chapter 21 of The Nature of Software Development: Scaling Agile
Chapter 20 of The Nature of Software Development: Agile Methods
Chapter 18 and 19 of The Nature of Software Development
DevOps principles for IT managers
Chapter 17 of The Nature of Software Development
Chef: Managing multiple nodes
Chapter 16 of The Nature of Software Development: Managing
Chapter 15 of The Nature of Software Development: The five card method
Practical Considerations For Microservice Architectures
Chapter 13 and 14 of The Nature of Software Development
Chapter 11 and 12 of The Nature of Software Development
Chapter 9 and 10 of The Nature of Software Development
Chapter 8 of The Nature of Software Development: Bug-Free and Well Designed
Chapter 7 of The Nature of Software Development: Building Features and Foundation in parallel
Chapter 6 of The Nature of Software Development: Building, Feature by Feature
Chapter 5 of The Nature of Software Development: Planning, Feature by Feature
Chapter 3 and 4 of The Nature of Software Development
Chapter 1 and 2 of The Nature of Software Development
Good Design is Easily-Learned
Chapter 7 of Effective Unit Testing: Testable Design
Chapter 6 of Effective Unit Testing: Trustworthiness
Chapter 5 of Effective Unit Testing: Maintainability
Chapter 4 of Effective Unit Testing: Readability
Docker Clustering on Mesos with Marathon
Chapter 3 of Effective Unit Testing: Guidelines for using test doubles
Chapter 2 of Effective Unit Testing: In search of good
Xp Simplicity Rules
Give Yourself the Gift of Sanity This Christmas
Chapter 1 of Effective Unit Testing: The promise of good tests
Chapter 12 of Building Microservices: Bringing It All Together
Chapter 11 of Building Microservices: Microservices at Scale - Scaling Databases
Chapter 8 of Building Microservices: Monitoring
Chapter 4 of Building Microservices: Integration
Docker Clustering on Mesos with Marathon
Chapter 3 of Building Microservices: How to Model Services
An Open Letter to the Erlang Beginner (or Onlooker)
Chapter 8 of "Programming Erlang" - The Rest of Sequential Erlang
Thinking like an Erlanger
Part III of Test-Driven Development by example: Mastering TDD
Part III of Test-Driven Development by example: Refactoring
Part III of Test-Driven Development by example: Design Patterns
Part III of Test-Driven Development by example: Green Bar Patterns
Improving the study path
Part III of Test-Driven Development by example: Red Bar Patterns
Part III of Test-Driven Development by example: Patterns for TDD
Spawned Shelter!
Chapter 2 of "The Software Craftsman"
How to setup docker monitoring
Analyzing Your Applications with StatsD, InfluxDB, and Grafana
Chapter 1 of "The Software Craftsman"
Metrics in Kanban and Cumulative Flow Diagrams
Chapter 7 of "Programming Erlang" - Binaries and the Bit Syntax
Part III - Chapter 25: Dependency-Breaking Techniques
How we ended up with microservices
Daily Activity Log To RSS
Part III - Chapter 25: Dependency-Breaking Techniques
Part III - Chapter 25: Dependency-Breaking Techniques
Continuous Delivery of Microservices at Netflix
Part III - Chapter 25: Dependency-Breaking Techniques
Chapter 24: We Feel Overwhelmed. It Isn't Going to Get Any Better
Continuous Delivery of Microservices at Netflix
Chapter 23: How Do I Know That I'm Not Breaking Anything?
Chapter 7 of "Programming Erlang" - Binaries and the Bit Syntax
Chapter 23: How Do I Know That I'm Not Breaking Anything?
Chapter 22: I Need to Change a Monster Method and I Can't Write Tests for It
DDD: putting the model to work
Chapter 7 of "Programming Erlang" - Binaries and the Bit Syntax
Chapter 22: I Need to Change a Monster Method and I Can't Write Tests for It
Chapter 6 of "Programming Erlang" - Error Handling in Sequential Programs
An introduction to unikernels and how to deploy an Erlang application to EC2 as a LING unikernel
Enabling a basic multiple-cursors in my emacs configuration
Microservices @ ThoughtWorks
Using spacegray-theme and enabling auto-complete in my emacs configuration
Git 2.5, including multiple worktrees and triangular workflows
Chapter 22: I Need to Change a Monster Method and I Can't Write Tests for It
Effective API testing with Cucumber
Chapter 5 of Mostly Adeguate Guide to Functional Programming
Strangler Application
Chapter 22: I Need to Change a Monster Method and I Can't Write Tests for It
Some thoughts about recruiting a passionate developer in the 21st century
Chapter 22: I Need to Change a Monster Method and I Can't Write Tests for It
Chapters 1-4 of Mostly Adeguate Guide to Functional Programming
The Most Common Reasons Why Software Projects Fail
Professor Frisby's Mostly Adeguate Guide to Functional Programming
Eric Evans JAX 2015 Keynote: DDD and Microservices: At last, some boundaries!
Chapter 6 of "Programming Erlang" - Error Handling in Sequential Programs
Just created the "Simple Board" project in Phoenix Framework
Chapter 21: I’m Changing the Same Code All Over the Place
Chapter 21: I’m Changing the Same Code All Over the Place
The Most Common Reasons Why Software Projects Fail
Chapter 20: This Class Is Too Big and I Don’t Want It to Get Any Bigger
Playing around the Phoenix Framework with a simple project
Chapter 20: This Class Is Too Big and I Don’t Want It to Get Any Bigger
Sandro Mancuso : Crafted Design
Sandro Mancuso : Crafted Design
Chapter 20: This Class Is Too Big and I Don’t Want It to Get Any Bigger
Chapter 19: My Project Is Not Object Oriented. How Do I Make Safe Changes?
Implementing the logic for a board game in Elixir - Torben Hoffmann
Doing some practice with Phoenix Framework
Chapter 18: My Test Code Is in the Way
Chapter 17: My Application Has No Structure - Telling the Story of the System
Object-Oriented Reengineering Patterns
Chapter 17: My Application Has No Structure
Chapter 16: I Don’t Understand the Code Well Enough to Change It
Practical Refactoring
Martin Fowler @ OOP2014 "Workflows of Refactoring"
Chapter 14: Dependencies on Libraries Are Killing Me - Chapter 15: My Application Is All API Calls
Anti-fragile and feedback. Trying to make up for the failures of "agile."
Phoenix Framework
Chapter 13 of "Working Effectively with Legacy Code":
- I Need to Make a Change, but I Don’t Know What Tests to Write - Characterization Tests
Chapter 5 of "Programming Erlang" - Records and Maps
Refactoring with Loops and Collection Pipelines
Postscript: Time Goes On
Chapter 13 of "Working Effectively with Legacy Code":
- I Need to Make a Change, but I Don’t Know What Tests to Write
Testing Puppet with rspec-puppet and manage module dependecies with librarian-puppet
Refactoring with Loops and Collection Pipelines
Preparing the daily-activity-log-concept github repository and a ready-to-go project to help users to start with.
Chapter 12 of "Working Effectively with Legacy Code":
- Using Effect Sketches to Find Hidden Classes
- Pinch Point Traps
Ember.js documentation
Q&A How to deal with a legacy infrastructure
Just finished to read "Kanban and Scrum - making the most of both", really enjoyed it.
If you are searching for a pratically and a smoothly introduction to Kanban,
this is the book to start with.
Composition vs. Inheritance: How to Choose?
Mob Programming Kata @ HLCS
Q&A How to deal with a legacy infrastructure
How to get started with Kanban
Kanban Pizza Game workshop
Using XML/XSLT to display my activity log
Part I of "Kanban and Scrum - making the most of both"
Part I of "Kanban and Scrum - making the most of both"
"Part II: Case study" of "Kanban and Scrum - making the most of both"
How to express action in RDF
Why RDF model is different from the XML model
Kanban Pizza Game workshop
"Part II: Case study" of "Kanban and Scrum - making the most of both"
"Part II: Case study" of "Kanban and Scrum - making the most of both"
Kanban, dall'idea alla pratica
Kanban and Scrum - making the most of both
How the process/product quality is perceived from internal to external
How to get started with Kanban and why
about a web based application that helps you to create and organize notes on a virtual desktop (like post-it)
Designing your Kanban board to map your process
XML and XSLT