4 ms·
I use this one from "How To Write Unmaintainable Code". /* /* Procedure Name: /* /* Original procedure name: /* /* Author: /* /* Date of creation: /*
by ransom1538 5y ago
I use this one from "How To Write Unmaintainable Code".
/*
/* Procedure Name:
/*
/* Original procedure name:
/*
/* Author:
/*
/* Date of creation:
/*
/* Dates of modification:
/*
/* Modification authors:
/*
/* Original file name:
/*
/* Purpose:
/*
/* Intent:
/*
/* Designation:
/*
/* Classes used:
/*
/* Constants:
/*
/* Local variables:
/*
/* Parameters:
/*
/* Date of creation:
/*
/* Purpose:
*
/
- marginalia_nu 5y agoYou should just fill out a TPS report instead.
- mns 5y agoI'm reading the comments here and thinking I'm some outdated greybeard. Do people actually spend more time now trying to write commit messages than doing actual work? I would never put any of my teams to do something like this, do actual developers LIKE spending more time to actually write these messages? Is code today so hard to understand and read (what about comments) that you need these things for reviews?