I know there’s this notion that you shouldn’t label yourself as a “.Net dev” or a “Python” or “Java” dev because programming languages are just tools that have areas in which they shine. Nothing’s wrong with that statement because it entirely true but I believe in picking something and mastering it so if someone wants a python dev or java dev they know where to look and what to expect. Nothings wrong with being a jack of all trades master of none because the industry needs people like that, but if you don’t have to then don’t.

  • 2
    I will try and master whatever language I am currently paid to support. Knowing full well that the next job may be a completely different language. Also knowing I may lose a ton of knowledge when I switch.
  • 4
    Idk, I can't agree with that attitude as a rule of thumb. This is how people like java haters emerge. When people can write code in a language but have no clue how its guts are working these people start spreading false myths about them.

    I say learn 1 or 2 languages in-depth and skim over the others. Feel free to share your opinions about those 1-2, but keep it to yourself about the rest
  • 0
    C# and .net are not equivalent.

    Saying you're a c# dev could be a bad idea. Languages are easy and simple to learn for the most part, and to master them is generally the process of memorizing the standard library and the most effective ways to use that language to do common tasks.


    Saying you're a .NET developer is definitely a huge plus. Saying you know how to use an entire ecosystem and that you have experience with it is incredibly important because most ecosystems don't have very transferrable skills like languages do. A windows and .net guy would get completely stuck 3 seconds into Android development. An iOS developer wouldn't have the first clue what to do with an Angular project.

    These are the things that make up your identity as a developer.

    Languages simply enable your identity, and are largely transferrable.
  • 0
    I started working 2 years ago for agencies and was very passionate about learning all the frameworks. That quickly faded away as now I don't have the energy to learn something new after work. I may be good for 10 years with my current stack but it feels kinda scary when its the only stack I've worked with and making a switch would almost be like starting over.
  • 1
    .NET dev since 1.1 and I tell that people.

    I know many other languages, but I don't want to deal with them on daily basis. I know pretty much about .NET internals and such. Learning that much of another language takes years of pain.
    Frameworks and Tools that give that much freedom have tricks and flaws that you will learn over time.
    A jack of all trades and master of none is for example full stack. Backend and Frontend are so complex nowadays, that full stack devs basicly are always bad.
    My 2 cents on this. Btw. I do this over 10 years professionaly and as a hobby about 23 years now.
    Starting with a T knowledge shape and expanding it later is not a bad approach.
Add Comment