![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
The article isn’t terribly long, but here is the direct link to Taters https://www.youtube.com/watch?v=GvJtVOmFs5Q
The article isn’t terribly long, but here is the direct link to Taters https://www.youtube.com/watch?v=GvJtVOmFs5Q
Lots of good technical starting points here. I don’t want to prematurely discourage you, but before you get into any code, evaluate your problem solving abilities. If that is an area you struggle in, work on that first, or at least in conjunction with programming basics.
I’ve worked with engineers who have all the code skills, but when faced with a complex issue, struggled to break it down into it’s simplest components and wound up with a messy, over-engineered solution.
My social anxiety would love to give a one word answer and move on, my ADHD/self-doubt/trauma says “are you sure that’s enough? they’ll think you are an idiot and don’t know what you’re doing if you don’t elaborate”
For me, it depends on how much time I have before starting. If the start is immediate, “I’ll figure this out on the fly” then ride that “oh, shit I don’t know what I’m doing” adrenaline fueled dopamine wave all the way to borderline success. If I have lots of time before starting I’ll over analyze then try and fail to become an expert and give up before starting.
The bulk of my day to day work is with a legacy application written in vb.net, and I couldn’t agree more with your first paragraph.
People don’t want to watch reruns