One of the features I implemented recently at work was allowing users to create “cards” inside their workspace by sending an email to the workspace itself. While not a revolutionary thing to do, it is a step towards giving users the ability to forward confirmation emails to their workspace and have it auto-generate data based on the email contents.
It may seem like common sense to some but using environment variables to mask sensitive access/account information is something more and more junior developers are NOT learning in code schools. Join me as I take a look at some easy ways to prevent that important information from being pushed to your public code base.
I had some time before medical appointment this morning to think a bit more about the Scheduler service I need to create for my PRC-119 app. I have a tendency to think through solutions in my head but not write them down causing me to have to cover the same ground the next time I actually sit down to code.
What follows is a stream of consciousness “brain dump” about that feature/service and some other random thoughts.
After the rousing success that was Day One of the 2016 Ruby on Ales conference, I was incredibly excited to see what Day Two would have in store for us!
…after a bit of breakfast and slow start to the morning thanks to the after party the night before.
One of the hardest parts of starting a new career is the eventuality that you’ll have to interview with a new company at some point. While this process is rarely a pleasant experience, it becomes especially daunting for the rookie developer trying to find that first job where you break into the “real world” of software development. I recently went through a few interviews and wanted to share one of my experiences.
One of the biggest hurdles I faced this year in deciding to make the move from software support over to software development was deciding how I’d get the skills to become employable. There are a multitude of code schools, programming boot camps, and online courses out there that all promise to get you “job ready” in X amount of time.
So where do you even start when evaluating the options?!?
Welcome to the inaugural post of my Error Log! Today my main task was to adapt the geolocation and geosearch features I made last week into an API consumable form. A fun little task that definitely highlighted some knowledge gaps and common mistakes on my part!
One of the biggest sources of frustration for me as a relatively new software developer has been making the same mistakes over and over again and not learning from it.
I’m not so much talking about minor “brain farts” like forgetting to close a parentheses, those are just typing/style blips for the most part. Instead I mean things like forgetting about/how to use parallel assignment or confusing a few of the Array versus Hash methods in Ruby.
To help alleviate those issues: Enter The Error Log