Location: Wisconsin, USA; US Citizen
Remote: Yes (remote only)
Willing to relocate: No
Technologies: (Vanilla) HTML/CSS/JS
Résumé/CV: Nothing relevant.
GED, some college (web design & dev), and have been programming as a hobby for 18 years. I'm most comfortable with JS, but am liking CSS3 the more I use flex and grid. I learned to read documentation from the Java and Android docs, so I love well-written detailed language documentation like on Mozilla Dev Network. I use/used Travis-CI, AppVeyor, and now GH Actions for CI/CD including testing, building and publishing artifacts to GitHub Releases (if any), code coverage (nyc or c8 for Node/JS, kcov for Bash) with `codecov` for reporting, and automated code reviews by `Codacy` (if the language/project is supported).
My projects are largely experimentation for the sake of exploring and expanding my limitations, and low or zero dependencies unless there's something too complex to "reinvent the wheel". Currently I'm working on a vanilla HTML/CSS/JS editor-only VSCode clone. My most notable project yet is an Electron Linux/Mac/Win Steam client settings manager GUI app. It could modify most settings, included backup/restore with a minimal data snapshot (to remove useless/sensitive info), and had two automated workarounds for common issues. First, using a hidden-in-plain-sight feature to temporarily skip an update for an app (since removed); and B, cancel an app update after it started. My Mac died and then Valve/Steam began major updates to the client shortly after I released this, so it had a short life.
Other dumb ideas include a Bash list-based prompt and small automated test framework when I only had a phone (Android < 10 + UserLAnd + Ubuntu = <3), and helping add the beginning of cross-architecture builds to `kcov` using qemu and binfmt-misc around that time; a HTML/CSS/JS Mastermind-like solving tool for an event in a game I used to play; two attempts to build a hybrid web/Android Java Git app (first was zero deps so obviously went awful, second would use JGit but the code viewer evolved into the VSCode clone); some minor Payday 2 Lua mod bug reports/fixes and one update to a mod; multiple attempts at an ultra fast Mocha-inspired vanilla JS test framework; and more.
Can only recommend HTML5/CSS3/ECMAScript (modern JS) as I'm not deep into the backend yet. No matter what else is piled on top they are the core, and others are using them on some level. The languages you use are less important than the concepts you will learn, in the long run. Because if you know how to do something in one lang/stack you can do it in any comparable alternative provided enough documentation/StackOverflow and time. I went for languages instead and though I can "just read" some code I don't fully understand in random languages, I also don't have as good of a grasp on my preferred & used languages.
Just a hobbyist, but always wanted a programming job; not a socialite though as everyone expects nowadays. Currently screwing around with vanilla HTML/CSS/JS to build a zero dependency simple code editor using VSCode as inspiration. Parsing and highlighting is working well, including nested tokens, but folding is kicking my teeth in. Took a break from that to work on Shift/Tab indent/outdent, and that has went about as well. So, bouncing between those and treading water.
I'm sure spez will deliver the checks in person monthly. He can talk to the users about their comments he edited recently, and encourage them to join communities like jailbait.
Odin Project and freecodecamp were highly recommended on Reddit a couple years ago, no idea if that still holds up. Worth looking into. Colt Steele/Udemy/paid courses you can't guarantee are up to date suck because of low effort updates to outdated content.
MDN (Mozilla Dev Network) is best for detailed documentation, and has plenty of small lessons but no actual bootcamp/course. Avoid w3schools except for reference documentation; they have gotten better, but there's still plenty of simplified examples that are bad practice like inline styles and event handlers.
One of the first lessons from good teachers is to not compare yourself to others, as everyone learns differently. Only compare yourself to your past self. Programming is extremely complex and usually doesn't "just work" for the brain, so any progress towards understanding is great.