@tempest thanks!! 💜

this entire project Sure Is Something and has company-wide notoriety for having been a terribly managed shitshow. it’s now common knowledge that everything is saddled with tons of technical debt despite not having been released yet

@ilobmirt

admittedly, it’s because she has no idea what anything does and wanted to alleviate her anxiety related to the project’s impending deadline

i have no idea what anything does either but i’m okay with that

@catgirl_so as the supreme knower of [thing] eternal, one must enjoy the benefits of the position responsibly. which is say constantly with no interruption, especially not for questions of any sort.

Hover to show content

@rowan correcting {the (now former) world expert on [thing]} about [thing] makes one the new expert on [thing]. rebuff any questions about [thing] with "it's too political to ask questions"; this ensures one cannot be [corrected, dethroned]. secure in the knowledge of one's place as the supreme knower of [thing] eternal, take a cozy nap.

@Shivaekul aw, thank you! 💜 it’s not too bad, i’m going to take most of next week off to compensate :3

her exact phrasing was “it’s just too political right now” (in reference to sending an email to another company that we hired to checks notes answer questions)

my work week so far

• already at 40 hours
• had to correct the “world’s leading expert in [thing]” on [thing]
• rewrote a sql query that originally took 3 minutes to run, it now takes 3-5 seconds
  • to be fair to the previous implementer, he had to write it without knowing anything about the data
  • the person who made the database couldn’t write it because he “hasn’t played with the tables much”
• was loudly talked down to by my boss because she’s upset that her attempt at replacing my software with something made by chatgpt didn’t work right
  • this conversation started because i had a question and was told that it’s too political to ask questions

@kirakira side note: strict mode fixes the globalThis issue in constructor functions

@kirakira both of them produce an Object, which is the same one you get when you use the object literal ({ foo: 1 }) syntax. these are all mutable by default (unless if you use one of the metaprogramming functions like Object.freeze or, more specifically, Object.preventExtensions which stops new properties from being added to an object)

@kirakira ES6 classes are not exactly the same but bear significant resemblance to constructor functions. for sake of simplicity, it’s easiest to say that ES6 classes are syntactic sugar on top of constructor functions. the major difference is that classes throw an error when attempting to construct them without the new keyword while a constructor function will have a corrupted state (notably, it will inherit the globalThis as its own this).

the following declarations are nigh-identical

class bitchA {}

function bitchB() {
  if (!new.target) {
    throw new TypeError("calling bitch constructor without new is invalid")
  }
}