Why, a hexvex of course!

  • 0 Posts
  • 87 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle

  • Coding is a very… emotional activity. We get a bit salty sometimes.

    I remember commenting a particularly bad routine with “Lasciate ogne speranza, voi ch’intrate”.

    There are also phrases such as “by the process of offending god, this somehow outputs…” and “This block was written by someone whose sanity was not so much questionable as it was entirely reprehensible - but it works”.

    I also remember doing a search and replace of every instance of the word “fuck” with “[fornicate]” when bringing someone new onto a project.





  • At first it all seems normal, every now and then a random sound effect is replaced by ominous hooting. Every hour, on the hour, a green owl flashes on the screen for a frame or two, it’s eyes boring into you before vanishing. Once every 50 or so times it pumps your volume up, selects speakers as output and let’s loose a screeching hoot. Random popups slowly ramping up “Restart your streak today”, “Where did you go?”, “Duo misses you”. At first just once or twice a day, but steadily increasing in intensity till it’s one every 23 seconds.



  • HexesofVexes@lemmy.worldtoScience Memes@mander.xyzdo crimes
    link
    fedilink
    English
    arrow-up
    43
    ·
    2 months ago

    Short Answer - Universities

    Long Answer:

    To get and hold a job as an academic, you must continually produce “high quality research”. To get the job, in the first place, you must also be seen to do this.

    “High quality” is often metriced by universities to mean “published in high impact journals” and “well cited”. This metric is known to be faulty, but universities really dislike change.

    So, to get a job, you have to give up your rights to your research, and to keep your job, you have to do likewise.

    Worse, in the current financial climate, academia is seeing unprecedented cuts, which further entrenches this issue.









  • Worse - pulling data from a web page, then using the power of pure jank to parse this input, and then invoking a sheet of reference string builders to construct formulae and execute them using too damn many @indirects nested into vlookups before finally adding in date aware data reveals, because no excel abomination is complete without trying to parse dates.