Productivity in software engineering can be helped by writing down what you have to do. Agile buzzwords-free post.

Some links to writings that once read will change a bit of your life for the better. Not developers-only.

Maybe unit tests for dynamic languages have to do what static language compilers already perform. But there are drawbacks like simple delegation...

What is a good domain model? The one that bridges together domain and infrastructure...

It's hard to get work done when you're not in the zone, and distraction comes in. To help productivity, let's enforce good practices instead.

Why using a factory to produce simple objects? Because new keyword has to be isolated, even if it is only new Form();

PHPUnit is a wonderful tool, but this time it was being a bit too smart. Here's a workaround to fix its mocking capabilities.

Have you ever tried to test a private or protected method? Every time a test invokes a private method by reflection a fairy dies. Be more responsible.

Systems grows and also classes do, but we should respect the Single Responsibility Principle. Rule of thumb for noticing potentially God classes.

Doctrine is growing and the 2.x branch will support persistence ignorance for domain classes. But to start doing some Domain-Driven Design more metadata is needed.

Unit testing can be more effective of integration one because it find defects on the single parts. But also single parts, a la unix way of life, can be more effective of a whole.

The writing activity will move on another website.