Michael Gao is a Software Engineer at SolarCity. In this episode, Michael talks about his decision to return to the Bay Area after graduating from Johns Hopkins University in Baltimore, Maryland. Michael started out as an environmental engineer, researching hurricane induced power outages but later became a software engineer. To help contribute to his research group’s model, he learned R programming, and eventually learned other software tools to explore ways to the model faster and more accurate.
He remains curious in learning. He sees programming as a tool, and the application is where his passion derives from. He feels it’s quite fortunate and a coincidence for him to become a software engineer. He talked about how he got the job at SolarCity by learning about the opportunity at a conference. Michael compared the differences between working as *a contractor within an applied science program* at NASA and SolarCity.
For the second interview, I’m happy to invite Henry Ng, a software engineer at SolarCity. 吳奉全 is Henry’s Chinese name (if you are wondering). He can speak Mandarin and Cantonese (and English of course).
We chatted about Henry’s decision to move to the Bay area from Canada, and about the differences he’s found between San Francisco and other parts of the world. He thinks people in SF are more forward thinking. People in SF believe they can change the world and improve society. He talks about how Canadians fit into the Silicon Valley. Visa issues and housing conditions are big concerns to almost every immigrant here.
For the first interview, I’m honored to interview Jordan Olthoff, a software engineer at SolarCity. In this episode, we learn that Jordan grew up in San Diego and came to the Bay area 6 years ago. He studied psychology in college and has pharmaceutical research experience. He recently started his career as a Software Engineer at SolarCity. We had an interesting discussion about how psychology might influence his thinking and help him in developing software.
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.
The programming Editor is a Software Engineer’s best friend (quote from Brian Hsu!!) A software engineer spends most of his time in Editor to write codes (excluding the time we spend on Google and Stack Overflow, of course). So what Editor should you choose for your software engineer life?
Well … there is no real answer for that. You choose whatever you like and make the best use of it. Each Editor exists for a reason. If you can have the highest productivity using a certain Editor, then go for it!