3 ms·

> In the end though, its absolutely about culture and Enterprise IT will suffocate you no matter what language. The one thing I really worry about is being stu

by kzisme 9y ago

> In the end though, its absolutely about culture and Enterprise IT will suffocate you no matter what language. The one thing I really worry about is being stuck in the MS stack for years and not learning as much as I can (or want to). I still ~really~ dislike the term "IT" or "IT Dept" - since the majority of the time you are seen as some guy who works on computers or can fix your problem. I just don't want to become stuck.

wvenable 9y ago
Don't worry so much about the quantity (learning as much as you can) than the quality. You could basically kill yourself trying to learn every modern piece of technology. It's not really worth it -- it'll be obsolete before you get a chance to actually use that knowledge. It's one thing to be stuck with terrible non-moving technology but .NET is a good technology stack that is progressing in the future nicely. Conceptually you'll be fine.
- kzisme 9y ago
  Yeah I just worry that being tied to C#/.NET that I'll be stuck with the same sort of job (and the knowledge won't transfer to other stacks)
  - pjmlp 9y ago
    You will always be stuck to a certain stack, specially in countries like Germany where what HR department cares about is what language/tooling you did use during the more recent years before the interview. Usually knowledge learned on side projects are not taken seriously by them, as they weren't on the job. Oh and they love paper (certifications of all sorts). Algorithms and data-structures always transfer to any stack. Learn the CS mathematical foundations of them. A good way to avoid being stuck with a certain stack as you put it, is working for a consulting company. It is way easier to jump stacks when switching projects than than trying to convince random HR department of what you actually know.
- kzisme 9y ago
  Yeah I just worry that being tied to C#/.NET that I'll be stuck with the same sort of job (and the knowledge won't transfer to other stacks)

by kzisme 9y ago

wvenable 9y ago

Don't worry so much about the quantity (learning as much as you can) than the quality. You could basically kill yourself trying to learn every modern piece of technology. It's not really worth it -- it'll be obsolete before you get a chance to actually use that knowledge. It's one thing to be stuck with terrible non-moving technology but .NET is a good technology stack that is progressing in the future nicely. Conceptually you'll be fine.

kzisme 9y ago
Yeah I just worry that being tied to C#/.NET that I'll be stuck with the same sort of job (and the knowledge won't transfer to other stacks)
- pjmlp 9y ago
  You will always be stuck to a certain stack, specially in countries like Germany where what HR department cares about is what language/tooling you did use during the more recent years before the interview. Usually knowledge learned on side projects are not taken seriously by them, as they weren't on the job. Oh and they love paper (certifications of all sorts). Algorithms and data-structures always transfer to any stack. Learn the CS mathematical foundations of them. A good way to avoid being stuck with a certain stack as you put it, is working for a consulting company. It is way easier to jump stacks when switching projects than than trying to convince random HR department of what you actually know.
kzisme 9y ago
Yeah I just worry that being tied to C#/.NET that I'll be stuck with the same sort of job (and the knowledge won't transfer to other stacks)