@Zenith said in I work for Microsoft:
barely-documented black box on a forced deprecation/abandonment treadmill dropping features/compatibility left and right
Yeah that describes the entirety of what I work with every day.
My most productive times were working on C# with SQL Server on VS 2012 and was churning out features at a very fast pace. Had this gig for a couple years and the kind of things we worried about were always oh shit how do we handle this piece of business logic, how do we handle the other thing, how do we architect the application and nothing ever related to the actual language/framework itself.
With .NET Core there seems to be a lot of battling with the language. I've had hour long discussions with colleagues as to what sort of config file should we use to read from at runtime and what you want to use today sure as fuck gets depreciated tomorrow.
I'm hooked to this because of C# and if I find a better alternative to building web applications with a statically typed language I am jumping ship. I've been giving these folks the benefit of doubt for so much time and I've lost patience. If I go back to AWS, which is a UX nightmare and is a pain to work with, but at least works consistently IMO.
Engineers at MS don't know why certain things in Azure work the way they do. SMH.