Jul 24, 2011

Help, my CEO is a better programmer than me!

Ha ha, no, he just read "Learn Visual Basic in 21 Days" (well, he skimmed the first few chapters) and he thinks he can program. And he's a "hands-on" type, and feels that if he's not mucking around in everything, he's not doing his job. (Mind you, he actually *is* good at his real job - executiving and shit - he's just not a programmer)

For dealing with such people, have you ever thought about leaving in some really obvious awful stuff that they can point at and say "Hey! Fix that!" and they can go away feeling useful and you can save the buffer that already had that change made and get on with work? Or does that nagging doubt that maybe he *won't* see it - or worse, will like it - prevent you from taking such action?