Is it a good idea to use many programming languages and technologies in the beginning of your career?

View other answers to this thread
Start a personal dev blog on your domain for free and grow your readership.

3.4K+ developers have started their personal blogs on Hashnode in the last one month.

Write in Markdown · Publish articles on custom domain · Gain readership on day zero · Automatic GitHub backup and more

Haris Secic's photo

I had more turbulent switches than you. Started with vanilla PHP, JS, HTML, CSS and after 1+ years switched to Java, Spring, JSF, AngularJS then used it for about 3 years switched to Node.js and Android and after 8 months went to ColdFusion and C#. Then again, after 1 year of that switched to Java and some Scala and after 8 months to C#. After ~10 months of C# switched to Java, Kotlin, Groovy combination and been working with it for 1 year now.

  1. I learned about concepts of development and different styles and can pick a nice tool for some tasks quite easily. This is huge plus for consultancy when job needs to be done quickly.
  2. I don't care anymore about this or that being better and ignore such posts. I can learn other languages much faster than before as I'm not stuck with only 1 style of development or 1 technology.

Problem is that I see a lot of friends being experts at some things and I cannot put it on a paper and companies usually avoid such developers. Reason is that they all want experts. (as you mentioned)

Because of my destiny to quit and get fired frequently I never had time to learn some stuff I wanted so I lack things like being able to always tell which pattern is best here and such. Although I don't really care it's quite required to be like that when looking for a job the same as with years of experience.

Now all that said I think technologies will be hard to learn when switching, it's much easier to learn what is what in one language and understand where it got inspiration from and why is it like that. Then learn a lot of different languages, tools, frameworks to understand different approaches to the problem.

Currently I got into position as System Architect (consultant) by accident. I work for a client in their offices which is not Software Company. Now those guys only present you feature requests and you do your best to make it good. And as soon as you get out of software companies you see that we should serve rest of the people by automating their work and making it way easier. Rest is not so much important

Show +2 replies
Saikyou's photo

You can check the latest information about Japanese Igaming here