Jesus

No, in my experience velocity always goes down and to the right while burn down goes up and to the right

Can’t add gifs to messages anymore, texting my wife is a lot more boring now

DHH is a driver for JOTA in LMP2, he was originally a gentleman driver in pro-am like your typical rich tech guy

Typical DHH bullshit. He likes to be contrarian but he never actually follows through.

He’s a little bitch and both Ruby on Rails and the world endurance championship would be better off without him.

Yeah, :wq! Hits a lot harder than a Ctrl+x and Ctrl+o

Tell me you didn’t read the blog without telling me you didn’t read the blog…

Not sure I can get behind this one. This is a quote from the write up you linked and while I agree these comments are dumb, a “don’t use this because our font won’t support it or a no it’s the editors that are wrong and should change” approach feel ridiculous.

Sometimes programmers rely on the monospaced grid to create a second column of values or comments on the right side of the page. It’s true, these secondary columns won’t align in a proportionally spaced font. But why are we making these columns in the first place? Even in a monospaced font they can be finnicky and hard to maintain. In virtually every other form of typography, the responsibility of alignment is given to the typesetting application, not the font. If source code editors can highlight syntax, they could also interpret tabs and syntax to create true, adjustable columns of text.