Submit captions for this cartoon of “The Moverick” in this post’s comments. And don’t forget to submit captions for the other Software Engineer Types as well…
The Maverick
The Maverick will do your feature IF he can do it in Ruby on Rails. Or Haskell. Or Python. Or <other hot new language that his peers don’t know and therefore can’t evolve or maintain>.
And, NO, this type of Maverick has nothing to do with John McCain or Sarah Palin. Well, probably not.
Distinguishing Characteristics:
- Smart. Creative.
- Doesn’t want to build on or maintain the existing codebase (because it’s a spaghetti nightmare AND because it’s written in Java, which is sooo passe), so he’ll roll his own. This will include the creation of an exotic protocol and adapter layer so that the old code can call his code.
- Dependable — if you let him do it his way.
- Magically finds his way off the project if he is not permitted to build in his preferred language.
Project Pitfalls:
Oh, you’ll get your feature all right, and you’ll get it on time and it’ll probably be done well and it may even delight you and your users, but once that guy leaves someone is going to have to refactor it in order to evolve it. And we all know there are few words a PM likes less than “refactor”.
Achilles Heel:
Back in my hometown, we used to say “That dog won’t hunt” when referring to someone who simply and inexplicably will not do the obvious, such as build on the tech stack into which he was hired.
Do you need this engineer?
Maybe you could aim this smart engineer at a custom one-off or a stand alone widget that doesn’t need to be evolved or maintained. No.
Best Bet:
Be prepared to make your perfectly reasonable case for building the feature in the existing language in a public forum. Make said case without emotion, and in front of his peers & manager because, trust me, they don’t want to support his alien creation any more than you want to.
Submit captions for this cartoon of “Offshore” in this post’s comments. And don’t forget to submit captions for the other Software Engineer Types as well…
Offshore
Where are these guys, anyway, and what time is it there? Who knows; you always have to count the time difference on your fingers.
But anyway, they seem very nice, and they do try to read the documentation. They just don’t always understand it and it’s not their fault that they were home sleeping when those critical changes were decided last week.
Distinguishing Characteristics:
- Located in Malaysia, China, or a former Eastern Bloc country. (Ukraine is the new India).
- Their proper English is downright charming.
- Sometimes they say they understand when you know they don’t.
- They make a lot more work for you, including having to attend 9PM meetings. On the upside, it is nice to have a glass of wine in your PJs while discussing the desired behavior of wildly far-flung corner cases for no other benefit than that of QA.
- Will often do the needful.
- Sometimes their code isn’t great. But, as I have mentioned, they are generally quite polite.
- ARE ULTIMATELY NOT CHEAPER. But we’ll let CPM cover that topic separately.
Project Pitfalls:
Too many to count on your hands.
Achilles heel:
Communications.
Best Bet:
- Document the hell out of your requirements and functional specs.
- Provide completed mock sets,including exception scenarios.
- Keep up with change requests.
- Meet with them often, and for God’s sake speak slowly (but not louder, because duh) and speak clearly
- Stop the meeting conversation often to see if they have any questions.
- Also, I know you don’t want to hear this, but for best results, you really should just go there for a week or so.
Submit captions for this cartoon of “The Great One” in this post’s comments. And don’t forget to submit captions for the other Software Engineer Types as well…
The Great One
Where did this engineer come from, and can you have five more of him?
Distinguishing Characteristics:
- Always delivers on schedule, even when unforeseen code bottlenecks require more time that initially estimated.
- If unforeseen bottlenecks arise, you don’t hear about it from this engineer. Instead, you hear about how this engineer worked all weekend from one of his peers.
- Respected by engineering peers. Professional in meetings.
- Honest with estimates.
- May have a Star Trek accent or a superhero fetish. Loves watching “How It’s Made”.
- Solid code, sometimes delivers more than what was requested.
- After the feature is launched, asks whether it met the users’ needs.
- Keeps up with his bug queue.
Do you need this engineer?
Um, duh.
Project Pitfalls:
Try not to hug this engineer in public. He gets embarrassed and human contact is sometimes confusing.
Achilles Heel:
This engineer is so dependable that his manager tends to put him on every project. He sometimes has trouble saying “no”, so can become overstretched. Also he tends to be optimistic in his estimates.
Best Bet:
- Give lots of public credit to this engineer, even if he doesn’t care about that — because his peers might.
- Send nice notes to his management.
- Don’t ask him to attend time-waster meetings, but if he must, publicly change the agenda to accommodate his part first so he can leave quickly.
- Add time to his initial estimates to buy him some wiggle room.
- Play Halo with him
- Bring him food.
- Ask how you can help him, and ask often.
- Encourage this engineer to breed.
Submit captions for this cartoon of “The Hotshot” in this post’s comments. And don’t forget to submit captions for the other Software Engineer Types as well…
The Hotshot
Smart and knows it, often quite young. Has great ideas and hacks crap together at midnight, then… is done.
Distinguishing Characteristics:
- Unfortunately has little appreciation for what it takes to actually ship software and thus never really finishes his features and his stuff is often fragile or just broken.
- Can’t be bothered with making sure his stuff is internationalized, thread-safe or designed to scale.
- Can’t be troubled to fix what he built because he’s on to the next thing.
- Detests “process” and all the process hangers-ons like QA, PM, Training, and Project/Program Managers.
- Doesn’t read the documentation OR reads the documentation and codes something “better.”
- Says things that annoy his fellow engineers and managers like, “If it takes Ed more than 2 days to do this feature, then he is seriously stupid.” But of course, Young Hot Shot never actually finished a real feature in just 2 days either. That is, if “finished” means working in more than just an obscure corner case scenario.
- Rarely seen without headphones or earbuds. Plays World of Warcraft and Halo.
- Drinks Red Bull and stacks empty cans up in his cube as some sort of offering to the God of Unmaintainable Software.
- All shirts purchased from threadless.com. Appears to either skate or snowboard. Green IM status 24/7.
- Natural habitat is start up environments.
Do you need this engineer?
Depends on whether you’re building something that a person will eventually need to use.
Project Pitfalls:
None, really, because you are not even on his radar.
Achilles Heel:
Cannot build evolvable, sustainable software.
Best Bet:
Convince him he’s a genius who really belongs in your company’s “Innovation” or R&D group.
Fun, fun! Submit your captions in the comments for this cartoon of “The Veteran.” And don’t forget to provide captions for the other Software Engineers Types too!
The Veteran
He’s been here for five years, and he’ll be here for five more.
Distinguishing Characteristics
- Cranky.
- For some reason, he’s permitted to use profanity in meetings and otherwise behave in ways that would make his mother cringe and your company’s attorneys start job hunting.
- Casual Friday dress is too formal. Facial hair is common.
- You’re never in on his private jokes.
- He’s eaten 5 Product Managers before you, and he will chew through 5 more after you’re gone.
- His manager is afraid of him. He’s eaten through 5 managers before this one, and he’ll chew through … etc.
- Yes, he is always a “he”.
Do you need this engineer?
Yes. He has the best only knowledge of your product’s undocumented, spaghetti code and he knows it, which is why he will never support projects aimed at documenting it. Also, if left ungoverned he can negatively impact the other engineers (except for any offshore team members, which he does not really consider to be part of his team.)
Project Pitfalls:
He can smell fear and ignorance, so don’t defer to him too quickly and don’t ask dumb questions. You’re toast the second you utter your first corporate buzzword in his presence. If he gives you a nickname such as “MBA,” you’re screwed.
Achilles Heel:
He wants to tell his project war stories, like how f-d up the project before this one was, and which “business people” on the project couldn’t handle the stress. He’s happiest when reminiscing about Assembler, or about launch 1.x of the product (which is now in V8.3)
Best Bet:
Bring food. Listen to his stories. Defer to his expertise on architecture, even if you think it’s wrong, because he’s probably right. Do this publicly, so he wins. But the architecture battle is your pawn: don’t compromise on anything user-facing, because if he discovers that can scope-cut one critical user-facing feature, this will set the pattern of your relationship.
Remember that “6 Types of Software Engineers” post from way back, authored by “Another PM”? Well, a most excellent reader named HW drew some WICKED AWESOME cartoons of each. PLUS, another wicked awesome reader, Eric, added a 7th type of Engineer – The Clockwork Mouse.
So, now we’re going to have some fun — help the Cranky Product Manager come up CAPTIONS for each of the cartoons.
How to Vote
To facilitate voting, the Cranky Product Manager has created a new post for each Software Engineer Sub-Type with the new cartoon. Please submit funny captions in the appropriate post’s comments.
The Deadline
Submit your captions by midnight (PST) on FRIDAY, NOVEMBER 7.
The Prize
The Cranky Product Manager will send one lucky reader/caption-submitter a mug featuring the winning caption and its companion cartoon. If you leave a real email address, that is. (remember, your email is not published to the blog. Only the Cranky PM can see it.)
Why is the Cranky Product Manager doing this?
Reason 1: Because the Cranky Product Manager wants a funny coffee mug to haul around the office and leave around the war room. When an engineer says something “typical” she shall hold up the mug and point to the appropriate Engineer caricature. It will go over REAL NICE, she’s sure, and do wonders for Product Management and Developer relations. But frankly, she doesn’t give a s&*#. She wants her mug, damnit!
Reason 2: Duh…. To drive blog traffic. Because nothing feeds the Cranky Product Manager’s ego like a bunch of page loads.
Reason 3: What a great way to get out of writing an original post this week! Have the readers do the work!
The Maverick will do your feature IF he can do it in Ruby on Rails. Or Haskell. Or Python. Or <other hot new language that his peers don’t know and therefore can’t evolve or maintain>.
