News for hackers. Stuff that matters.

A comment on Narbacular Drop Technical Design Document [pdf].

Re:Narbacular Drop Technical Design Document [pdf] by asdfasdf on Wednesday July 06, 2016 @05:26PM (#12045998)
Coding guidelines

- Precompute whenever even remotely possible.

- Measures must be taken to prevent copy paste errors.

- Measures must be taken to prevent copy paste errors.

- The STL is evil (most of the time).

- Unnecessarily virtual functions should be rewritten to remove virtual requirements.

- Sloppy code must be marked for recoding later.

- Unreadable code earns you a free punch in the face.

- Measures must be taken to prevent copy paste errors.

[ Parent | on HN ]
Re:Narbacular Drop Technical Design Document [pdf] by rbanffy on Thursday July 07, 2016 @03:00AM (#12047880)
"Checkouts can be performed at will (network permitting), but all code checked into the primary code branch MUST compile. Anyone caught checking-in uncompilable code will be tarred and feathered."
[ Parent | on HN ]