km89

km89 t1_je8koaz wrote

>modern self-care ✨ mentalities of being okay with things like throwing away the majority of your personal responsibilities for the sake of mental stability.

Do you need a mop to clean up the condescension you just dripped all over the floor?

Dude's been hospitalized for weeks. This is either a suicide attempt or fallout from his stroke, or both. Question his current fitness to hold office all you want, but throwing away your mental health for the sake of impressing people who would approve of that is just fucking stupid.

34

km89 t1_je1v2k6 wrote

It's divided up, and any remaining space is filled with zeroes.

You may have heard the terms "bit," "byte," "megabyte," etc. A bit is one digit; a byte is 8 digits, and multiples of that are named with their SI prefixes ("kilobyte", "gigabyte", etc).

So when the computer reads, it's reading in multiples of 8 digits. In your case, the computer might read one byte that has the binary data "1001" stored in it. To the computer, this would show up as "00001001", but 2 would just be "00000010" and 1 would be "00000001."

Note that I'm talking about bytes for simplicity, but computers generally run off a "word" size (which is itself some multiple of 8 bits), and sometimes the first digit is flipped to 1 even if the data doesn't fill the whole space. You can ignore that for now, that's not important for this answer. Specifics aside, the point is that the computer is reading specific numbers of digits at a time and the data is padded with 0s if it doesn't fill all of the digits the computer's reading.

1

km89 t1_jaaaztl wrote

The way he explains it is actually pretty good.

Replacing it with actual numbers:

You live in 2020.

You go back to 2000.

In that case, events in the past (2000 to 2020) caused you to do an action (go back in time).

Once you're back there, though, time still works the same way it always did. Events in the past can cause an effect in the future, but tomorrow isn't ever going to directly change today.

So, once you're back in 2000... the events of 2020, which to you are in the past (because you remember going back in time and everything that happened before that), can change your future actions (which to you take place in the year 2000). That means that if you can go back in time to change the past, you can change the past: your actions in your immediate future can cause changes.

But, the future can't change the past. If you went back to 2000 and did something there that made you not have to do that in 2020... well, you still did do that in 2020, because how else would you have been in 2000 changing things?

The idea is that once you go back in time, any changes you make are focused on the way you experience time, not some third-party objective time.

1

km89 t1_j9x5158 wrote

As is learning that sometimes you can make time for you.

Hence the "as long as it's not abused" part of my comment. Of course you can't call out every time you have a deadline or a test or you're feeling a little stressed.

But the occasional "look, I'm not physically ill but I just need a day" is fine. It's exactly what people are already doing, except you don't need to hang your head upside-down over the side of your bed to make it sound like you have a cold when you make the call.

1

km89 t1_j8ukh6r wrote

Coming from a place of total ignorance here, is there any explanation for why SSRIs work so well, assuming serotonin isn't correlated with depression?

2

km89 t1_j6ohjbn wrote

Exactly what it sounds like.

It's not a super common term, so it really doesn't have a firm definition. But it's an email that you either get or receive that does damage to your professional reputation such that your career is effectively over, either in general or at a particular place.

For example, sending an email to the entire company criticizing upper management's decisions is likely to end your career at a particular place.

18

km89 t1_j6gyzgw wrote

Taking a risk of making some big assumptions, I think I might see your problem here.

There are many types of therapists, but they fall largely into two categories: talk therapists, and behavioral therapists.

Talk therapy is used when you really need help sorting out problems, emotions, hang-ups, whatever else. It's a way for you to vent your problems and explore what their root causes are under the guidance of someone who can help you tease out these answers by yourself. They're not there to tell you what to do or how to feel, they're there to help you decide what to do and how to feel.

On the other hand, behavioral therapists do tell you what to do. Usually, you'd approach them with a problem that you want help resolving, and they can help you develop the skill to solve that problem. As a personal example, I recently crashed hard due to burnout at work, and one of the symptoms of that was uncontrollable anxiety and frequent panic attacks. I went to see a behavioral therapist, who explained in part about how panic attacks are essentially a short-circuit in your brain causing panic where it isn't warranted, and she suggested several methods of interrupting this process so that I could reassert control. The result was me becoming functional again, and ultimately to the anxiety diminishing as I learned to handle it.

It sounds like you've been going to talk therapists when what you're really looking for is improvement on specific things that are bothering you, based on your other comment that you want to make things work and get better.

If that's true, you may want to come up with a list of specific things you want to improve on. Maybe you have trouble getting to work and you want strategies on how to motivate yourself. Maybe you struggle with anxiety and you need strategies on how to handle it. Maybe you find life joyless and want strategies on how to bring back the happiness. Maybe you don't even know what's wrong and you need strategies for identifying things that are bothering you. Behavioral therapists can help with that.

11

km89 t1_j6glfvx wrote

>Your logic doesn’t even make sense tbh

I think the logic here is "you won't be able to buy an AI developer that can do everything a developer can do any time soon."

Which is true. And as OP said, it'll drastically reduce the number of developers... because the things it can do will ensure that every remaining developer can do several times the work they used to be able to.

Which is exactly what happened to farming. It only takes one farmer with a combine harvester to harvest the same amount of corn that would take many farmers with scythes.

2

km89 t1_j66tdsk wrote

Reply to comment by Psychogistt in Chance of riots tonight? by [deleted]

>Police brutality happens regularly to working class white Americans as well.

I'm sure, but it's worth pointing out the overtly racist elements of police behavior. It's not even remotely out of the realm of possibility that these cops have gotten it in their head that they are some of the "good ones" who either personally or whose family at one time escaped the hood, and have contempt for those who have not. I've personally head almost as many black people as white people make the comment that "there's n*****s and then there's black people." (EDIT: Though, to be fair, my social circle is mostly white. It's possible there's a bias there, regarding which black people choose to be a part of that circle or are made to feel uncomfortable doing so.)

Here's a personal anecdote. Probably about 10 years ago or so, I was in an acquaintance's back yard. There were a group of white adults, white teenagers, and one black teenager. All of us were borderline white-trash at the time.

A cop car comes screaming up the driveway. Two officers jump out, ignore every single white person, and tackle the black teenager. They ended up fracturing his skull and breaking his nose. We later found out that they were doing a drug bust... at the wrong house. I offered to testify, but the victim and his family never took me up on that and I have no idea if it went anywhere.

The point is, we were all very obviously of similar economic background--but somehow that was not enough to cause police brutality to the white people, but was enough to cause police brutality against the black person.

I think it's true that police action is largely class-based, but it's also important not to forget that there are racist elements at play.

2

km89 t1_j66sel8 wrote

Reply to comment by Psychogistt in Chance of riots tonight? by [deleted]

An alternate perspective: these people have done something that arguably makes them not worth rehabilitating. They are willing to literally kill the citizens they're supposed to protect, seemingly for no reason at all other than perverse enjoyment. A man is dead so that these people could exercise their authority and power.

I personally don't support the death penalty... largely because I don't trust that the government will use it correctly, and that largely based on decades of evidence of wrongful convictions.

But if it were to be allowed and used correctly, it would have to be a method of removing un-rehabilitatable, dangerous people from society. People who either cannot ever be trusted not to be a danger or who have shown that they are unwilling to cooperate with reform attempts.

I don't disagree with the death penalty as a concept, in some fictional ideal world where it would only ever be used on people we know will never not be dangerous to society. We don't live in that world, but I sympathize with people who believe that people who commit crimes like this should just be removed.

2

km89 t1_j5kjd17 wrote

>AI isn't biased, it just uses what is available to it.

I mean, that's a little convoluted.

The bias in the dataset creates a bias in the AI. Remember that AIs aren't necessarily looking at the data set every time they need to create something; they're trained on the data set, but the model itself isn't referencing the dataset when it's not being trained.

So yeah--the initial bias definitely comes from the people who select the training data. But the bias persists in the absence of that data, too.

0

km89 t1_j1ohf92 wrote

Sort of, but not really.

It could be faster than classical computers at a specific task, yes.

But it's not just churning through the same steps a classical computer would, faster than a classical computer would. It's something entirely different, which is why the biggest benefit is likely going to be the simulation of systems we can't currently simulate.

So it's not like a really fast CPU, the way a car is a faster vehicle than a horse. It's more like a petting zoo versus a conservation zoo. Some of the same things are present in both, but they really have almost entirely different purposes.

9

km89 t1_j1in2qg wrote

I don't think the point was an "all lives matter" equivalent, but more "what's different about LGBT+ places that requires different training than any other club?"

If there's separate training, it's because there's something different about the process requiring a different curriculum. But it's not like gay clubs tend to be open spaces while straight clubs tend to have lots of rooms and hallways or something.

Regardless, the question's based on a misunderstanding. They're training employees of the venues at risk, they're not training police officers on LGBT+-specific tactics.

1

km89 t1_ixdadxz wrote

A "class" is a group of related code, typically organized such that you can instantiate an "object". For example, you might have a Fruit class that contains all the methods and properties that a fruit can do (ripen, rot, color, etc).

A "method" is something that the object can do. As noted above, a Fruit class might have methods for ripening or rotting; these methods would contain the code necessary to manipulate the object to do those things.

A "property", which you didn't ask about but which is important, is something about the object--not something that it can do, but something about its current state. A Fruit's Color property (Fruit.Color, for example) could be set to red, or orange, or yellow, or whatever else.

Here's an example of how properties and methods can work together.

 class Program{
      public static void main(String[] args){
           Fruit banana = new Fruit(); //This calls the constructor, which currently doesn't do anything.
           banana.Color = "Green"; //Sets the Color property of the Fruit object to green.

           banana.Ripen(); //Calls the Ripen method, which for the sake of argument here changes the color

           Console.WriteLine(banana.Color); //Would write to the console the color of the fruit. 
                                                 //For the sake of argument, assume the Ripen() method 
                                                 //changes the color from green to yellow, so this would 
                                                 //write out "Yellow" to the console.
      }
 }

When you first instantiate an object, you call that object's "constructor". A constructor is a special method that contains all the logic needed to set the object up initially, before you begin to do anything with it. This will get slightly more technical, but imagine this:

 class Recipe{
      private List<string> ingredients;
      
      Recipe(){
           ingredients = new List<string>();
      }
 }

Above, the Recipe class has a private List of ingredients (and it's declared with List<string> because the List class can be of any type, so you're telling the compiler that all of the stuff in this List will be of the string data type). It's private, because nothing should be able to directly access it. But, also notice how it's not actually instantiated. The constructor, which is the one method in this class, instantiates the List object. An actually useful class would also have methods for getting and setting the ingredients, but they're not listed here.

Constructors are occasionally paired with "destructors." A destructor is another special method that handles any logic the object needs to do before it goes away. If you don't manually declare one, the compiler will put a fake one in for you, so don't worry about these unless you have to.

Structs are different from classes. They share a lot of similarities, but ultimately they're more limited and less able to change. The big difference is that they're not really objects and thus shouldn't--or can't--be changed after creating them, and they can't be used to inherit from.

Here's a good link that has a rundown of the differences between structs and classes, which I'll link rather than just typing out the differences here.

>https://www.c-sharpcorner.com/blogs/difference-between-struct-and-class-in-c-sharp

2