Thank you so much for replying and I’m grateful for your insight. In regards to your first point, it is interesting that it is not completely required to be an active contributor to get your foot in the door. I do think it would help with the substantive issue of being a bit rusty at coding and my confidence (as well as being a good thing to do), but it is good to know that there are differing opinions in industry about that.
I had the same impression as you in regards to the helpfulness of a degree. I had wondered how much I missed out by not going to a flagship state university or a well regarded private school, so knowing that some people view good grades at a mid-tier university as qualifying is helpful. It is also helpful to know that while not ideal, mediocre is at least acceptable in the beginning. I probably have been letting tropes about “genius tech founder” influence my perception of necessary qualifications. Even though intellectually I know that both not everyone is incredibly technically competent and that the trope is usually hype to attract VC funding.
Also, that roadmaps.sh site looks really helpful in that it shows the concrete skills necessary. Thanks!
I completely agree with you about motivation in isolation. I’ve been doing a bit more this past week, but I need to keep pushing myself to stay focused on the same project after a day or so. It was easier in college because I had more external motivation. I did have the idea recently that I could learn a bit of graphics and get a bit more motivation out of what I code. I’ll probably stick with that for a couple of months because it is a fairly versatile skill to know how to tell the GPU to do things. Additionally, thank you for letting me know about the Out in Tech group. It sounds like it would be helpful.