It's has been a year since my first gem was published. What I have learned so far?
Juan Ferrari
Posted on May 3, 2020
Things happen fast! One year ago I was a Junior Developer building a really small gem for Ruby on Rails sort_n_params, my first contribution as a developer to the open source's scene.
What have I learned since then?
1.- It's always good to build things, no matter how small.
If you have an idea, build it up. Ask for help from your colleagues if you're stuck -- it doesn't matter if your idea sounds silly or small, building and finishing things helps us improve our skills.
2.- Publish and share your work!
The solution you have found may be useful to others, so share it. Maybe someone else will help you improve your solution. Don't be shy!
3.- An example of what you can do
Maybe you're looking for your first job in the industry, but a lot of interviewers ask you about previous experience. Having your own project published in Github or deployed in Heroku will help you prove that you already have some experience with coding.
4.- The importance of testing and continuous integration
Technology is advancing rapidly and it is very possible that our code will change in the near future. Testing our code prevents problems and saves time and setting up a continuous integration service like TravisCI to our repository ensures the proper functioning of our project.
5.- It's good to contribute to the Open Source scene
It doesn't matter if you only make a small contribution, it will help you improve and meet a world that is growing every day
6.- Publishing a gem is really easy
Don't be scared! If you want to publish a new gem, there are plenty of tutorials on the web and it doesn't take long to do so.
I hope my experience encourages you to make your own gems and projects. Let's code!
Posted on May 3, 2020
Join Our Newsletter. No Spam, Only the good stuff.
Sign up to receive the latest update from our blog.