@heroesbane If you write on top of code that is broken and it's still broken, is it now "more broken"? Likewise, if you actively decide not to write additional code on top of broken code, does it become "less broken"?

Wait, wut?

It can be very challenging to convince someone that they are better than they think they are, especially when they are so deeply set in the whole "I can't do this" mentality.

As some of the peeps above have already alluded do, perhaps throwing some challenges his way might help build up his confidence? You could set them with a goal of building something the two of you might use, or search around for some coding challenges online (codeingame.com might be a fun start).

Failing that, see what happens when you stop telling him to dev altogether. As a neanderthal myself I have to fight the urge to do the complete opposite of what people tell me to do a lot of the time! No idea what it is about us dudes, so many of us can't stand being told what to do... but I guess that's a discussion for another site.

#stubborn_old_men

"Hello, this is Microsoft Support. How the fuck did you get this number?"

DOS

@GodHatesMe So THAT's what they look like!

@Kalvin Expanding on your point, I wonder if there is a generic "sweet spot" that a user expects to wait for. Not so short that it's over in a flash, and not so long that they get bored. My gut feeling would be around 30s... just enough time to throw in an advertising loop and high-five Satan

HAHAHAHA! LOVE IT!

Teaching others is a great way to learn... its also a brilliant way to totally fuck up generations of devs by misunderstanding something! XD

What have you got against Satan's balls?!