- 🔭 I’m currently working @Voxel
- 🔙 Just to work @codurance
- 👯 I’m looking to collaborate on communities and open-source projects
- 🤝 I’m looking for help with communities
- 🌱 I’m currently learning best practices
- 💬 Ask me about Software design principles, Test-Driven Development, Pair/Ensemble programming, Trunk-base development, Slicing, Continuous Integration, Continuous Delivery, Feature Flags, Mutant Testing, DDD, CQRS
- 📚️ You could find my research with @marabesi about Common Patterns that make TDD harder: An essay from practitioners
If you want to know more about me you could find me at me website
| TDD Anti-Patterns with @marabesi | Improving your life with Extreme Programming | Re-aprendiendo Orientación a objetos, esta vez, bien with @antonio_gg_dev | Test-Driven Development, ¿cómo pasar de las katas a un proyecto real? |
|---|---|---|---|
 |
 |
 |
 |
- Test-Driven Development "styles" Classicist (Detroit/Chicago) vs Outside-in (London)
- Outside-in: technics Pivote and Drill-down
- Discovering Peers with GOOS Techniques
- In depth view to Peers, Internals collaborators
- The Gold-Plater or Over-Engineer
- The Toxic Critic or “No-but” Engineer
- The Martyr or Over-Committer
- The Ivory Tower Architect
- The Knowledge Kidnapper or Silo Builder
- The Micromanager or Puppet Master
- The Cowboy Coder or Lone Wolf
- The Hero / Rockstar / “10× Developer”
- From “Ivory Tower Architect” to Staff & Principal Engineer
- Mockist TDD: Just enough design
- 🧠 Motivation doesn’t live in a dashboard
- CRC cards: Class, Responsibility, Collaborator cards
- Test-Driven Development the basics
- Exploring Testing Strategies: Past, Present, and Future
- 🧯 Never the expert: breaking knowledge silos and bottlenecks in technical teams
- ❌ ÑaaS: when patches become a product
