• 0 Posts
  • 40 Comments
Joined 2 years ago
cake
Cake day: July 13th, 2023

help-circle
  • Ok, so imagine you were expected to strip naked, cuddle up to someone else who was also stripped naked. Imagine you are expected to pretend to have very real and intimate feelings with one another and in the process do very intimate things with them like kiss, touch their body, and simulate penetrative sex all while being in a room full of people watching you do this and with cameras recording the entire thing with the intent to show it to the world. That in itself would make most people at least a bit uncomfortable.

    Now, maybe you also feel uncomfortable because you have a spouse or significant other. Maybe you know this other person well and they are platonic friends. Maybe they are barely an acquaintance, just a work colleague. Maybe you have romantic feelings for this other person. Maybe you hate them. Maybe the other person has made advances on you. Maybe you have a history of being assaulted or of being used sexually. Maybe you are self conscious about your body. For any number of very justifiable reasons, this situation can be anywhere from slightly to very uncomfortable for either or both actors, even scary in some situations.

    The intimacy coordinator is not a sex coach. They are there to make sure the situation is safe, consensual, and as respectful and private as possible for both actors, and to see that their needs are met for this very stressful circumstance to minimize discomfort. They also make sure that nobody on set oversteps boundaries, that the actors’ rights are upheld, act as the single point of contact between the actors and production to minimize uncomfortable conversations and miscommunication. They will be involved in choreography of the scene, but not as a coach so to speak, but rather in mentally preparing and making exactly clear the understanding for all parties what is going to happen, giving everyone the time to process and veto plans if necessary.






  • Horseshit. Computers aren’t tools for a software engineer. Computers are tools to an administrator, an accountant. Computers are the sandbox you are building castles in as a software engineer. If you don’t understand the system upon which you build, its abilities and features, its limitations, it’s dependencies, you are going to make some stupid mistakes.

    You need to understand discrete mathematics as a consequence of computer computation. You need to understand parallel processing and threading for muli-core processors. You need to understand networking, package management, security vulnerabilities, etc. from different architectures and protocols. And it ALWAYS helps to understand the very basics of a computer’s functioning, from hardware, CPU architecture, machine code, assembly/low level programming, memory management, etc.

    print('Hello, World!) is day one shit for a reason. Programming language and logic is the basics. The real expertise comes from your 3rd and 4th year materials. Databases, architecture, theory of computation, discrete mathematics, networking, operating systems, compilers, etc.



  • This shit sounds like when your mom tells you that the Facebook printed out her bank statement on the fax machine. I’m not smart enough to even guess how you did something dumb enough to make that happen.

    How bad are you at writing queries? How does your hard drive overheat even under 100% load? Do you have it smothered under a blanket? Did you crack it up and expose it to cheeto dust? What does running a query on your, presumably, remote database even have to do with your harddrive in the first place? Are you trying to copy the entire database locally to a laptop? Do you know how to tie your shoes yet, or are you still on the velcro?