DEV Community

Cover image for Monolingual Maestro or Polyglot Prodigy: Which Programming Path Resonates with You?
dev.to staff for The DEV Team

Posted on

Monolingual Maestro or Polyglot Prodigy: Which Programming Path Resonates with You?

Would you prefer to possess unparalleled mastery in a single programming language or a diverse repertoire across multiple languages? Which path ignites your coding spirit? What are the potential advantages and challenges of each approach? And how do you think your chosen path would shape your coding journey?

Follow the DEVteam for more discussions and online camaraderie!

Top comments (4)

Collapse
 
kaamkiya profile image
Kaamkiya

I am definitely a polyglot dev. I started by decided to try a ton and stick with what I like, but now I have like 6 things I like. (Go, C++, Python, x86_64 assembly, ...).

It helps when trying to learn new things, but your skills are lower than that of a monolingual developer.

Collapse
 
fen1499 profile image
Fen

I'm a polygloth and at first I thought it would be better but turns out it makes it harder to get a decent job or I end up getting assigned to something that I'm not really into but still capable of.

The good part about it is that I'm usually the one that can see solutions other people can't and learn things very fast.

Collapse
 
jmfayard profile image
Jean-Michel πŸ•΅πŸ»β€β™‚οΈ Fayard

I thing there are not really wrong paths, even if you learn a "bad" programming language you can and will easily course correct

My path was to try multiple languages then I settled down on one.
I learned from each one I've learned, even if I didn't use it much.
There are plenty of transferable skills and concepts.
Learn haskell, go back to Java but write it a bit differently.

Then at some point I settled down on Kotlin because it was very productive for most things I wanted to do with a programming language.
Even if Rust or whatever were marginally better, the existing skills I had make Kotlin the obvious choice and I focused instead of aspects that made bigger impact, and usually those were non technical things.

Some comments may only be visible to logged-in visitors. Sign in to view all comments.