Gregory's ServerDeveloper accused of unreadable code refuses to comment
 30 comments
  @GhostOnTheHalfShell @Natasha_Jay itβs twice as hard to debug as to write (Ritchie?) - so never debug it :) @Natasha_Jay Though there's a lot of unreadable code that would remain unreadable even with all the comments in the world :meow_dizzy: ( Yes, I got the joke too :meow_eyespin: )   @Natasha_Jay@tech.lgbt it took me 6 tries to read this. i need to sleep now. it was a long day.  @osma @Natasha_Jay So the PR firm had no comment at this time. Likely that's their job. π @Natasha_Jay I have interacted with this toot in all ways possible at it's still not enough π   @Natasha_Jay want a comment? here
*opens vim* *types* ggI/*<esc>GA*/<esc>:wq (this will comment the entire file)  Curse you... and take my up vote! ;-)  @Natasha_Jay We haven't been able to get in contact with programmer writing unreachable code
@Natasha_Jay sometimes it's almost unreadable, and you wish it was totally unreadable, because there's not enough mind bleach to erase from your memory. Totally! I remember a developer who'd built something in SQL in a single statement with six-seven levels of nesting and inner joins and god knows (I could hardly work it out and I was an ex-dev and had written that functional spec. It worked sure, but was insane, warped, and unmaintainable) I pointed it out to the Dev Team Manager who I knew very well and it was rewritten later on ...  |
@Natasha_Jay puntastic!