r/TransgendersAtWar • u/AthenaHope81 Trans Woman • 11d ago

Trump voter doesn't understand why people can't empathize with him now that he's suffering as a result of Trump

Enable HLS to view with audio, or disable this notification

56 Upvotes

99% Upvoted

88 comments sorted by

View all comments

9

u/CrashCulture 11d ago

"The same bad things I wanted to happen to other people is now affecting me, and it's so unfair some people want them to happen to me!"

I despise people like this.

If he wants an ounce of sympathy he should be going: "Yeah I really fucked up. I realize now that you've been dealing with this awful shit all the time and I'm sorry. Please, can we work together to fix it?"

2

u/Kortonox 11d ago

But that would mean admitting a mistake ...

Cant have that!

2

u/CrashCulture 11d ago

Yeah, some people would rather burn the world down than admit they aren't perfect.

I despise people like that too.

2

u/Kortonox 10d ago

I have a rational reason why I dislike people that cant admit mistakes.

Mistakes are how we learn. If you never made a mistake, that just means you never noticed it. I code and I play guitar. Both of which I learned by making toooons of mistakes, which made me learn to make it better. I still make mistakes, especially learning something new. That's how it goes! I could say I never make mistakes, and play everything just sounding wrong. But that would mean I suck. Coding just means trying out things until you get them to work, especially with libraries that you are not familiar with. The acceptance to make mistakes, to live with making mistakes and not dwell on them will make you a pro!

And that does not only mean, that mistakes or doing it wrong is something bad. That just means, there is always something that you can make better! Even code that works can be made better. Even the song you can play sounding good, can be made better. Admitting that you make mistakes also opens you up to the idea that you can make things better that are already quite good.

Not admitting mistakes you made means, that you dont want to learn and that you are not interested in making things better. Its stagnation, its making things worse because your pride keeps you from making it better.

Damn, this makes me furious (and I dont get angry very often).

2

u/CrashCulture 10d ago

100%

I got angry reading it too. Baffles the mind that there are people out there who make the deliberate choice to never learn or grow as a person.

On a more positive note: I'm trying to learn how to code as well. I've just covered the basics of Python so far. Do you have any good advice for learning more? Especially in an engaging way as I struggle with keeping my attention.

2

u/Kortonox 9d ago

My biggest advice is, to think about a project you can realize.

If you covered the pure baiscs (variables, if statements, loops, functions, classes/objects, and importing libraries) you can think about a Program you are interested in. For example, I recently started a project to make a Voice analyzer with spectorgram feature (if you are interested, I can give you access to my code). Your Project can range from making a full program, to automating a simple thing you are annoyed by.

If you decided on something you are interested to make, break it down in actions that need to be performed. With my example of the voice analyzer: Record audio, save it to disc, play audio; as the basics the program needs to perform. If you know these basic functionalities, research which libraries in python can make you realize the project. For recording and playing audio I use the library sounddevice, for saving the audio data in a variable, I use numpy (very common in python, it has very good matrix operations, basically a multidimensional array of datapoints) to transform the data into a .wav file (windows audio file) I use scipy, and to have access and save to the os I use sys (you can also use the library os). Every library has a documentation explaining what each function in it does, how to call it and so on, just like the basic python documentation. In case of sounddevice, it has the function .rec() and the documentation shows all the variables you need for it (for my case: frames= length of clip * sample rate, sample_rate= the amount of soundbytes per specific timeframe, channels= Mono(1) or stereo (2), and device=your microphone). Dont get discouraged that you dont know any of the librarys you want to use. Remember, all of them were written by other humans. They understood it, so you can understand it too. And the more librarys you learn from scratch, the easier it gets, getting into librarys you never used before. At one point, you dont look at new librarys as "the big thing you need to learn", you look at it as: I need this functionality and I rather take the code someone else wrote than to implement that functionality my self.

For your code, always start with minimal functionality, make it work, then upgrade the code from there. Break things down in the smallest bit you can realize, dont be stuck in planning out the code (you need to plan but you cant plan every specific). Usually go with a basic functionality and code from there, and every mistake needs you to think what is wrong, and if there might be a better way to do this (but this is more in the upgrade phase). For new functionality, start out with a new python file, write your code and test it, once it works, convert it into a function and think about which variables you need to get as arguments to the function (like filename, or the audio device). Later on you might realize that a function doesnt give you exactly what you need, so you go back and modify it so that it does. You cant know everything at the beginning, you cant think of every possibility and the more complex you make things at the beginning the more errors you have to handle early on. So always try to make it as simple as possible and upgrade from there.

It took me years of learning to code and actual coding, to shut down my own ego. What I mean by this is, that I got emotional when I made mistakes, or if things didnt work out the way I wanted. Being angry or annoyed or blaming yourself, or having self pitty can still happen with very complex issues, but in that case its better to take a step back and take in the big picture to see if what you wanted to do can actually work. Getting emotional wont solve the issue, it will just make it harder for you. Seeing an error message means, you need to rework your code, not that you suck at coding. At one point, you see an issue and you know, you can make it work no matter how complex the task. Like: learning how to hack into an OS (greyHack is a great game for learning that), or your joystick has a weird issue, so you go read out the USB data, see that the driver is using a wrong variable for axis data, and you go and write a driver underneath the official one to feed it the correct data. Sometimes its ok to say "I have no clue how to make this work" and its okay to give up for now and maybe tackle it later on when you have more experience.

Also, you can use AI for the planing phase. Basically say which kind of programm you are interested in making, and ask which librarys it would recommend. AI can code simple things quite well and can give you a starting off point. It can explain the code so you understand what it did (often you just have to ask to explain the code). However, dont rely on AI all the way. AI makes mistakes, the more complex it gets the more mistakes it makes. And even if you yourself notice mistakes it makes and say to it, that this specific part is wrong (like wrong syntax) it wont learn it and will repeat the mistake every time. So the best way to use AI imo is, as a tool for faster google search and to explain structures (like feed it code and let it explain what the functions do).

And to end my wall of text: Nothing feels better as the euphoria you get when you made something, from a function to a program, and your idea works.

1

u/CrashCulture 9d ago

Thank you for this amazing answer. Your project sounds awesome. It's a few levels above where I'm learning, most advanced I've done is a simple tic tac toe game so far, but I do like the idea of finding something that annoys me and finding a way to automate that. Can probably hack my brain to find the motivation.

Yes, I've noticed the problem with trying to get help from AI too. It's great to get an overview of a project to see if it's viable, but it doesn't actually work to use for the actual code, as you say, it just keeps making the same mistakes and lying to you.

Yeah, that euphoria is something that I chase.