About Darin Boesch

What is your tech story?

I started coding in the late 1980s, writing programs to solve fluid dynamics problems while getting my BS in Aeronautical Engineering from The Ohio State University. Upon graduation, I headed to Seattle and joined Boeing to work on the 777, where I designed a part-tracking database.

Seattle was an incredible place to live in the 1990s. Grunge bands were everywhere, Microsoft was on the rise, and yes, I wore flannel with Birkenstock sandals. (This would sound quite funny if you knew me now!) Mobile phones were becoming mainstream, so I did some contracts at AT&T Wireless. Of course, living in Seattle during the “dot-bomb” era made it necessary to take a few jobs for some doomed startups. I still feel that it was valuable experience to have been at failed companies. I am now able to recognize some of the signs when a company is in trouble.

In 1998, I moved to Charlotte and have been here ever since. I have done a number of contracts all around the city since then. And for about 10 years, I owned a company that provided Electronic Data Interchange (EDI) solutions to suppliers for BMW. I have used quite a number of programming languages and technologies, and I have written software for a very wide range of businesses.

Why did you decide to teach at the Coding Boot Camp?

I have been a Lead Developer and mentor to a number of more junior programmers, and I have even been a part-time Life Coach. A successful career needs to include knowledge sharing, in my opinion. I see the Coding Boot Camp as a way to reach more individuals to do just that.

What is your teaching background/style?

Up until now my experience teaching has been more one-on-one or to small groups. I am a huge advocate for learning and for providing support and help when I can.

In the Boot Camp, I’m looking forward to discussing  context, alongside of the topics. In programming, knowing when and why to do something is as important as knowing how to do it effectively. Googling how to do something is easy, but knowing what you need to do to solve a particular problem comes primarily from experience.