This guy should rush to write documentation first...He will probably "build to budget" exhausting money and his time in coding.
If he does so and finishes his project with a burnout there is a huge interrogation on how production people will be able to fix without a good knowledge of the design during the recovery time (burnin =~ burnout time).
Read the source luke is nice. But 10 pages in natural languages speaks louder than 10K lines of codes even with comments.
I dislike these kind of coders that goes for the beef and despise the grunt works like not for them.
Documentation should come first. This code will have to be maintained since he -like a good drug dealer- is trying to hook people to use his code.
If he does so and finishes his project with a burnout there is a huge interrogation on how production people will be able to fix without a good knowledge of the design during the recovery time (burnin =~ burnout time).
Read the source luke is nice. But 10 pages in natural languages speaks louder than 10K lines of codes even with comments.
I dislike these kind of coders that goes for the beef and despise the grunt works like not for them.
Documentation should come first. This code will have to be maintained since he -like a good drug dealer- is trying to hook people to use his code.