• 1 Post
  • 72 Comments
Joined 1 year ago
cake
Cake day: July 10th, 2023

help-circle

    1. Sadness and depression are chemical events in your brain that you have no conscious control over
    2. You can consciously control some of the common triggers that lead to negative thoughts but most people can’t completely turn off given thoughts
    3. Your brain is like the earth and thoughts are like rivers, the more you think certain ways the more you will continue to think those ways, neural pathways are strengthened by their activations

    Learn to redirect, wear a bracelet or similar physical reminder of a specific thing you like, when you experience the thoughts you want to avoid, redirect and focus on the things you like

    Change your environment, identify triggers that push you toward depression and avoid them. Some literally cannot be avoided, and some situations are impossible to escape, in those cases accept the associated negativity and redirect

    Find people who have the attitudes and feelings you want to emulate and spend time with them, we are social and learn much from our peers

    Ingest media that aligns with your desired world view, avoid tragedies, horror movies, gore, popular doom news media, etc. This will force you into an echo chamber but it is a popular coping technique

    Most important you are your own person, write down how you feel and what triggered those emotions every day. You can’t really know if you’re improving if you don’t have a record









  • The real example of a health check trait really brings this issue to life, it’s linked within op’s article as well

    Is this a reasonable summary?

    Say you want a trait where a method returns a task that you would like to sometimes run within your own thread and sometimes move it to a separate thread to be executed, that means the Send constraint isn’t necessary to add to your trait but it would be nice to add that constraint within another method’s parameter definition so that it can accept structs that implement the trait and further constrain that implementation to be Send’able. That’s now possible with this new rust language feature, though it was previously possible through a crate, now it’s no longer needed.








  • I explained a little about buffer overflows, but in essence programming is the act of making a fancy list of commands for your computer to run one after the other.

    One concept in programming is an “array” or list of things, sometimes in languages like C the developer is responsible for keeping track of how many items are in a list. When that program accepts info from other programs (like a chat message, video call, website to render, etx) in the form of an array sometimes the sender can send more info than the developer expected to receive.

    When that extra info is received it can actually modify the fancy list of commands in such a way that the data itself is run directly on the computer instead of what the developer originally intended.

    Bad guy sends too much data, at the end of the data are secret instructions to install a new program that watches every key you type on your keyboard and send that info to the bad guy.


  • There is a ton of literature out there, but in a few words:

    Rust is built from the ground up with the intention of being safe, and fast. There are a bunch of things you can do when programming that are technically fine but often cause errors. Rust builds on decades of understanding of best practices and forces the developer to follow them. It can be frustrating at first but being forced to use best practices is actually a huge boon to the whole community.

    C is a language that lets the developer do whatever the heck they want as long as it’s technically possible. “Dereferencing pointer 0?” No problem boss. C is fast but there are many many pitfalls and mildly incorrect code can cause significant problems, buffer overflows for example can open your system to bad actors sending information packets to the program and cause your computer to do whatever the bad actor wants. You can technically write code with that problem in both c and rust, but rust has guardrails that keep you out of trouble.