Is It Orthogonal Enough?

// Coding Best Practices: // One of the key concepts of quality code is orthogonality // Me: // Is it orthogonal enough? /***/***/***/***/***/***/***/***/***/***/ /***/***/***/***/***/***/***/***/***/***/ /***/ /**/ /**/ console.log(... /**/ /**/ $$=>$=> (~~-~$&&$$ /**/ /**/ (~=>$),(_$➞$=_>$ /**/ /**/ (_[~$=_??=$?_$ /**/ /**/ (~_$)_)(_)))))_( /**/ /**/ ==[]+~_+~_+~_+_ /**/ /**/ /**/ /***/***/***/***/***/***/***/***/***/***/ /***/***/***/***/***/***/***/***/***/***/ DEBUG CONSOLE /usr/local/bin/node ./orthogonal.js 2 3 5 7 11 13 17 19 23 29 31 37 41 43 47 53 59 61 67 71 73 79 83 89 97

A dark-themed code editor shows a comment about coding best practices and orthogonality, followed by deliberately bizarre JavaScript full of symbols. The debug console runs orthogonal.js and prints prime numbers, making the joke that the code is technically orthogonal or functional but absurdly unreadable and overcomplicated. People send this as a reaction to chaotic code, excessive cleverness, or questionable programming style.

• @dev_meme / 5131 2023-04-17
• @gentoomemes / 3969 2023-04-17