[0x457]

Tutorial hell...if I had a dollar for every "Anyone has a tutorial on how to build X" where X is some very specific business idea.

I feel the same about "what books do you recommend reading to learn Y" Have you tried looking at the online documentation?

Usually see it from people that have formal CS education. They learned one way to learn things and refuse to adapt to real life.

[Muvasa]

Documentation is not meant for learning. It's to be used as a reference. It's like learning medicine by reading a medical dictionary.

[0x457]

Yes, and? You can definitely learn how to do something by reading relevant references.

[Muvasa]

How would you go about it. Let's say I want to learn how to do x in library y. How am I gonna find x. When library y has it's own idiosyncraties. In the library the concept is named differently so searching through the documentation yields nothing. Let's say you find what you are looking for. You read the documentation. And it makes no sense like if I was learning haskell and I searched for a monad and got "a monad is a monoid in the category of endofunctors". It's a ineficient process.

Documentation is the most helpful when you already know something and want to learn the specifics. Or when you are already using something and have an issue and want to figure out why.

EDIT: Another issue I just came up. Structure is very important. It's good to know how to sum before how to multiply. It's so important having a hand crafted pathway leads to rapid success like MathAcademy does.

[0x457]

To be clear, that is not the way I'd recommend for someone with zero knowledge in software development. The assumption is that you understand something, just not this language/library. I don't think following a tutorial is a good way to learn anything besides doing this very specific thing in a tutorial. You won't learn things like how to consume documentation and evaluate libraries, which is IMO required to develop anything there isn't a tutorial for.

Maybe use libraries (and language) with better docs? I don't know much about Haskell beyond fixing other people outdated software, but I was able to do these fixes without watching any tutorials and reading books, just by reading docs.

If I were to build web service in rust, Google would lead me to axum, and https://docs.rs/axum/latest/axum/ pretty much gives me everything I need to know to get started.

Then I will want to add some sort of CLI to start that service, clap.rs docs are pretty clear. Then I will want some configuration management, I will search crates.io for crates providing such functionality and evaluate how they work (by reading the documentation), pick one and implement.

When I wanted to build an android tv app, I've read android docs and built it. If I were in tutorial hell, I'd google for "building android tv reddit client" and not found any.

Decided to build a small macOS tray app for myself? A few minutes reading the official docs, and I'm ready to start.