DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

Yet Another Take on Software Developer Archetypes

In this post we take a lighthearted look at some different types of developers. Which one best matches your personality?

Michael Mainguy user avatar by
Michael Mainguy
·
Feb. 17, 17 · Opinion
Like (1)
Save
Tweet
Share
3.25K Views

Join the DZone community and get the full member experience.

Join For Free

If you search for Software Developer Archetypes you'll find a large number of perspectives on this ranging from serious and helpful to lighthearted to frankly kinda mean. I'm going to give a lighthearted example of core Archetypes I find when dealing with software developers.

The Squirrel

These developers are happy to jump between frameworks, languages, and design patterns willy-nilly, and will be running 1,000 miles per hour toward a "Haskell event processing framework to render static HTML files" and after 3 weeks/months, suddenly pivot, turn 135 degrees, and implement the remaining 10% (which will only take a couple days) in Ruby on Rails. By the end of a project, there are so many frameworks, dead ends, and partially done solutions that no matter what the original design was their immediate solution to all problems is to "rewrite it in...something else."

The Sloth

These are almost diametrically opposed to squirrels, they often know "one thing" (though not always), but the defining feature is that it takes 3 weeks to implement "Hello World" in a language explicitly designed to produce "Hello World" apps. You can immediately spot these folks because the "remaining estimate" tends to either stay at "two weeks" (or some other random time amount), or you have to pad their estimates by the factorial of their original one.

These developers are a middle ground in velocity and direction change between the first two, but are characterized by always having a "go to solution." If they're a "Java developer," coding something in Groovy will "blow their mind" and they'll insist this new arcane "dynamic mumbo jumbo" is completely useless. They are often religious defenders of "their way of doing things" and often have "anything you can do in 'A' I can do (maybe better, maybe not) in 'B.'"

The Duck-Billed Platypus

While interesting creatures, these developers are easily spotted when you look at their code and you spend most of the time scratching your head thinking, "WTF?" They are often adept at stringing together inappropriate design patterns and tools to produce solutions that just don't make sense from any reasonable perspective. At the end of the day, their code may "work," but it is a nonsensical assortment of odd parts glued together seemingly ad-hoc.


Software developer dev Archetype (information science) Software

Published at DZone with permission of Michael Mainguy, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • A Beginner's Guide to Back-End Development
  • Integration: Data, Security, Challenges, and Best Solutions
  • Debugging Streams and Collections
  • The Quest for REST

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: