If you put things in triple backticks ```, it’s formatted as a code block

Like this

I believe you can specify a language for syntax highlighting at the start of the code block.

SELECT * 
FROM passwords
WHERE storage_method = 'plaintext' 
-- TODO rename storage method to something less obvious so the IT-Sec guys get off my case

<p class="bold">Stop storing password in plain text, dammit</div>
<!-- TODO clean up the tags so the linter stops complaining -->

if (true) this.code.makeCringe(this.reader);
else 
    { 
throw new NullPointerException("Unreachable code"); }
// Why, yes, I do love creating terrible code

I don’t know what or how it guesses the language otherwise.

if (highlighting == "Python"): 
  System.out.println("Wait, that's not a Python command");
  std::cout << "Also not Python"
  print("This one is")

CASE highlighting 
  WHEN 'SQL' THEN 'I dont know any dialect-specific ways to check which one this is'
  WHEN 'sql' THEN 'Apparently its case-sensitive' 
  ELSE 'No clue' 
END 

(concatenate 'string "I can't be arsed to try everything I know" "So this will have to do")

Nah, there was another contender, but they were a fuckin’ nerd with big, scary words and headachy sentences and got bullied out of the race.

(The nerd is a general analogy to reasonable people, not any specific person or group)

Or the server move

The only cats I’ve got are con-cats, unfortunately, but they do put things in a row.

I’d love to work more with animals - pythons, anacondas, pandas, cats… Alas, I am stuck with SQL and Power BI, for better or for worse.

Data Analyst: So what do you want to measure? What question do you want to answer?
Customer: Can you do a column chart, where I can see how many Orders we have?
Data Analyst: Column chart? What’s the Axis? Per day?
Customer: No, per month.
Data Analyst: Right, so new Orders per month?
Customer: No, how many we have in general, new and old.
Data Analyst: Do you mean the old ones still open at the start of the month?
Customer: That’s a good idea, yeah. Actually, can you add the ones we complete in that month too?
Data Analyst: The amount of completed orders? That would double-count them.

*shared moment of confusion*

Customer: Don’t make it so complicated, I just want to see how many orders we had.
Data Analyst: Let me ask again, what question do you want to answer?
Customer: I want to know how much our teams are working.
Data Analyst: As in, how many orders they’re completing?
Customer: I also want to see if we need more people.
Data Analyst: Like, if they can’t complete all their orders? So basically, the rate of completed versus new ones?
Customer: Ooooh, good idea, can you put that rate as a line over our chart of new, old and completed orders?

Customer: Oh, and the warranty returns too! They need to be processed as well, that’s also work.

Customer: Actually, we have this task tracking for who does which work for the order or warranty return.
Data Analyst: Shouldn’t we use that to track how much work the teams are doing?
Customer: Yes, put it in the chart too.

Epilogue: The Customer got a separate chart for the tasks - turns out I’m not charging by the chart, so you don’t need to cram as much as possible into a single chart. They also were persuaded to stick with “Old” and “New” to show the total workload, with the “Old” bars providing an indicator for how much stayed open and whether the backlog was growing.

ActiveSheet? Please no

I’m in a superposition of knowledgeable and ignorant until you ask me something, in which case I produce either a good or a stupid answer, depending on various random factors such as whether I’m versed in the general topic, happen to know the specific subject of the question or just get lucky with guessing.

(This analogy breaks apart if you consider the possibility of giving a mediocre answer that’s neither accurate nor entirely stupid, which probably makes it the perfect self-defeating counterexample)