Old Man Yapping: Three Common Problems

Look, it's the same old thing, find the problem and fix it. It's almost like software is not all that complex, it's just a matter of going in and getting things done. Using the garbage-farting machine doesn't count.
I had some focus problems with the camera, which is old and should probably be replaced.
Read my Substack - cdarklock.subs...
Follow me on Tumblr - www.tumblr.com...
Watch me lurk on Cara - cara.app/cdark...
Catch me on Blue Sky - bsky.app/profi...
Jump up my Discord (it's basically dead!) - / discord

[@flipperiflop]

“Any sufficiently advanced technology is indistinguishable from magic.” - Arthur C. Clarke
I do enjoy using Claude for sparring with ideas. I can give it a problem and let it generate some ideas to see how they compare to mine and get a feel for what might be a better way of solving the problem. Or I describe my idea to it and ask it to give feedback on it, and often enough it comes up with questions that I did not consider, that help me in making sure all the bases are covered.
If I worked in a team, this use-case is not as useful, but as a solo-ish dev, it is really damn useful.
As for the tutorial hell, best way to get out of it is to start building something new/different. So many times I've looked into something shiny through a tutorial, and then want to finally use it for the project that I have, the realization that I got no clue how to do it with this hits hard, and just need to try to build it in some way with what I learned and see how close/far it goes. You need to be brave enough to jump in and just build something to get the confidence of working with it.

[@easpur]

Tutorial hell also traps you with a false sense of security. You get used to only doing the tutorial parts and never venturing past it because you're even afraid of making mistakes anf breaking the tutorial program.
It's like doing the examples in a textbook and never doing the problem sets at the end of the chapter. You'll be trapped in a dangerous comfort zone.
The first step to escape tutorial hell is to accept that you are afraid of making mistakes. Next, go back and read out loud what you did (just like you suggested). While doing this, ask yourself why are the things in the tutorial the way they are and if they could be done differently. This can help you develop your critical thinking skills by judging your thought process (or the tutorial's author).
Then, start experimenting without being afraid of breaking things. And you will break things, a lot; it's part of the learning process. While learning, making new mistakes should excite you because it means you found a new opportunity to learn something.

[@cdarklock]

GREAT addition. You're gonna fuck up. You're ALWAYS gonna fuck up. If you're afraid of getting it wrong, you'll never get it right.
As I say over and over, you cannot do good work without doing a lot of bad work.