Don’t think I saw these mentioned so here ya go:
And this is extra but grab your friends and family and play some couch co-op. It can help get your mind off things and just enjoy being in company of loved ones.
Aand if you want to eventually find something that will keep you hopeful in the face of despair, in a healthy way, I recommend the first part of Honkai Impact 3rd. It’s long, has lots of depressing moments, enough to make fans call it Depression Impact. The story touches on themes of existential horror, suicide, duty, death of loved ones, humans who have no morals and believe that all rights and wrongs as transient, cosmological threats, etc. Despite all that, I’d actually say that it’s a story about hope, and what can lay the foundations for hope. It’s definitely fan-service-y, and it’s a gacha game, but very much ignorable and playable without investing any money in it. It’s also made by a Chinese company, but maybe that can help with recalibrating perceptions on Chinese people, instead of what we’ve come to know through their government. Of course, if you’re susceptible to gambling addictions, please feel free to ignore this recommendation.
This was pointed out in another comment but I will basically echo it to just give that call a boost: Point your instructor to well-regarded sources for introversion and extroversion, and let them know that the labelling in their note is not only inaccurate, it falsely attaches a wrongly defined word onto problematic behaviours that have nothing to do with what introversion and extroversion is, which is not good because it propagates a false narrative.
If your instructor doesn’t seem cooperative and insists on being correct, talk to other instructors that you trust, or even go to those with more authority to tell them about the issue. If you can’t get anyone to actually do something, I suggest you change schools immediately, and call the school out for what they did.
Maybe it’s just one of those days, but I have no tolerance for this sort of false narrative being spread, even if the original intention is innocuous, and especially in a school. Being forced to act in a certain way that deviates from one’s personality to not be perceived as a problematic person, especially over a badly-informed opinion, can have lasting negative consequences to children and adolescents. I’m tired of seeing introverted friends and family members suffer over the fact that they’re introverts, to the point where they will deny being an introvert and even echo these sorts of statements in order to blend in.
The fact that Reddit can still tell you that the user deleted their account is proof that not all of that user’s data in their systems are deleted. It may just be a flag in an account that marks them as “deleted”, and so whenever data about that account is being retrieved, their API server will look at that flag, and tell the recipient that the account is “deleted”. People in the software industry calls this “soft deletion”.
It seems like the author thought stack traces are underrated because people don’t like exceptions and don’t always
throw
. It seems like they don’t understand why people don’t like exceptions, and think that stack traces should be there for every case where the author thinks should be an exception, and ties the desire to avoid exceptions to some strawman use case — a nice looking output — and called it “modern error handling”.Error / exception handling is separate from stack traces. You don’t need to have an exception to have a stack trace, and stack traces aren’t just used for exceptions.
They also seem to not understand why people make do without stack traces in a microservice architecture. That’s simply not true. First off, you can still get stack traces of individual services. And secondly, if you build your services to accept, eg, something like a tracing ID, and print it along your logs, you essentially have a stack traces across services. In a web service, you can track the work done by all your systems for a single request from the client.
Now, onto why exceptions are somewhat disliked. Let’s just get the simple stuff out of the way: they’re generally bad for performance; they’re invisible to the method caller until they run into the problem, meaning you can’t ever ship updates that you’re confident won’t fall over disgracefully; try-catch hell, etc.
For a slightly more philosophical answer, why aren’t your exceptions just cases you need to handle? The try-catch pattern essentially builds up a separate channel of logic where your program needs to operate in but is expressed or recorded in very fragmented ways, forcing devs to have to pop open every function to look at why something is thrown, and hope that somewhere down the stack, no new exceptions are being thrown and not handled. The logic behind exceptions becomes second-class citizens that programmers can easily forget, instead of being front and centre. Can’t divide by 0? Tell me instead of setting me on a separate handling path. Why should I try-catch every single method call, or even property access? Don’t wait for the user to hit the call and just tell me that something is supposed to be impossible, or if I should handle the case where it doesn’t hold any values, right as I compile (dynamic languages can’t really do that).