Links from 2015

TL;DR: Links I tweeted during 2015

It's funny how old principles are still useful today. In 2015, the most important ones I've learned are the following:

• Command/Query Responsibility Segregation (CQRS): separate the "read" logic from the "write" logic
• Event Sourcing (ES): recording every action done for analytics and rollback purpose
• Command Bus: store and validate input in a Command object, pass it to a Command Bus middleware that will find and execute the appropriate Command Handler which will execture the logic
• Framework / Library agnosticism: decouple from vendors to be able to change/upgrade them without friction
• microservices: reduce the scope of an API, organize them into a communicating network
• Monolithic Repository: store related applications in the same git repository

It was a year full of links, so here they are!

Articles Highlight

• Using logs to build a solid data infrastructure, or why dual writes are a bad idea
• Targeting broad queries in search

Tools Highlight

• Puli:
  • 1.0-beta release
  • Slides: Pulis, PHP next package revolution
  • Resource discovery
  • Managing web resources
• Refactoring Browser:
  • Refactoring Rubicon
  • Qafoo PHP RefactoringBrowser
• Humbug:
  • Code Coverage lies, toward mutation testing
  • Introduction to Humbug, a mutation testing framework for PHP
  • Probing test suite quality with mutation testing
• Tactician, the PHP Command Bus:
  • A wave of Command Buses
  • Responsibilities of the Command Bus
  • From Commands to Events
  • Command Bus FAQ
  • Collecting events and the EventsAware Command Bus
  • Messaging Flavours
  • Form Command model validation
  • CQRS vs CRUD performances and scalability
• The log file navigator
• UUID:
  • auto incrementing to destruction
  • Why auto incrementing is a terrible idea
• Pomm:
  • Pomm 2.0 is out
  • A short focus on Pomm Foundation

Interesting Talks

• Monolithic Repository:
  • Monolithic Repository
  • How to manage multiple Composer packages within a single respository
  • see also article: Managing monolith repositories with composers path repository
• Doctrine:
  • Doctrine: to use or not to use
  • Doctrine ORM optimization hydration
• PHP Interoperability:
  • PHP FIG, the PSRs you do not know about
  • PSR 0 to 12
  • The PHP Interoperability Framework
• Desgin:
  • Why your test suite sucks
  • Embracing change
  • Driving design through examples
  • Brownfield Domain Driven Desgin
  • The quest for global design principles
  • Hexagonal architecture, message oriented software design
  • CQRS and Event Sourcing
• Symfony killed me
• Logs hunting
• Scaling Symofny apps with RabbitMq
• Breaking boundaries with FastCGI Symfony
• in french: Monitorer sa prod

Tests:

• Test Driven Desing (TDD):
  • Does TDD lead to good design?
  • TDD and complexity
• Economy of tests
• Your test suite is useless
• Specs VS Tests
• Just say no to more end to end tests
• Testing is not a choice
• Coupling tests
• Open letter from an ignored test
• Single source of truth
• Introducing BDD
• Eradicating Non-Determinism in Tests

PHP Interoperability

• PSR 7:
  • On HTTP middleware and PSR 7
  • PSR 7 by example
  • PSR 7 and the future of PHP
  • PSR 7 issues
  • PSR 7 support in Symfony is here
  • Using PSR 7 in Symfony
  • HTTP client for SDKs
• PSR 7 Container Interop = cross framework module system
• PSR 11 use cases
• PSR 11, performance impact of the delegate look-up feature
• PHP Security PSR 9 and 10
• PSR-What? Shared Standards for a Bright Future

Pet projects

• Redaktilo 1.7
• Stack middleware to rollback database transactions
• Memio:
  • its origin
  • SpecGen
• Symfony Micro Framework:
  • Symfony Empty Edition
  • MicroFrameworkBundle

Design Patterns

• The Repository pattern
• DTO vs Value Object vs POCO
• Decoupling architecture and domain with repositories
• Repositories On Top UnitOfWork Are Not a Good Idea

microservice

• Microservice Premium
• Monolith First
• Don't start with a monolith
• Is REST best microservices
• Microservices trade offs
• You're not going to do microservices

Refactoring

• Refactoring external service
• Refactoring the cat API client:
  • part 1
  • part 2
  • part 3

Keep it Simple

• Simplicity before generality, use before reuse
• Thoughts on design of APIs
• DRY is about knowledge

OOP

• Composition VS inheritance, how to choose
• The meaning of Object Oriented Programming

Git

• The beginners guide to rebasing your PR
• The magical and not harmful rebase
• Git's interractive patch mode
• Git disciplined
• Utter Disregard for Git Commit History

Security

• A few things about Redis security
• The Web Authentication Arms Race – A Tale of Two Security Experts
• Secure authentication PHP with long term persistence

PostgreSQL

• What PostgreSQL has over other Open Source SQL databases:
  • part 1
  • part 2
• A better ID generator for PostgreSQL
• Faster JSON generation with PostgreSQL
• Goodbye MongoDB, hello PostgreSQL

REST

• RESTful considered harmful
• Best practices for a pragmatic RESTful API

Performance

• 5 Doctrine ORM performance traps you should avoid
• Essential macro optimizations to improve PHP performance
• 5 ways to optimize Symfony baseline performance
• PHP high performance
• Intproducting PHP FastCGI
• Why is uniqid slow?

Agile

• Transform your stand up
• They won't be interrested
• Does organization matter
• Modern extreme programming
• If pragmatism raises technical debt, call it over simplification
• Don't blindly follow
• The role of a senior developer
• The failure of agile
• Heisenberg developers

DDD

• To DDD or not to DDD, what to do if your domain is boring
• DDD revisited
• Why CRUD might be what they want but not what they need

Symfony

• Do not use FOSUserBundle
• Re-thinking event listeners
• Tagging Symfony services
• Symfony from scratch
• Structuring my application
• Your package dependencies

Misc

• Do not learn frameworks, lean the architecture
• Let the magic die
• Naming is hard, or is it?
• Setter anxiety
• Doing terrible things to your code
• Programming sucks
• Switching to generators
• ORMs under the hood
• Hexagonal
• Burnout
• Formatting exception messages
• Approaching coding style rationally
• Pipelines, imutability and privates