Words of wisdom

Hahaha, this is why it's best to have multiple programmers working on multiple projects at one time. A many-to-many relationship is quite efficient if it comes to number per amount of time. I won't elaborate on the child bearing example.

This just makes me think of how efficient it would be to have a pool of programmers and a pool of tasks that have to be done and then let them sort themselves out. I reckon the programmers would eventually get bored and either work on the tasks or start side projects that would be quite profitable or make the work more efficient. Hmmm...

When my manager was thinking about adding recources to a delayed project, which would have made things even worse, I seriously told him "what one dev can do in one month, two devs can do in two months".