It's mainly what its used for, if you want to make pretty graphs and keep track of materials at your factory maybe you pull out .net if you want to do something interesting you use pretty much anything else. I know tons of people make a living with it, but I don't understand the passion for the language.
What about returning a dynamic object? You see a method returning "object" (unless it's yours) you immediately starts to feel awkward (should I cast it to something?).
Or what if I want to check if a property exists in a dynamic object? Catch the exception? Use the ExpandoObject? Will this affect performance?
What about local delegates?
I find more and more uses for C#'s reflection all the time. I have a project that is built almost 100% on it. Tagging things with attributes, reflecting over them, slicing and dicing all of the available data in all kinds of different ways.
I can't imagine trying to do such a thing in JS, which provides so little information about exactly what I'm reflecting over. And it's so clunky. Some things you can typeof, some you have to instanceOf, such that you basically end up doing both all the time.
With JS, I know that I have a bag full of things named something. I have to do my own work from there to find out if they are methods or properties or fields. In C#, I can just ask it to give me all of the properties. Oh, but stick to just the public ones. Or skip any that have an attribute named "Exclude" tagged to them.
Yeah, I have no idea what people are talking about that JS is better for reflection. That's just bonkers.
This can be a double edge sword. you enjoy your new responsibilities? good for you. not everybody wants to get more and more on their shoulders until the point of realizing that there ins't much time for that little thing called life. Also, most people who get promoted/raised around me end up working much more compared to raise they've been given.
Personal experience - in every single work I've done (roughly 10 customers/employers, perm+consultant) in 3 different countries, there was/is always room to grab more responsibility, more tasks etc. State of IT usually just a variation of a term MESS, with some technical debt here and there, everywhere. You work harder, solve more, take more responsibility and your career progresses along (or you go to place where it does faster).
But with this might also come 9-10 hours at work instead of 8 (plus lunch), company phone which is there just to remind you of the work when you're not in, maybe more weekends screwed up and so on. Even in otherwise very work/life balance oriented employers.
Want another advice? When having a formal talk with your boss, tell him you want a raise, but you don't want it for free, rather bringing added value. Define clear terms what is expected from you to get there, fulfill them and watch the magic happen :)
I've spent more time learning git than I have spent learning all other VCS combined, of which there have been at least a few in my history. My mastery of git is significantly less than that of any other VCS I've used. Less powerful VCS are easier to use, and that can be a feature.