• 1 Post
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle




  • Been there many times. Had one case where support had to through the reseller who sold licenses in our country. Actual people who knew what they were talking about was tier 3.

    We had a bug and were trying to report it and get a fix or workaround. Just told no, we’re doing it wrong. After a lot of back and forth we had to pay for an “expert” to fly over and show us what we were doing wrong. Turns out he wasn’t an expert, he was a salesmen. Made a demo for us on the flight and the first time he ran it was in our meeting room on projector.

    Failed in exactly the way we had been saying. It was very satisfying.

    Finally he phoned the dev team who confirmed the docs were wrong and we couldn’t do what we were trying.










  • I exclusively use CLI, it’s not ego at all, I simply find typing what I want to be quicker than clicking buttons. I’ve written a bunch of aliases to automate my common workflows.

    When I need to help a colleague who’s made a mess of something, I can easily give them the command to fix it rather than finding the right options in their GUI of choice and it’s often because of some broken abstraction in the GUI they got into the mess in the first place.







  • We use SQL Server at work and I really don’t get why. It’s so expensive. We’re hosting it on AWS as well. I can’t remember the numbers but it’s several times more than a similarly specced postgres and we’re only using Standard edition.

    I don’t think we’re really using any features that would stop us moving over, it’s really just inertia and in-house knowledge.


  • I’m working on migrating a lot of old .Net Framework code right now, we’re generally going with a complete rewrite but that’s more to do with poor architectural decisions and the fact a lot of it is VB rather than C#.

    It’s pretty impressive that code largely written up to 20 years ago is now running on a modern OS, and it’s using the latest Framework 4.8 with all the latest security updates and I can open VS2022 and hit run and it builds and runs fine. Our issues are the maintainability of the code and how it was written rather than the framework itself.

    Meanwhile, a few years ago now, I had a web project written in typescript, it was only about a year out of date and npm install failed. Turns out one of dependencies needed to build something with python2, updating that needed a new version of webpack and that broke something else that never got an update to the newer webpack. Installing python2 didn’t work either I think but I can’t remember why.

    There’s systems I wrote for .Net over a decade ago that I can guarantee are still running in production and haven’t been touched in all that time.

    In short, I think I’m agreeing with you. It’s painful but it’s possible.