Kalle Hallden Explaining Why People Shouldn't Write Code
If instead you generate your code automatically then everything goes better. How do you do that? With a program that automatically generates automatic code generator programs, of course. See Genesis.
At 4 minutes 42 seconds this process of code review is interesting! Here is an example of what used to be called a Design Change Order, at IBM in the eighties, but it was written under difficult circumstances, and would not have passed the review process. See Shadow TCP stacks in OpenBSD, it nevertheless gives an idea of the level at which a review could be done before even one line of code has been written. At this stage the design change review committee, made up of programmers and peers, would been able to point out errors or admissions, and suggest improvements, debugging strategies, etc. A design change like this would have typically taken several iterations of the review process before being authorised to proceed to the coding, unit test and integration phases. I have no idea whether this was feasible, because I never received feedback on it from anyone.
At 4 minutes 42 seconds this process of code review is interesting! Here is an example of what used to be called a Design Change Order, at IBM in the eighties, but it was written under difficult circumstances, and would not have passed the review process. See Shadow TCP stacks in OpenBSD, it nevertheless gives an idea of the level at which a review could be done before even one line of code has been written. At this stage the design change review committee, made up of programmers and peers, would been able to point out errors or admissions, and suggest improvements, debugging strategies, etc. A design change like this would have typically taken several iterations of the review process before being authorised to proceed to the coding, unit test and integration phases. I have no idea whether this was feasible, because I never received feedback on it from anyone.
Comments
Post a Comment