@fribbledom Hear, hear. From our coding best practices:
== Write code for other people.
Modern toolchains are pretty darned good at generating fast, compact binaries if you write semantically-clear code with a clear design.
@fribbledom Hear, hear. From our coding best practices:
== Write code for other people.
Modern toolchains are pretty darned good at generating fast, compact binaries if you write semantically-clear code with a clear design.
Please consider writing your hashtags in upper camelcase so screen readers have a chance at figuring them out.
#whyistayonmastodon sounds like an giant undecipherable mess of sounds.
#WhyIStayOnMastodon reads out "Why I Stay On Mastodon" 😄
(Reason #44 I stay here: my previous requests like this have been generally well-received, proving that most people are awesome.)
@jartigag Our big-picture number is just person-days. Since we track those it's easy enough to ask "how many person-days went into the control software for X?", etc.
It is poorly-correlated to SLOC. For hard problems you spend so much time researching only to produce like 50 SLOC. Easy problems like "implement this state machine" is a lot of very-nearly-boilerplate.
(I actually care far more about the distribution of completion time compared to the work estimate range!)
bicycling programmer in mostly #embedded #c & #cpp in off-grid #solar; into road, tour, gravel #bike fun; #linux, #python, etc.; #hiking, #books, #machining, #community building, you name it. southwestern Virginia, USA.
Bobinas P4G is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Bobinas P4G content and data are available under the Creative Commons Attribution 3.0 license.