|
|
|
|
|
by forensic
4956 days ago
|
|
Since this book will likely be unscientific conjecture backed up by an amateur conception of psychology and physiology, I hope you will detail as many case studies as possible to allow readers access to the data on which you are theorizing. Providing as much raw data as possible will greatly increase the value of the book. It could actually be picked up by academics who study these issues. When programmers attempt to study their own physiology and psychology, they are leaving their area of expertise. Most blog posts that try to address programmer productivity are tragically uninformed (and just as often contain egregious analytical errors). It's a very interesting topic and programmers have a lot of data to provide. |
|
One could take a sample of GitHub projects and commit times. You would have to find out the contributors' time zones, and adjust accordingly.
You need to balance the hobby contributors against corporate contributors i.e. those being paid to contribute.
If you wanted to make things really interesting, you could try and gauge code quality based on time. Perhaps trying to assign bugs against the commit they appeared in.