4 ms·
I too work with similar tech. It "just works" and fulfills requirements. > Our Azure bill now cost as much as an average European developer. > The main reason
by dvaun 6y ago
I too work with similar tech. It "just works" and fulfills requirements.
> Our Azure bill now cost as much as an average European developer.
> The main reason is a slow horrific monolith.
Would changing the tech either improve revenue and/or reduce costs? That is how I would suggest changes (if it applied where I work)
Edit: On the topic of working with boring/old tech...one thing that I've been doing is learning more of the internals of the environment I'm working in. For example, with C#, I've decompiled libraries and read through source code to learn new APIs and how some important functions are implemented (e.g. Crypt32 API).
I'm not sure if that would be interesting or if you would consider it a good use of your time.
- Gibbon1 6y agoI feel like OP might be in the situation where he's just skipping a huge amount of BS. A lot of shiny flashy stuff bring built today is basically unmaintainable garbage wrapped in gold colored tinfoil. You bring up C#. Microsoft is doing a big push towards a unified cross platform set of tools based around C#. Might make sense for OP to learn than because it's just a one step from what he's using now. Best code is being able to use netcore alongside the older tech and it interops fine. That said I'm out of my element here.
- non-entity 6y ago> For example, with C#, I've decompiled libraries and read through source code to learn new APIs and how some important functions are implemented This can be fun lol. I had huge performance issues with a mildly disliked (paid) library where the program would eat all the RAM my machine had. Curious as to what it was doing I threw the library in dotpeek and everything had been horribly obfuscated :)