19 karma · joined August 30, 2018
Good places to learn are things like the Rails tutorial on their website, the Ruby koans, or the Doug Crockford book about JS, frontendmasters.com. Treehouse was also helpful for learning the basics of CSS but I didn't love the cartoonish story around the lessons.
Above all, find a problem you have and think about how you could solve it with technology I would say, it will let you put into practice what you're learning and guide your direction by researching the things you're stuck on.
How do you find these? I've looked for PT work and everywhere wants FT employees or nothing because they say the marginal cost to them between PT and FT isn't much more (admin, training, office space and health insurance costs are pretty much fixed regardless of hours worked)
I end up leaving because I get burned out, because I don't want to drink the Kool-Aid and that doesn't sit well with management, and because I get bored: companies never do something so amazing that I want to keep doing it a year in. It's interesting in the beginning because you learn how the company works, how the software works, you meet new people, maybe discover a new area of the city where the office is in but all that eventually wears out.
As for a PhD, don't you need a masters degree and a topic you feel strongly enough about to spend years dwelling on it? It's not that I don't know what to do with myself, but rather that I don't know how to live my life without playing the rat race.