one time like five years ago i read an article that was like “we shouldn't use red and green for diffs we should use yellow and blue” and i still think about that and believe in it y'all

i think the argument was something along the lines that red/green implies that the old code was Bad and the new code is Good, which makes it hard to spot regressions or mistakes and adds bias, and that actually we should just mark the old code as Old and the new code as New because that's actually what the diff is supposed to signify lol

wikipedia does this in their diffs btw, probably for this reason

i'm pretty sure this article was also like "give code comments the most natural and easy-to-read and pleasing colour so that people will write a lot of them" and yeah colour schemes which make comments just fade into the background (or which make them jarring and ugly) aren't my style

i was assigning colours to github issues today and that's what got me thinking of this

programming take 

programmers: but kibi if the *comments* stand out then how am i supposed to read the *code*

me: no, but see, the code isn't *for* you, the code for the *computers*

programmers: ………

programmers: [ERROR: UNPROCESSABLE ENTITY. Retrying…]

programmers: but kibi if the *comments* stand out then how am i supposed to read the *code*

Follow

programming take 

@kibi I've always admired a line from SICP, that says something like "programs should be written for humans first, computers second"

and often this does mean just explaining everything with comments

Sign in to participate in the conversation
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!