At the beginning of the year I quietly changed jobs. It was a tough decision because I was only 6 months into my job at the time, but for a variety of reasons it wasn’t the right fit. I’m now one month into my current position and couldn’t be happier. Read More
I’ve always wanted to start an organization to help others. One idea that I have been exploring was a solution to connect busy folks with a mind to do community service, with volunteer opportunities. There’s no shortage of opportunities, but if you’ve ever tried to look for something on your own you quickly find challenges:
While planning out the next steps for my fitness app, the question crossed my mind, “should I use my own API to actually power the backend of my app?” After a little research, that is where I learned the pros and cons of “eating your own dog food.” Gotta love how technology professionals communicate.
As a technology professional, it is important to keep my skills sharp and stay up-to-date on the latest technology. The first step toward that end was finding my dream job. Nevertheless, it’s important to experiment with new things outside of work. Things that I would not normally get a chance to do otherwise. I’m using this post outline a plan of attack over the course of the rest of the year.
In preparation for building a RESTful API for my fitness app (and other on-the-job projects), I recently read Lorna Jane Mitchell’s book “PHP Web Services: APIs for the Modern Web“. It was fantastic and everything one could hope for in a technical read. It covered a wide range of topics, and yet each was in just enough detail that I could create working samples of my own.