Where I’ve been and what I’ve been up to.

Two updates in 8 months. I should be ashamed of myself. Tsk…tsk….

I don’t think I ever actually explained WHAT happened to me after I got that first developer job.

The first job I got was at a (very) small dev shop using Ruby and Rails. Without going into details, that job didn’t really work out. As far as positive takeaways I came away knowing that I had what it took to be a successful professional developer.

My next job was at a code bootcamp in the Los Angeles area. Not a fly-by-night, super shady type of bootcamp, but a legit and respected business. I started with the company as a Teaching Assistant for it’s 3-month all-day program. After a successful 3 months I got offered a position as Junior Instructor, which I accepted and remained in until I left in September 2015.

Without a doubt I would have to say my 10 months working at the bootcamp was the most educational and enjoyable job I’ve ever had. Not only was I able to improve my programming skills by teaching what I knew to others, but I felt a sense of accomplishment as a human being by playing a role in people changing their lives. I was able to learn from and be mentored by co-workers who were not only knowledgeable, but compassionate, determined, and enthusiastic about software development.

In September 2015 I accepted a position at a small startup in Los Angeles using MeteorJS. Meteor is a full-stack JavaScript framework, which means both the server-side and client-side code are written in JavaScript. The fact that I’m working on a full-stack JS framework and haven’t written much Ruby in 4 months is ironic considering I deliberately tried to avoid JavaScript when I first started learning to code because I thought Ruby’s syntax and standard library of functions were superior to JavaScript’s. Well actually, I still DO think Ruby’s syntax and standard library are superior, but at work we code in CoffeeScript, which IMO is what would happen if Ruby and JavaScript had a baby. I get the best of both worlds; I get to write code that’s relatively free of the oodles and oodles of parens () and curlies () and function this, function that, while still learning and being productive in the defacto programming language of the web.

I’ll be writing in this space more often because I have noticed that since Meteor’s adoption is not nearly that of Ruby-on-Rails that the amount of established conventions and standards is very very small. I have some ideas on how to write more straightforward and maintainable code using CoffeeScript and Meteor that I’d like to share here.

Leave a Reply