I'm currently a full time API developer using JS (Node), SQL (MySQL), and Ruby (Rails) and whatever is needed for each new project. - My initial experience wit

I'm currently a full time API developer using JS (Node), SQL (MySQL), and Ruby (Rails) and whatever is needed for each new project. - My initial experience with "coding" was MySpace (HTML/CSS) which led me to learn/experiment with JS. - Rails got me into API development because of all of its "magic" (even though now I'm less about magic by far); but it was a step. - Having experience with HTML/CSS/JS made Rails easier as far as getting something up and running because I already knew what my views should look like and how to get them there. - This allowed me more time to experiment and get to know Rails, leading me to discover a lot of terms and concepts I had to become more familiar with i/e cacheing, server-side rendering, deadlocks, data-layer, and the list goes on forever. - I realized the best thing to be great at, in my case, is SQL because persisting and extracting data the way you want/need to goes so far in making other things easier. - Finally, I started learning how to truly develop architecture, queues, schedule, etc once I got a job on a team where my peers and supervisors were willing to teach me. Hope some of that helps!