Conversation

Notices

1. Embed this notice
   Rusty Crab (rustycrab@clubcyberia.co)'s status on Sunday, 22-Sep-2024 02:45:53 JST Rusty Crab
   "the code is the documentation" is one of those phrases that we tell programming novices to say on purpose so we can easily tell who has never done real engineering in their entire life
   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Sunday, 22-Sep-2024 02:45:52 JST 翠星石

     in reply to
     @RustyCrab The GNU C should be so expertly handcrafted that it can be the documentation, but you should add some texinfo documentation too.
   • Embed this notice
     The MILF Messiah (lunarised@whinge.town)'s status on Sunday, 22-Sep-2024 07:36:37 JST The MILF Messiah

     in reply to

     • pettanko
     • Johnny Peligro, now on Mitra!
     @RustyCrab @mischievoustomato @pettanko hard disagree. I've worked on complex DSP solutions with over 40 MILLION lines and there was no documentation. The most you got were block comments on specific routines. Well names variables and good consistent style and a modern ide really is good enough
   • Embed this notice
     Rusty Crab (rustycrab@clubcyberia.co)'s status on Sunday, 22-Sep-2024 07:36:38 JST Rusty Crab

     in reply to

     • pettanko
     • Johnny Peligro, now on Mitra!
     @pettanko @mischievoustomato self documenting code does not exist. The best you can do is really clear variable names.
   • Embed this notice
     pettanko (pettanko@varishangout.net)'s status on Sunday, 22-Sep-2024 07:36:39 JST pettanko

     in reply to

     • Johnny Peligro, now on Mitra!
     @mischievoustomato @RustyCrab I've always heard that as one of the reasons for self-documenting code.
   • Embed this notice
     Johnny Peligro, now on Mitra! (mischievoustomato@mitra.taihou.website)'s status on Sunday, 22-Sep-2024 07:36:40 JST Johnny Peligro, now on Mitra!

     in reply to

     @RustyCrab lmfao. not even comments are that reliable if you forget or get lazy when updating them