My experience adopting Vue.js with my coworkers

-

This year I had the opportunity to lead 2 projects at work, one was an API for the company's Mobile App and the most recent one was a Web App, this last one was the most joyful for me and I want to share my experience adopting Vue.js with my coworkers in this project.

Prior to the projects, I assigned a task to the team, "choose a JavaScript Framework" to use in our future projects based on 3 simple criteria:

1) Learning curve 📚
2) Speed 🚀
3) Documentation 📑

Maybe there are better criteria but I didn't want to overwhelm the team with a bunch of trivial ideas of how to choose the best JS framework, and we had to start with something as soon as possible. Also, my team was really worried about 2 hidden criteria:

1) Experience among the team member in any JS framework to be adopted.
We were going to face new concepts, paradigms, technologies, therefore we wanted someone who could guide us during the process which is normal when you're facing new things. There were only 2 developers on the team with JS framework experience; I had worked with Vue.js in a personal project (RAMdomizer.com) and another coworker with Angular.

2) The framework's popularity.
Some team members didn't want to learn a technology not popular enough to be relevant for future job opportunities. I  understand them, however, I really disagree with this point of view. I had to emphasized that the JS framework didn't really matter to find a new job opportunity. Nevertheless, it's more important to improve your development skills.

We submitted our votes and as you can imagine for the title of the post, the winner was Vue.js.

The time to complete the Web App was only 3 weeks including the test, so there wasn't too much time to learn Vue.js. I made a short presentation, a demo, and give them some tips to start right away. The results were amazing, the team grasps the concepts really fast and we delivered on time.

To conclude, based on my experience I highly recommend you to try Vue.js, the community is pretty big, the learning curve is incredibly fast (tested by my team 😜), you will make awesome Apps with less effort. I also invite you to try vuetifyjs a Material Design Component Framework, your project will look prettier than ever.

Popular posts from this blog

GitHub Pages + Vue CLI 3

-
Image
In this post, I will show you how to run your Vue CLI 3 project on GitHub Pages in a few simple steps. GitHub Pages is ideally for your personal website, documentation, demos, or your wife's website  😊 ... basically, any static project that you want to display to the world quickly. For the purpose of this tutorial, I will be using  mejiamanuel5 / gh-pages-vue-cli-3    a project that I created for a better demonstration. You can clone my repo, use your existing Vue CLI 3 project or create a new one. If you don't know how to create one, this guide can help you. Ready? let's start: 1) At the root of your project create a file called  deploy.sh  and add this script: # abort on errors set -e # build echo Linting.. npm run lint echo Building. this may take a minute... npm run build # if you are deploying to a custom domain add a CNAME (uncomment the next 3 lines) #cd docs #echo 'yourcustomdomain.com' > CNAME #cd - # deploy echo Deploying..
Read more

A Closer Look at Pair Programming

-
Image
Last June 11th, I had the opportunity to participate as a speaker in the Vue.js Global Summit by Gleekle to talk about one of my favorite topics, Pair Programming. My intention with this talk was to motivate teams to adopt this wonderful technique to improve their productivity. Here I bring you a summary, we will be covering: What is Pair Programming? Benefits of Pair Programming Pair Programming styles Implementing Pair Programming (tips and tricks) Common Pushbacks Takeaways Before start talking about Pair Programming, it’s important to mention some of the most common problems inside a development team: First, Lack of communication between team members - This could be partialized or generalized problem depending on the company Another one is Centralized knowledge - This happens when one team member is the to-go person for any particular technology, codebase familiarity, or domain knowledge. And yeah somebody is coming to your mind right now Never-ending code reviews - A sing
Read more

Let's talk about Web Accessibility

-
Image
Most web applications are developed for users with no disabilities, under the assumption that all users have the same  physical abilities and resources , when in fact it's the opposite. The circumstances of our users will vary from having internet issues to being physically disabled, and here is when Web Accessibility comes into play,  so you can optimize your web app and adapt it to all audiences. Web Accessibility  (a11y for short)   refers to designing/developing web apps so people with some kind of physical disability, situational disability, and socio-economic restriction (like low internet speed) can use them. Web Accessibility encompasses all disabilities that affect web navigation, including: 👁 visual 🧠 neurological 👂🏽 auditory 🖐🏽 physical  🗣 speech The first time I heard about this concept, I was surprised by the number of people who are restricted to fully use web applications. My first guess was that around 1% to 5% percent of the population has a disability, but
Read more