3 ms·

I've been working at a .Net shop for the past year. There a tendency to see encyclopedic knowledge of OOP design patterns almost as a form of currency. C# itse

I've been working at a .Net shop for the past year. There a tendency to see encyclopedic knowledge of OOP design patterns almost as a form of currency. C# itself is an ok language. It's just the culture around developing web applications with .Net that's painful. At my workplace, we're currently transitioning from C# to Typescript. As you can imagine, it's not pretty. Key to this is how Microsoft have managed to encode much of the misdirection inherent in .Net webapp development, into the Azure API surface. I dunno... Now I sound as dogmatic as the community I'm accusing of dogmatism...

decafninja 6y ago
I am curious how that C# -> TypeScript transition is going, and how it is structured. I was in a project that involved a team of mostly traditional enterprise .NET devs writing a greenfield app in Python (language choice mandated from up top). The result was basically something that was designed like a dogmatic enterprise .NET application, only using Python abused and wrangled to fit that style. After that project was done, for subsequent work, the team split into two camps - one camp that despised being forced to work with Python and continued to write Python in enterprise .NET style, and one camp that decided to explore more about Python and try working in more "Pythonic" style. Code review sessions were full of emotions and drama. Pretty much everyone in the first camp eventually left, either for other internal teams that were still working in .NET, or for other companies.
- dynamite-ready 6y ago
  Yes. This sounds a lot like my current experience, except for the language involved (TS in my case) and the team split (I'm the one with less .Net experience). I like to think I'm experienced enough to see it as a valuable opportunity to learn something that's not just about code and product... Anyway, everything else you mentioned sounds uncannily similar. Makes you wonder how such a culture develops. The only constant appears to be Microsoft development tools, curiously.

decafninja 6y ago

I am curious how that C# -> TypeScript transition is going, and how it is structured. I was in a project that involved a team of mostly traditional enterprise .NET devs writing a greenfield app in Python (language choice mandated from up top). The result was basically something that was designed like a dogmatic enterprise .NET application, only using Python abused and wrangled to fit that style. After that project was done, for subsequent work, the team split into two camps - one camp that despised being forced to work with Python and continued to write Python in enterprise .NET style, and one camp that decided to explore more about Python and try working in more "Pythonic" style. Code review sessions were full of emotions and drama. Pretty much everyone in the first camp eventually left, either for other internal teams that were still working in .NET, or for other companies.

dynamite-ready 6y ago
Yes. This sounds a lot like my current experience, except for the language involved (TS in my case) and the team split (I'm the one with less .Net experience). I like to think I'm experienced enough to see it as a valuable opportunity to learn something that's not just about code and product... Anyway, everything else you mentioned sounds uncannily similar. Makes you wonder how such a culture develops. The only constant appears to be Microsoft development tools, curiously.