Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "tutorials suck oftentimes"
Just watched a 30 mins tutorial on youtube and atleast 20 mins of that was debugging his code. Can't you just re-record or atleast cut the part where you go through all the stack overflow solutions!1
STOP EXPLAINING ME THE MOST BASIC COMPUTER STUFF LIKE "What is localhost?" WHEN I'M NOT ON A BASIC TUTORIAL...9
I haven't hated on a thing here for a while, but in my desire to learn more about things such as NLP, ML and other buzzwords, I've had to learn a lot and the internet is the best resource for this. However, there are a million fucking Medium posts about them all with no real in-depth analysis of what is happing, just code snippets and vague instructions.
So my rant is thus: Medium posts and other shitty blog platforms make it so much harder to find legitimate resources for learning since anyone can put up a post and let it rise in search rankings. I want citations, links to documentation and some explanation of why you are doing a thing. Not fucking copy-paste code snippets that vaguely work.
All I want is to be able to go through a short tutorial, get some basic information and have a "For a more in-depth analysis, go here..." at the end. Is that so hard?
No more bullshit "tutorials" or blog posts. Keep your shitty fucking useless posts to yourself until you can flesh them out yourself!9
80% of the YouTube tutorials that I've watched suck and only wasted 10 minutes of my time each. Sometimes, I can work well with doing shit myself. Discovering errors yourself teach you more than following along someone else.2
Would love to share my experience with tutorial hell.
A year ago, if there is no tutorial teaching me how to do something, I am totally lost and stuck for days. Then, I decided to see how people got out of it.
The answer turned to be simple, get comfortable reading documentation AFTER you determine what you are trying to accomplish.
In other words:
1- Determine the problem and the desired end result.
2- Break the problem down into multiple smaller ones.
3- Determine the end result of the solution of each of those problems.
4- Read the documentation concerning what you need to use to solve each problem.
Over time, you would find the need for a tutorial much less in order to solve a problem. Plus, documentation would ideally give the optimal solution for your problem.
Would still be cool if you find a tutorial explaining something hard to grasp, but never depend on finding one.2
What do you hate about software and developer tutorials and how would you change them? What would totally disrupt the status quo with tutorials and make them easier to finish/useful/memorable/fun?6