PypeBros on Nostr: nprofile1q…xjvvf the reason mentioned by my colleague who insisted to work so is ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqqw9huvn8gh2svc3r7vlc9qcwy2l8rg0yxfzht4pd5e0z4s9j3jtqhxjvvf (nprofile…jvvf) the reason mentioned by my colleague who insisted to work so is the following: those comments won't evolve the same way code does, and sooner or later, they will become wrong with no possible way to catch it (through testing)
The potential better solution is typically documented in a task in phabricator and a `// FIXME: {phabricator task number} could be improved` is all we allow ourselves in the codebase.
I cannot tell yet whether this is the right approach, but it works for them.
The potential better solution is typically documented in a task in phabricator and a `// FIXME: {phabricator task number} could be improved` is all we allow ourselves in the codebase.
I cannot tell yet whether this is the right approach, but it works for them.