Showing posts with label management. Show all posts
Showing posts with label management. Show all posts

Wednesday, January 16, 2013

coding is like sculpting - but is it agile?

I've had a recent epiphany:  coding is like sculpting.  I guess it took me a while to see the connection (since I'm not a sculptor), but as I imagine it, sculpting goes something like this:

  • Get a big pile of clay.
  • Reduce the pile of clay to the size of the intended sculpture.
  • Start cutting the clay into a roughly hewn representation of the sculpture.
  • Examine your work - is the design going as intended?  If so, continue, else start over.
  • Refine your sculpture with finer cuts - yielding a less coarse result.
  • Examine your work again.  If on track, continue, else back-up.
  • Continue refining your piece - refining, backing up, continuing, etc.
  • Repeat for as many steps as needed.

I've lived with Agile for many years - and my conclusion is that Agile is purposefully designed to support the idea that coding is like sculpting.

Every sprint is your opportunity to move your sculpture forward to it's next level of refinement.  Said another way, at the end of each sprint, your sculpture should be a finer version of what you sculpted the prior sprint.

Agile gives this a name:  the vertical slice.  Every sprint should be a working model that moves (feature-wise) closer toward the end result.

I begrudgingly admit these facts, since I admit I set about writing this to bash Agile for not supporting the notion that coding is like sculpting - when in fact, I concluded the opposite.  Score one for Agile.

Sunday, January 8, 2012

interviewing ftw

The interview process - what a mess.

Sometimes, superstar candidates get looked over.  Sometimes, less than stellar candidates get hired.  I've pondered this at length... it's frustrating.

As an interviewee, you're at the will of an unpredictable, inconsistent, filtering process.  As such, I suggest the following conventional wisdoms:
  • Your resume and cover letter should present your best efforts and qualities.  Sell your "wins".
  • Enumerate your skills, e.g., C++, SQL Server, Perl, etc.  It might seem trivial, especially if you think of yourself of more than just a set of skills, but if you don't, you'll be at a competitive disadvantage.
  • During the entire interview process - from the first contact, the first phone call, and the first interview - speak calmly and purposefully.  Answer questions directly, don't speak wastefully, and communicate as eloquently as possible.
  • Whether asked or not, when you're posed with a "thought" question, speak through it.  Reveal yourself, your manner of thinking, and above all, be honest - in particular, when you don't know an answer, say so.
  • Know something about the position and company for which you're interviewing.  Think of poignant questions to ask your interviewer(s).
The frustrating part is this:  even if you're at 100%, your interviewers might not be.  They might be facing deadlines of their own, interviewing other candidates that day, or just having an "off" day.  You simply cannot control their perspective on that particular day, regardless of how prepared you are.

For interviewees, that's the reality of it:  despite your best efforts and best qualities, your interviewers may fail to expose how awesome you are.  If your interviewers decide to pass on hiring you, that's their loss, unless in fact, you're not awesome.  But that's another issue altogether.

So let's assume you are awesome.  Now we need to examine the process from the interviewer's standpoint.  Because the failure is the interviewer's if they choose not to hire you.

As an interviewer, you're faced with a huge responsibility.  Being one of three to five interviewers (typically), you share the responsibility of whether to spend tens to hundreds of thousands of dollars on a new hire.  Will they be worth more than their salary?  Will they add to the social glue of the team?  Will they motivate their fellow team members, junior and senior, to rise to new levels?  Holy crap this is a big deal.

Here's the weird thing about hiring:  typically, senior staff will conduct interviews.  Being senior, they'll have biases.  Their opinions on hiring will be based on 1) whether the candidate shares similar personal/educational growth, and 2) the statistical pattern bias of their hiring history.  For example, if the interviewer has spent ten+ years becoming a master at recursion, they will take a negative bias of the candidate if they don't firmly grasp recursion - regardless of how much recursion is used in their products.

If you're an interviewer, here's my advice:  erase your biases.  Think of every candidate of being great until you've proven otherwise.  Your job is to discover the candidate's qualities - not eliminate them because they don't have the same technical "chops" as you.  This becomes the interviewer's challenge...  so how do you do it?

I have an approach to interviewing.  Of course, it is biased to my personal viewpoints and past interview experience.  But I strive desperately to avoiding succumbing to my biases.  I honestly believe that, as an interviewer, I am burdened with the challenge of discovering the candidate's greatness in 45 minutes or less.  So let's get to the meat of it - my approach to interviewing:
  • At some point during the interview, I like to take a negative stance to something the candidate expresses a belief in.  I'm trying to evoke a response - because work isn't all positive.
  • All good workers care deeply about the quality of their work.  So I might ask them to explain, comprehensively, how they ensured the quality of a particular project they implemented.
  • As I interview, I listen to every word choice - and every sentence.  Communication skills are paramount.  This is a potential teammate - they need to be articulate.
  • Also, as I listen, I am measuring the candidate's passion.  I am seeking natural, unforced passion.  The best workers are naturally motivated.
  • Finally, I want to measure the candidate's talents for the position.  Being technically savvy is crucial - and I usually pose a handful of technical questions to measure their technical aptitude.
That's just a flattened perspective on conducting a decent interview.  The fact is, I cannot write a recipe on how to conduct the perfect interview.  I will say that, as an interviewer, I am always prepared:  I've read and researched the candidate and their past few employers, I've written my questions on paper, and I am mentally prepared to make the most of the few minutes I'll have with the candidate.

Regardless of what side you're on, I suggest putting forth a strong effort.  Distinguish yourself, whether interviewee or interviewer - your (potential) employer will recognize the effort.

Saturday, October 15, 2011

the "wish and hope" strategy

As a self-proclaimed AMD fan-boy, I have to add my commentary on their recent Bulldozer release.

I'm really disappointed.

It isn't just a matter of being disappointed in the chip.  The Bulldozer failure is a reflection on the engineers and management at AMD.  They must have adopted a "wish and hope" strategy - and that's unfortunate.  They hoped that setting a World Record overclock would matter - but it doesn't.  They hoped having eight cores would be a strong differentiator - but it isn't.

I imagine there was an AMD Bulldozer engineer who convinced his Product Marketing what direction to take the chip.  This engineer's approach was academic - focusing on architectural perfection - instead of what the market wanted.

All we wanted was a new cpu that would put a beat-down on the Core i7 - and AMD didn't deliver.  In my opinion, AMD should have held the Bulldozer release.  Would BMW release a new M5 that couldn't beat Mercede's latest AMG?  No way!!  I think I speak for many when I say I want to be proud of the cpu I choose for my system.  I've been taking a beating from my friends for years for continuing to support AMD.  I knew I would be able to dish it right back at them when the Bulldozer came out... but no... I'm still the dummy.

You goofed up, AMD.  You lost sight of what was important, you rushed a product to market, and you "wished and hoped" we'd be okay with it.  Left with the same decision, I would have simply moved the Phenom to 32 nm and made it an 8-core.  That'd be a true 8-core, none of this shared floating-point pipeline kind-of-but-not-quite-hyperthreading Bulldozer mess.  Instead, you're end-of-life-ing the Phenom.  What?!

Here's my message for everyone trying to bring a new product to market:  don't "wish and hope" that your potential future customers won't notice if you release something that isn't the best - because they will.  Instead, work with your customers:  learn how they'll benchmark your product, and learn what qualities will distinguish your product as a great one.  Then focus like hell on these "qualities of greatness" - and you won't have to wish or hope.

Friday, October 14, 2011

tampering voids warranty

I've been in software R&D for more than 17 years.  I find the recent  trends towards Extreme Programming, Agile, Scrum, etc., very interesting to observe.  Before I share my observations, consider my background:  in those 17 years, I've been a technical first-level manager for ten years, and a second-level director for two years.  I've seen these processes in action as a developer, manager, and director.  In fact, one of my responsibilities as director was "development process".  I've been through Agile training and I've used leading software (Rally) for planning/tracking iterations.

upper management's view

Upper management tends to see Agile and it's kin as "the next great thing".  It makes sense:  these processes promise high quality deliverables and fine grain control of release dates.  Also, because customer involvement is high, the deliverable will be precisely what the customer wants - no more, no less.  These are things the VP R&D struggles to get right every day - Agile processes are seen as a "silver bullet".

first and second level manager's view

First and second level managers get the bum end of the deal when it comes to rolling out Agile.  They have to understand the new process well enough to manage within it.  They have to deal with the full spectrum of developer reactions to this change:  some developers will fully embrace it, some will do everything they can to avoid Agile process.  They have to answer to the VP R&D - and try to explain why the "silver bullet" is taking so long to work.

developer's view

Developers all have something in common:  they are motivated to write awesome code and get recognized for doing so.  Daily scrums, day+ long planning sessions every iteration, and retrospectives - are just a bunch of meetings that get in the way of being awesome.  The majority of developers tend to resent the number of meetings, seeing them as low value.  The final issue:  Agile makes developers feel a bit claustrophobic, since every aspect of their day has to be "part of the iteration plan, in support of their team".

the challenge

If you read about Agile and it's kin processes, they all say the same thing:  "If you don't follow every aspect of the process, it won't work".  I call this a "tampering voids warranty" disclaimer - and I don't like it.  If someone approaches me with the-next-great-thing and it has a "tampering voids warranty" disclaimer, there's a 99% chance I'll reject it.  Let me explain a bit further with an analogy.

I see anything that has a "tampering voids warranty" disclaimer as an immutable puzzle piece.  You're the other puzzle piece.  Since the-next-great-thing puzzle piece is perfect and immutable - you have to change yourself, your team, your family, etc., to make the fit work.  The human nature response to this is to resist.  Not because of the old saying that "change is hard".  People resist because deep down, we all know that there is no silver bullet and the-next-great-thing isn't perfect - it goes against human intuition.  Also, the more you ask someone to change, the more benefit that person should see from having made the change.

Coming back to Agile, the people being asked to change are the developers and the first and second level managers - and no matter how much you polish it, they will see the change to Agile as a net loss for them.  However, the VP R&D didn't have to change at all - all s/he had to do was say, "we're an Agile shop now" - and s/he and the company get all the benefits.

so - what to do?

I wish I had a magical answer here - but I don't.  And you wouldn't believe me if I said I did, since I just made the case that there is no silver bullet process.

What I will say is this:  to be a great manager, director, or VP, you have to resist falling prey to the-next-great-process - especially ones that come with a "tampering voids warranty" disclaimer.  Great products come from great people - not process.  You simply can't invest heavily enough in your people - and I'll be honest, molding great developers/managers is a lot of work - but it always pays off.

As for process, I say tear off the "tampering voids warranty" tag and see what happens.  Trust your team to come up with variations on the process, and let it evolve.  Remember:  the most important aspect of the process you choose is that it brings benefit to people you're asking to change.

Wednesday, October 12, 2011

goal setting

Goal setting happens everywhere - at work and at home.  A personal goal might be, "I want to lose weight."  Your manager may have a performance goal for you, "Improve your communication skills."

These are both great goals - to achieve both would make you healthy (losing weight) and professionally stronger (better communicator).  However, a crucial aspect is missing:  how will you achieve these?!

I bet you thought the missing part was "making them measurable".  Agreed.  These goals lack measure.  But that is easily fixed.  Lose weight:  "I want to lose 25 lbs."  Communicate better:  "Demonstrate improved communication skills by presenting a well-rated presentation at this year's User's Conference."  I'm flying past "making these measurable" because, to be honest, that isn't the hard part.

The hard part is setting up a plan to achieve these goals.  That's because the foremost strategy for achieving a difficult goal is to attack it head-on.  The challenge with the head-on strategy is it will feel like you're making an incredible sacrifice.  Your motivation will waver and usually break because of two reasons:
  1. You're attempting to establish a new behavioral pattern that is less enjoyable than your old ways.
  2. Change in oneself takes time; slow progress will make you question and usually abandon the goal.
Let's take weight loss as an example.  A head-on strategy would be a typical approach:  diet, cardio, and resistance training.  Diet is a sacrifice - let's face it, fries, chips, butter, soda, fast-food, all taste good for a reason - and you've banned them.  Exercise takes time - and it hurts.  So you're eating less delicious food and you're sore all the time.  Your measure of progress is your weight scale.  You get on the scale every morning - and progress is brutally slow.  In as few as a couple weeks, you may start wondering, "All this sacrifice for 1 lb a week?!?!"

Here's my suggestion:  choose a lateral, or indirect goal.  The lateral goal you choose should have these qualities:
  • The side-effect of the lateral goal will be progress against the main goal.
  • Visible progress is easily made - this is critical!

Again, let's come back to weight loss.  Here are some examples of lateral goals for losing weight:
  • Eat "clean" for 21-days.
    • The measure here is to count days.
  • Train for a half-marathon that is nine months away.
    • The measure here will be progress with the distance/time you're running.
  • Enter a weight training regimen with the goal to bench-press, deadlift, and squat your bodyweight.
    • The measure here is the amount of weight you lift.

I admit that a head-on strategy will achieve the same result as a lateral approach - and maybe even faster.  But that is a surface-level perspective.  If you break the surface, people who take a head-on approach are less likely to continue their endeavor - because the psychological "net worth of the investment" will be viewed as a loss.  Progress came too slowly, and the sacrifice was significant.

On the other hand, a lateral approach has measures that are more quickly made.  Even if you only run another quarter mile this week, or get another rep at 135 lb - you're seeing more progress more quickly.  The psychological net worth will be viewed positively.  As a result, you'll be motivated to continue.

I wager that most goals are in desperate need of lateral thinking: 
  • "I want to save more money."
    • Lateral:  read a book a week for a year (suggest the library).  This would have multiple side-effects.  Less electricity used (TV).  Instead of going out to the movies, start a book club.  Most importantly, learn something new (improve yourself professionally, earning more $$$).
  • "I want to improve my relationship with my spouse."
    • Lateral:  ask him/her one question about their day, every day.
  • "I want to make my product the best."
    • Lateral:  institute a corporate-wide emphasis on first-class techniques for hiring and keeping the best staff.

I'm a big believer in lateral goal setting - I've had a lot of luck with it!  Good luck approaching your goals laterally!