• 0 Posts
  • 15 Comments
Joined 11 months ago
cake
Cake day: May 7th, 2024

help-circle


  • I’m thankful I don’t do software dev (I did two years as a working student, that was enough), but working in Data Engineering / Analytics* doesn’t make things better. I’ll overengineer the database, ETL and reporting, define a dozen measures I’ll never use, prepare a dozen ways to slice and view the data I’ll never look at and build a whole data warehouse I’ll never look at.

    Eventually I remember that it exists, realise that I’ve answered all my questions by directly querying the database, except for “What am I running out of?”, which I answer by looking in the cabinet because I never update my inventory anyway.

    *I don’t even know where the line is anymore and how much of my responsibilities is on either side of it



  • He uses a pencil, paper and a mechanical calculator to tally up the bill, which I absolutely understand when your career is in IT.

    When the alternative is either having to search, evaluate, compare, select and configure an application for that purpose that you’re never quite happy with, or to scope, design, develop, test, deploy, maintain, eternally find things you wish you’d done better, refactor, realise you’re spending your free time on doing more of your job, regret your life choices, resolve to only make this last improvement and then call it good enough, renege on that promise to yourself a week later, burn out, curse that damn app for ruining your hobby…

    …yeah, using the most trivial low-tech solution possible does look rather sensible.


  • My new data structure:

    Given a heuristic for determining data quality, it homogenises the quality of its contents. Data you write to it has pieces exchanged with other entries depending on its quality. The lower the quality, the higher the rate of exchange.

    If you put only perfect data, nothing is exchanged. Put high quality, you’ll mostly get high quality too, but probably with some errors. Put in garbage, it starts poisoning the rest of the data. Garbage in, garbage out.

    “Why would you want that”, you ask? Wrong question, buddy - how about “Do you want to be left behind when this new data quality management technology takes off?” And if that doesn’t convince you, let me dig around my buzzword budget to see if I can throw some “Make Investors Drool And Swoon”-skills your way to convince you I’ll turn your crap data into gold.









  • Idk how that person’s IT works, but in mine, that would probably warrant a lot of paperwork. The techs would have to pitch the change to client management, client management would have to pitch it to change management and provide test results to show it has no side effects, then deal with the techs complaining about the uptick in tickets about slow boot times or people justifying never shutting down or restarting with it taking so long to boot.

    Not that they’re actually slow, our users are just super entitled. I got to observe the rollout of automatic screen lock for security reasons, and the ensuing pushback. The audacity of having to reenter your password if you’ve spent more than ten minutes doing nothing!

    Security even managed to push for reducing it to five minutes after some unfortunate incident… but it got reverted for reasons you can probably guess. Hint: shit always flows downward.


  • I work in our service department myself (not as support tech though), but obviously, all tickets are supposed to go through 1st level. I don’t wanna be the dick skipping queue, so I did then one time I had an issue.

    There’s a unique feeling of satisfaction to submitting a ticket with basically all the 1st level troubleshooting in the notes, allowing the tech to immediately escalate it to a 2nd level team. One quick call, one check I didn’t know about, already prepared the escalation notes while it ran. Never have I heard our support sound so cheerful.