Conversation

Notices

1. Embed this notice
   V4N4D1S (v4n4d1s@mastodon.social)'s status on Thursday, 01-Feb-2024 04:14:35 JST V4N4D1S

   Oh no.

   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     13 barn owls in a trenchcoat (hauntedowlbear@eldritch.cafe)'s status on Thursday, 01-Feb-2024 04:14:35 JST 13 barn owls in a trenchcoat

     in reply to

     @V4N4D1S great, I absolutely needed to get rickrolled by a code comment

   • Embed this notice
     2xfo (rndanger@infosec.exchange)'s status on Thursday, 01-Feb-2024 05:19:11 JST 2xfo

     in reply to

     • Christoph Petrausch

     @hikhvar @V4N4D1S
     "Hey fam, I'm here to show you how to edit a text file. Now before we begin, we need to know a little bit about what we're doing. A text file is a series of bits stored in sequence that a machine can read..."

   • Embed this notice
     Christoph Petrausch (hikhvar@norden.social)'s status on Thursday, 01-Feb-2024 05:19:12 JST Christoph Petrausch

     in reply to

     @V4N4D1S let's replace readme.md with a 20 minute video.

     esmevane, sorry repeated this.
   • Embed this notice
     Pleroma-tan (kirby@lab.nyanide.com)'s status on Thursday, 01-Feb-2024 23:41:07 JST Pleroma-tan

     in reply to
     @V4N4D1S i feel like there'd be some.... moderately bad security problems from something like this being introduced into some popular code editors
   • Embed this notice
     Dag Ågren ↙︎↙︎↙︎ (waha_06x36@mastodon.social)'s status on Saturday, 03-Feb-2024 00:41:10 JST Dag Ågren ↙︎↙︎↙︎

     in reply to

     @V4N4D1S Don't get me started on how it is 20 fucking 24 and we still can NOT, under ANY CIRCUMSTANCES, put a PICTURE in a code comment.

     Because clearly no code has ever needed a DIAGRAM to explain it. That would be utterly useless. Besides, it's not like computers could handle it.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 03-Feb-2024 00:41:10 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Dag Ågren ↙︎↙︎↙︎
     @WAHa_06x36 @V4N4D1S I'd say if your code needs an /inline/ diagram to explain it, your code is likely unreadable and so must be rewritten.
     
     Documentation of the public API (which this one isn't) on the other hand could, which JavaDoc and similar ones tend to allow via rich-text/hypertext formatting.
   • Embed this notice
     Dag Ågren ↙︎↙︎↙︎ (waha_06x36@mastodon.social)'s status on Saturday, 03-Feb-2024 00:50:39 JST Dag Ågren ↙︎↙︎↙︎

     in reply to

     • Haelwenn /элвэн/ :triskell:

     @lanodan Well, let me tell you from plentiful personal experience, that is incorrect.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 03-Feb-2024 00:50:39 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Dag Ågren ↙︎↙︎↙︎
     @WAHa_06x36 Meanwhile the only time I had to document that much was because people reading it couldn't actually read code (And not as in they sometimes need a bit of help, which is fine, but as in doesn't even gets things like string vs. integer vs. float).