If it's all gobbledygook to you, then you weren't the target audience.

Most developers are writing for developers who have approximately the same skill level and knowledge. The vast majority of tutorials out there are definitely not aimed at beginners. They're aimed at peers who know most of the same stuff, but want to broaden their horizons a little.

Now, if it were 95% easy to follow, and then there was one step that was only a few words long and made no sense at all, that would be the typical badly written tutorial. There are way too many tutorials that have a "rest of the owl" problem at some stage. I was trying to figure out how to do something today and I must have skimmed through 30 tutorials aimed at people roughly my skill level before I finally found one that explained the missing bit. That missing bit turned out to be pretty easy, but almost every thing I read just assumed people knew how to do that part, and focused in on all the wrong things.

As for actual tutorials for beginners, the biggest problem isn't that they're badly written. The biggest problem is that they don't exist. But, to be fair, they're actually really hard to write. Explaining things requires that you really understand them well. But, when you understand them well, it can be hard to put yourself in the shoes of someone who knows so little they don't even know what questions to ask. Most computerey things are complicated enough that by the time you feel confident enough to write a tutorial, you've forgotten what it was like to be a beginner.

TBF, if your step by steps instructions works, it doesn't matter how complicated the command is.

When it comes to documentation, at least for myself when I'm learning new things, I like to look at it like a recipe book.

The book shouldn't contain just the ingredients and what the final product looks like. It needs to be more in depth than that. It needs to contain the ingredients that go into it, how much of those ingredients, the time to cook, what consistency to look for, prep time, etc.

There are plenty of people out there who have never cooked before, and a recipe book/instructions on how to cook a favorite dish is the perfect way to share your love of the craft and the dish that you made. Then, with your recipe as a guideline, people could change it to suit their tastes, and so on and so on.

That's just how I look at it. I wish I could interpret developer instructions and write up a more user friendly documentation for them. I would love to be able to give back to the community in some more meaningful way than just barely knowing what the developer is providing and using it and making a mess of it my first few tries until I learn from my mistakes.

Boop!

Oh do grow up, frankly.

When I taught myself to program, there was no internet. You went and bought an enormous, 800 page book (usually written by Charles Petzold) and you hoped to Darwin something, anything would be understandable and lead you to move forward just a little bit.

If it’s worthwhile doing it’s hard.

I'm going to steal some of these words and use them in my future projects, and no one can stop me from doing that

I really enjoy this writing style. It reminds me of what it was like reading Dave Barry’s Sort Of History of the United States when I was a kid.

And that’s what led me to argyling the pintafore with the quagmire instead of the hoobastank!

Tank vs. quagmire, who wins?