Programmer Architypes

By: Johnathon Wright on: November 30, 2020

In early 2004, Nikhil Kothari wrote about three personas Microsoft came up with while working on Visual Studio 2005. Mort, Elvis and Einstein. I have my own list.

As a tech lead, I talk to my team about programmer architypes. We all have many traits within is... and these can be good when used at the right time, but bad when used at the wrong time. At any rate, they are characteristics of programmers that are worthy of naming so that we can think about them.

Super Man: Superman flies in to a Big Disaster. He battles the enemy at all cost. He destroys everything in the vicinity. He doesn't write or run any tests. Instead, once the enemy (a huge bug or problem code), s/he flies away leaving broken streets, fire hydrants spraying water, cars destroyed, and walls lasered. I guess the insurance companies clean up after him?

Yoda: Yoda is a powerful and wise user of the force. However, he is hesitant to act. He is often mysterious, causing others to wonder whether he will actually do what needs to be done. He speaks in riddles. He's still a fun and interesting person -- but his hesitation paves the way for Emporer Palpatine to take control. In summary, you can be too cautious. Trust

Pigpen: Best Practices, Hogwash! Interfaces are for sissies! Symptoms: Classes with no state; Classes with 104 methods; Many copy/paste methods

Inspector Gadget: Big new project?! He’s got some untested tools that would be perfect! Does not care about risk. Loves new technology. Knows all the newest jargon. Doesn’t so much care whether technology is “vetted” or “a good fit.” Finds solutions without problems.

Batman: Motivated by culture, guilt (or other), suffers silently. Will sacrifice anything for the team: Work long hours, Will strive for any impossible / arbitrary deadline; enables / hides poor management; poor work/life balance;

Road Runner: Accomplishes a LOT of coding -- so much so that s/he is the biggest contributor on any project. Maybe not the absolute cleanest code, but will knock things out and get to the next task. Becomes very popular with management, not very popular with those left behind to clean it up. This developer then struggles to move on because they're always called back to work on or explain sections of their own code. Likely to get burnt out. Developers who move too quickly are actually a larger risk to long-term success than developers who move too slowly. A video about being a 10-x developer focused on output vs outcome (and a roadrunner is obviously focused on output.)

See my presentation on common development project issues.

In early 2004, Nikhil Kothari wrote about three personas Microsoft came up with while working on Visual Studio 2005. Mort, Elvis and Einstein. I have my own list.

As a tech lead, I talk to my team about programmer architypes. We all have many traits within is... and these can be good when used at the right time, but bad when used at the wrong time. At any rate, they are characteristics of programmers that are worthy of naming so that we can think about them.

Super Man: Superman flies in to a Big Disaster. He battles the enemy at all cost. He destroys everything in the vicinity. He doesn't write or run any tests. Instead, once the enemy (a huge bug or problem code), s/he flies away leaving broken streets, fire hydrants spraying water, cars destroyed, and walls lasered. I guess the insurance companies clean up after him?

Yoda: Yoda is a powerful and wise user of the force. However, he is hesitant to act. He is often mysterious, causing others to wonder whether he will actually do what needs to be done. He speaks in riddles. He's still a fun and interesting person -- but his hesitation paves the way for Emporer Palpatine to take control. In summary, you can be too cautious. Trust

Pigpen: Best Practices, Hogwash! Interfaces are for sissies! Symptoms: Classes with no state; Classes with 104 methods; Many copy/paste methods

Inspector Gadget: Big new project?! He’s got some untested tools that would be perfect! Does not care about risk. Loves new technology. Knows all the newest jargon. Doesn’t so much care whether technology is “vetted” or “a good fit.” Finds solutions without problems.

Batman: Motivated by culture, guilt (or other), suffers silently. Will sacrifice anything for the team: Work long hours, Will strive for any impossible / arbitrary deadline; enables / hides poor management; poor work/life balance;

Road Runner: Accomplishes a LOT of coding -- so much so that s/he is the biggest contributor on any project. Maybe not the absolute cleanest code, but will knock things out and get to the next task. Becomes very popular with management, not very popular with those left behind to clean it up. This developer then struggles to move on because they're always called back to work on or explain sections of their own code. Likely to get burnt out. Developers who move too quickly are actually a larger risk to long-term success than developers who move too slowly. A video about being a 10-x developer focused on output vs outcome (and a roadrunner is obviously focused on output.)

See my presentation on common development project issues.





Comments:

Fgrsfleex said: viagra w dapoxetine overnight best price for viagra safe generic viagra

Stevenloobe said: buy zithromax zithromax https://worldrx100.com where to get zithromax

Stevenloobe said: average cost of generic zithromax zithromax 500 without prescription https://worldrx100.com buy cheap generic zithromax

golden goose sneakers said: I have to express thanks to this writer for bailing me out of this particular instance. After surfing around through the world wide web and meeting ways which were not productive, I assumed my life was over. Existing devoid of the solutions to the difficulties you've resolved through your short article is a critical case, as well as the ones that might have adversely affected my entire career if I had not come across the blog. Your own expertise and kindness in touching the whole thing was useful. I'm not sure what I would've done if I had not come across such a step like this. I am able to at this point look forward to my future. Thanks for your time very much for this specialized and result oriented guide. I will not think twice to propose the website to any person who ought to have tips on this subject. golden goose sneakers [url=http://www.golden-gooses.com]golden goose sneakers[/url]

yeezy 380 said: I have to show some thanks to you just for bailing me out of this particular trouble. Because of looking out throughout the internet and getting suggestions which were not helpful, I was thinking my entire life was gone. Being alive minus the solutions to the difficulties you have sorted out by way of the short article is a serious case, and the ones that might have badly affected my career if I hadn't encountered your blog. That ability and kindness in playing with the whole lot was excellent. I am not sure what I would have done if I hadn't encountered such a step like this. It's possible to now look ahead to my future. Thank you very much for this professional and results-oriented guide. I will not think twice to recommend the website to anybody who requires care on this subject. yeezy 380
Back