If you are a developer in the web development world, you know that we are in a fast evolving industry. There are tons of new things happening every day. In order to be productive and build great web applications, we need to learn everyday. Attending conferences is one of many great ways to learn. In the conference, I can observe what the current trends are, how people solve problems, and how to make our development lives easier with new tools.
Luckily, my company, SolarCity, supports me to attend conferences. Our team went to the 2016 Fluent Conference in San Francisco last week. It was my first time attending a large-scale programming conference, and I really had a great time learning from all sorts of topics there.
Below is my learning summary:
The web development world is really energetic. Lots of companies provide frameworks, tools, testing, deployment solutions, trainings, etc. The barrier to start building a web app is becoming lower and lower everyday.
If you are front end or full stack software engineer, you usually manage your app’s dependencies in your package.json (NPM) and bower.json (Bower). Do you have the experience that you need to update all the dependencies to the latest version?
I understand some developer don’t like to use the latest version of libraries because of compatibility issue. However, I feel most of the time, the updated version of libraries are more stable and reliable (bugs fixed and people’s open source contribution to make the software better). Our team at SolarCity before didn’t update some dependencies to the latest version for one of our apps. However, I found out that one of the error we saw wouldn’t even happen if we use the latest version of the library. Therefore, after discussion, we decide that we would use the latest version of libraries from then on. One problem is that it’s such a pain to update dozens of libraries in our json file.
Here is the package file for my previous project: OpenElect. Oh dear, how many dependencies are there…it will take years to manually update the version number.
Since I started working as software engineer at SolarCity, I’ve been using AngularJS a lot. This article summarizes the useful articles for AngularJS.
How to get started (Part 1 of the AngularJS – from beginner to expert in 7 steps series)- Great article to help you learn Angular step by step if you don’t know Angular yet.
Angular Style Guide: I always mis-match the John Papa’s style guide with Papa John’s Pizza…You might find me saying Papa John’s style guide and John Papa’s Pizza sometimes…Anyhow, John Papa’s Angular Style Guide is definitely the Bible of Angular style guide. If you are new to Angular, please definitely check this for the best practice of Angular.
AngularJS performance & production tips: Very organized tips for better Angular App performance.
In Hack Reactor week 6 (the final week of our junior life), we started working on our MVP project. It’s our first time in Hack Reactor to work on a project solo. Within 36 hours, we needed to come up with an idea, write our product from scratch, and prepare a demo.
My MVP project is called Github Saga, which is a web service that allows you to enter your Github handle and find out your contribution data among your followers and following.