To add to what the admin said, the software this site runs on, PostMill, will on some future date probably have more options for adding images to themes and shit.

EDIT: ok the author stopped development of PostMill so that's not going to happen.

they shall be memorialized in commits

I feel like this is, again, some Uncle Bob bullshit. Seriously, fuck that sexist prick. He has this schtick about how TDD is all and other techniques to improve reliability and reduce errors are bullshit. Like I would be much more congenial to the attitude if it implied things like (choose your own picks):

1. programming by contract
2. property based testing
3. fuzzers
4. unit testing
5. integration testing
6. good method documentation, perhaps with (an) example(s)
7. literate programming
8. code review
9. formal specs
10. some nicer type system
11. pair programming
12. safer languages - if there are no segfaults, you don't need to advertise the risk of one
13. Have some people dedicated on hammering your software in evil manners
14. proofs (but that's avant garde tbh)
15. stats on commits/bugs per product, project, package, module, file, method/function. If something gets a lot of work done, unleash the testers.
16. Outsourcing to Donald Knuth

I think it's the case usually that this comment hater has one or three favorite techniques they like and thus disregard the rest of the universe and I bet they don't even have TAOCP on their book shelf.

run, it was a super raccoon

It has this cute logic of "excess comments indicate poor quality" and also this hidden thing where you don't need to write comments that you find boring to write anyway but now you have a virtuous reason not to.

If I was an instructor on some software course, I'd make an online assignment to come up with 5 excuses for not writing documentation and share the best answers with the class afterwards.

Class invariants are imo cool and underappreciated part of OOP. It's also my belief, untainted by any real research though, that designing, verifying and testing them would kill lots of bugs.

tbh I do want to admit contemporary academic success measured by metrics isn't, like, the way to decide these things since phrenology also had its heyday once. I haven't been reading Chomsky since I was like 14 so I can't judge him adequately but I'm also somewhat disinterested in him so yeah.

Houllie d'Hoppée, Duchess of Mêmes

"I don't write comments because comments and code drift apart."

"See the unit tests if you really want to figure out how it works."

"I'll document it later now that I got it working and it made it into the API."

"I'll lock down this method's name before writing its documentation."

"Contracts? Code is law."

"We use test driven development here so we don't need dedicated testers."

"The language I use doesn't support checking class invariants well so I just ignore them."

"It was clear enough for Torvalds."

"Commit it now, compile it later."

"I don't write documentation for functions besides types, since types are compiler verified and they are plenty good anyway. Everybody gets these things just like me."

Chomsky is like the second most cited person ever after Plato though.

Hey I can post lots of stuff like this, just give a day! The Algorithm led me upon plenty of this stuff that sound similar and are also moe branded, for some reason. I suppose YouTubers collectively decided at some point that this is what moe girls sound like...

I love this so much

I literally thought of Ableton but I haven't ever used it actually. I was just thinking about what might be commonly enough used software that could spread that exact clap so widely.

Warning: extremely moe (I suppose): It's this clap. In the context it sounds somewhat unenthusiastic even, like it was tired salaryman asked to pretend to be enthusiastic after a 80 hour work week.

bring it on

nah I only asked how Hswap relates to Hstuck, that's way simpler, isn't it?