Comparing to another activity is useful if it helps you formulate questions, it's dangerous when you use it to justify answers.

I can only think of so many good ideas in a week. Having other people contribute makes my life easier.

Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.

One of the things I've been trying to do is look for simpler or rules underpinning good or bad design. I think one of the most valuable rules is avoid duplication. "Once and only once" is the Extreme Programming phrase.

Comprehensiveness is the enemy of comprehensibility.

Never in the annals of software engineering was so much owed by so many to so few lines of code

If you're afraid to change something it is clearly poorly designed.