• 0 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • You got in at a bad time and probably picked some subpar investments. You likely bought some big tech stocks at the worst possible time, and many of them never recovered because they were way over valued to begin with.

    Stick with total market or sp500 fund like VTI or VOO. You’d be up right now if you had.

    Also, it sounds like you invested once and then never bought more? The whole point is that you’re buying more every paycheck. You’d be way up if you’d kept investing through 2022 when prices were low.

    Retirement accounts with the right funds are supposed to be set it and forget it. Make the automatic contribution every paycheck and look at it maybe once or twice a year. Otherwise, let it be.


  • Memory safety for one. C is very memory unsafe and that has been the source of a great, great number of software vulnerabilities over the years. Basically, in many C programs it has been possible to force them to execute arbitrary code, and if a program is running with root privileges, an attacker can gain full control over a system by injecting the right input.

    I have very limited knowledge of rust, but from what I remember writing memory unsafe programs is nigh impossible as the code won’t really even compile. Someone else with more knowledge can probably give more detail.



  • phoneymouse@lemmy.worldtoMalicious Compliance@lemmy.worldWork from home
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    4 months ago

    Yeah and they want to install some profile that gives them access and puts your internet connection through their VPN. My coworkers look at me like I’m crazy because I carry a work device and a personal device. Like, why would I give my employer access to all of my web traffic on my phone? You’re crazy if you don’t carry two devices.



  • Love it when my coworkers reformat the code style, making it nigh impossible to understand what they actually changed, while greatly inflating their “contribution.”

    It also blows away the git blame, making it hard to know who actually changed that one critical line of business logic 3 years ago that you need to understand before trying to fix some obscure bug.

    I have one coworker who does this constantly and if you just looked at git blame, you’d think he wrote the entire code base himself.