My Secret Life as a Spaghetti Coder
home | about | contact | privacy statement
Everyone will run into "that guy" on a project at some point in their lifetime. He complains about everything, and he's actively trying to subvert it at any given time. It seems like he had an agreement with another vendor to take a kickback, but they didn't win the bid so he's stuck with you until he can prove your incompetence to the other stakeholders in his organization.

At every turn, he's complaining about something. He's "spent hours on the phone" with you about a problem, but you know you've only talked to him once for 5 minutes to get a password outside the normal meetings. The normal meetings resulted in changing requirements and specifications as time went on, and he never spoke up until that part of the product was complete. Now he says you're useless and can't follow directions: he wants the original widget design back.

He's not the only stakeholder, but he's the stakeholder for certain parts of the project. Maybe his mini-projects are just there to grease the wheels and facilitate other parts of the whole. Maybe it's a key part of the end product.

There's an effective way to deal with bitchy subversives when you're at the meeting with everyone from each side of each organization and "that guy" is making insane requests and ridiculous accusations. Simply pose an open question for everyone to answer: what about that piece is holding the rest of the project back?

Trying to answer that question will reveal that there's nothing technical that's holding it back. The only thing holding back the project is that guy's whining.

Then you can move forward.

Hey! Why don't you make your life easier and subscribe to the full post or short blurb RSS feed? I'm so confident you'll love my smelly pasta plate wisdom that I'm offering a no-strings-attached, lifetime money back guarantee!

Leave a comment

Great idea! I'll try to use it next time if happens.

Posted by Kevin Guerra on Jun 30, 2016 at 04:41 PM UTC - 5 hrs

Leave a comment

Leave this field empty
Your Name
Email (not displayed, more info?)


Subcribe to this comment thread
Remember my details

Picture of me

.NET (19)
AI/Machine Learning (14)
Answers To 100 Interview Questions (10)
Bioinformatics (2)
Business (1)
C and Cplusplus (6)
cfrails (22)
ColdFusion (78)
Customer Relations (15)
Databases (3)
DRY (18)
DSLs (11)
Future Tech (5)
Games (5)
Groovy/Grails (8)
Hardware (1)
IDEs (9)
Java (38)
JavaScript (4)
Linux (2)
Lisp (1)
Mac OS (4)
Management (15)
MediaServerX (1)
Miscellany (76)
OOAD (37)
Productivity (11)
Programming (168)
Programming Quotables (9)
Rails (31)
Ruby (67)
Save Your Job (58)
scriptaGulous (4)
Software Development Process (23)
TDD (41)
TDDing xorblog (6)
Tools (5)
Web Development (8)
Windows (1)
With (1)
YAGNI (10)

Agile Manifesto & Principles
Principles Of OOD
Ruby on Rails

RSS 2.0: Full Post | Short Blurb
Subscribe by email:

Delivered by FeedBurner