Conversation

Notices

1. muesli (fribbledom@mastodon.social)'s status on Tuesday, 25-Jan-2022 21:01:24 UTC muesli

   Don't write as little code as needed, write as much code as required to make it readable and understandable.

   • Jon Dubovsky (jond@mastodon.social)'s status on Tuesday, 25-Jan-2022 21:12:11 UTC Jon Dubovsky

     in reply to

     • muesli

     @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.

   • Cyastis (cyastis@mastodon.social)'s status on Tuesday, 25-Jan-2022 21:39:09 UTC Cyastis

     in reply to

     • muesli

     @fribbledom With that said, it's best practice to prefer self documented code over heavily commented code. So, write code correctly from the first place. A million lines of comments with no discriptive variable names won't save you from confusion.

   • Marcel Gagne (wftl@mastodon.social)'s status on Tuesday, 25-Jan-2022 21:54:30 UTC Marcel Gagne

     in reply to

     • muesli

     @fribbledom Hmmmph! Next thing you're going to tell us is that we should document our code.

   • Ripp (ripp_@mastodon.social)'s status on Tuesday, 25-Jan-2022 22:04:46 UTC Ripp

     in reply to

     • muesli

     @fribbledom oof aint that true, I wrote code last week and am already regretting how little I wrote

   • Dissy (dissy614@mastodon.social)'s status on Tuesday, 25-Jan-2022 22:12:01 UTC Dissy

     in reply to

     • muesli

     @fribbledom
     ++++++++[>++++[>++>+++>+++>+<<<<-]>+>+>->>+[<]<-]>>.>---.+++++++..+++.>>.<-.<.+++.------.--------.>>+.>++.
     😛