(Thanks, I dig your game)

Check out the username.

All this stuff about source and destination and target or whatever hasn’t helped me because those terms are too confusing when it comes to what they do with links. I like to think of it as hitching a new car onto a train. ln is the locomotive, the car that’s already there comes next, and then you link the new one to it.

Yep, definitely better than pooping back out the mouth.

How big are the glove boxes/how tiny are the women over there?

How often are you reinstalling your OS? Maybe that’s where your frustration should go.

solving puzzle after puzzle

That about sums it up for me. Figuring something out lets out the good brain chems. The opposite sucks, though, getting stuck on something, especially when it’s something small that I was just too tunnel visioned to see.

I inherited ansible that always used maps instead of lists and it drove me up the wall. Still untangling that.

The deer is responsible. Safety first.

Octopus lovers: taking the k out of kink.

Can they each appeal and claim they were charged for the crimes of another man with the same name, at least for the ones that match?

Why did he put it back in the lunchbox?

You want an award? I hate working with JSON without a prettier.

A few weeks? How do you stay employed? How do you even feed yourself at that pace? Blocked on making a sandwich, I’ve got the wrong type of bread.

It’s three lines in an editor config file to standardize the indents across any editor: https://editorconfig.org/

In vscode, adding two extensions is all I need:, yamllint (if you don’t use linters, I don’t know how you do your job in any language) and rainbow indents. Atom had similar ones. I’m sure all IDEs are capable of these things. If you work at a place that forces you to use a specific editor and limits the way you can use it, that’s not YAML’s fault.

At a certain point, it’s your deficiencies that make a language difficult, not the language’s. Don’t blame your hammer when you haven’t heated the iron.

So it’s easy to enforce locally but you don’t have to. And it’s easy to see indentation on modern IDEs and you can even make your indents rainbows and collapse structures to make it easier to see what’s going on, but I guess since some people want to write it in vi without ALE or a barebones text editor, it’s bad? Like there are legit reasons it’s bad, and other people have mentioned them throughout the thread, but this seems like a pretty easy thing to deal with. I work with ansible a bunch and YAML rarely is where my problem is.

YAML mixes 2 and 4 spaces

I think that’s a user thing and it doesn’t happen if you have a linter enforce 2 or 4.

That’s why there’s the JADE acronym. You never justify, argue, defend, or explain. That makes them think there’s a chance if they just counter every single thing you say.

I want onion rings now, but those aren’t allowed in c/nottheonionrings

Please don’t.

But I just moved to opensearch.