Web Development Overload

As someone a little bit older than most in this community, I have been in a few shifts in the workplace. I started working when it was cool to be in a factory or work on a farm. Doing physical labor and being in the middle to upper-middle-class family was a goal in life. My things have changed over the years.

Posted by David J Forer on February 12, 2020

It’s pretty exciting to create your very first ruby app or gem. It kind of makes you feel like you belong on a minimal, low level but belong none the less. When we decide we want to become a developer, we strive to be seen as worthy. Imposter syndrome is not a joke. Once you have something complete that works and was created by you; You feel like you are part of that community. It is then that you can look back on what you did to learn from the positives and negatives of creating that gem. This article explains some of the lessons I learned while doing this and hopefully help someone else down the road.

1. Prepare and write out a plan. I tend to have ideas and would instead action items then prepare to do them. However, without proper planning, those ideas are fraught with errors. When coding, it is imperative to have a plan so that you don’t go down a rabbit hole. My first attempt at creating a gem wasn’t appropriately planned and thus failed. I just wanted to get some information, but it was unclear how I was going to get it. It would be best if you also had an idea of what the completed product looks like so you can determine the best path. In this particular gem, I had a good idea where I wanted to get to, which helped me determine how to get there.

Posted by David J Forer on February 11, 2020

Lots of Positions

Posted by David J Forer on February 11, 2020