Brian grew up in Santa Clara, the son of a mechanical engineer turned software sales executive. Brian excelled in school, but was primarily interested in sports, never really appreciating the technology and entrepreneurial spirite in his own backyard.
Brian spent his four undergraduate years at Dartmouth College in the frigid hills of New Hampshire. Drawn originally by the desire to go skiing after class, his Dartmouth experience included majors in economics and government, and forever shaped his friendships and ambitions.
After an exhileratingly challenging year as a public school math teacher in Oakland, Brian spent the next 5 years in the corporate comforts of Google and Metromile. Analyzing marketing opportunities, crunching models in Excel and optimizing ad campaigns quickly became second-nature.
The entrepreneurial itch in SF was too contagious in San Francisco, so Brian waved goodbye to a stable income and benefits and began a 4-month coding adventure with Dev Bootcamp. He is now working on a few side projects and expects to turn one of them into a full-time pursuit in early 2016.
This last blog post recounts my experience transitioning this blog site from a static CSS structure to one that uses the Bootstrap CSS framework.
As we wrap up the remote Phase 0 stage of Dev Bootcamp, we'll soon begin the onsite immersion program where we will spend significant time using the web application framework known as Ruby on Rails, or more simply, Rails. Rails is an open-source web application framework originally designed by David Heinemeier Hansson in 2004. What exactly is a web application framework? For starters, we must consider what a web application is.
This week in Dev Bootcamp was our 3rd week diving deeper and deeper into Ruby. In today’s post, I’m going to attempt to explain the concept of classes, and why they are incredibly useful in any object-oriented programming language (i.e. pretty much all modern programming languages).