Skip to main content

New Year Resolutions 2012



Before I get into the New Year resolutions for 2012 let’s recap how I have done with my 2011 resolutions.  Thankfully they are easily found on my blog:
http://www.mikebz.com/2011/01/new-years-resolutions-2011.html 

How did I do?  I had just five things on my list: dribbling better in soccer, dropping my body fat percentage below 10%, taking jiu-jitsu classes, take meditation classes and go on a Zen retreat.

I actually did pretty well.  I have been consistently going to meditate at the San Francisco Zen Center and even went on a retreat to Green Gulch farm.  The jiu-jitsu ended up getting punted on.  Body fat percentage is stuck stubbornly at around 12% and won’t go below 10%.  Soccer got taken off the list because I just can’t find a good soccer league close to my house.  Instead I picked up tennis, I think it’s a fair trade.

Now on to my 2012 list:

- Consistently take Yoga and work on the flexibility of my body
- Figure out a good travel diet so that my time on the road doesn’t kill my stomach
- Use Ruby on Rails in at least one project
- Write blog posts every two weeks
- Try Jiu-Jitsu (2011 resolution carried over)
- Take Tennis classes

Let’s see how it goes!  Wish me luck!

Comments

Popular posts from this blog

Quality of Code is Quality of Life

About 20 years ago when I started working in technology companies I remember “the best” engineers had similar patterns:
-They worked crazy hours
-They knew the systems no one else knew
-They could react and deliver something faster than anyone else
You could always hear other employees say: “Bob is really smart, no one knows how to get anything done in system X besides him!”

This reinforced optimization around being the only person who knew how to do something in some part of the code.  That in turn reinforced job security and bargaining for those engineers, but also chained them to a particular system.  We had big code bases of C++ or Java code where some “Bob” hacked up features as soon as he possibly could.  “Bob” would have occasional nuclear disasters where he’d sleep in the office or through the weekend and then everyone would thank him for how he “saved the day.”  “Bob” sacrificed his quality of life to get praise when he hacked stuff up quickly and then the second time when n…

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of
different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers.

Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily accessible…