I write bugs and sometimes features! I’m also @CoderKat@kbin.social.

  • 0 Posts
  • 25 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle

  • I am a bit curious where the balance is for how much shit you’ll put up with if it means a lower cost of living (or bigger/cheaper home, anyway). I’m personally of the stance I will pay (or give up) a significant amount of money to live in a good, mostly sane place.

    It’s obviously a balancing act. Nobody will give up all their money to have marginally better emotional safety. But where is the line? How much better do things have to be in a different place (or how much worse in your current place) to accept, say, a small apartment that costs a solid third of your income? Or inversely, would you put up with a Gilead situation if you got a sprawling mansion out of it?






  • There’s already a ton of such exploits. Most servers use Linux and many exploits of corporations this had to go through Linux (though many exploits aren’t related to the OS at all – eg, SQL injection is OS independent). I expect it’s more common, though, that attacks on Linux systems are either meant to target servers or were personalized attacks that you’re not gonna accidentally download.

    On that vein, I also kinda suspect that many people who use Linux may be bigger targets for their employer than their personal PC. Which is actually scary, cause personalized attacks are far harder to defend against. I expect the average Linux user is technically savvy. Not a lot of money in try to do a standard, broad attack on such types (I think most attacks on personal computers are broad attempts that mostly depend on a small fraction of technologically incompetent people falling for simple schemes). But a personalized attack that happens to infiltrate a fortune 500 company? Now that’s worth a lot of money. Using Linux won’t protect you against those kinda attacks.




  • Find local groups. Two notable ones for me are that I found a discord for my city for people looking for friends (which means stuff like regular board game events and the likes) and the kink community (ie, fetlife) regularly does similar (you don’t treat that one as a dating site, but rather a way to find real life events where you meet people).

    There’s probably various other ways to find real life meetups that aren’t for the explicit purpose of meeting people to date, but will find em anyway. Casual sports leagues, hobby oriented groups, co-workers, etc.







  • But are they? Generally in tech, it’s really hard to gauge people’s performance and most companies are conservative with firing people for performance reasons. So you could coast by on mediocre performance. You team won’t be happy with you, but you probably will keep your job simply because you’re given the benefit of doubt. Tech is one of those areas where someone can actually be 10x as effective as another person, because so much of the job can be spent on stuff like debugging and dealing with weird issues, where one person might spend all day on an issue that another person can resolve in minutes.

    There’s also something to be said about the fact that companies are usually paying for your time, not output. Contractors are the ones who are paid for output, not employees. It’s also straight up expected in tech that you’re looking for ways to automate some tasks so they don’t have to be done anymore. It’s not like some mindless office job where you’re expected to do X reports per day. There’s a never ending list of bugs to fix and features requested. You’re generally paid to find ways to increase productivity, not merely do the same thing over and over.

    At any rate, tech is usually also paid well enough for it. There’s still massive income disparity between regular workers and C-suite, but at least the pay is always well, well above living wages, stock options are commonly given to regular workers, and high performers often are rewarded for doing better than average. IMO, tech jobs aren’t really an area to focus on the kinda mindset you have, since it does so much better than most (not perfect, but still far better). Most jobs don’t get anything close to what tech jobs offer to regular employees.



  • The problem is that the “assault weapon” wording makes it easier for pro gun to dismiss you. The US has a lot of people obsessed with guns. I’d love if the US could just ban guns entirely, but reality is that we’d have to at least start with reasonable baby steps and cannot give them any easy way to get out. By using the “assault weapon” wording, you’re just making it easier for them to dismiss gun legislation cause they’ll claim “it’s too vague” (even if it’s not).

    It’s unfortunate that wording has to matter so much, especially in colloquial usage, but it’s such an uphill battle to get even the slightest gun restrictions in place, so we sadly do need to be perfect. And yeah, it’s stupid. It’s dumb that the US can be like it is and people will still defend their guns to the death. But we have to account for that if we want to make anything better.


  • Personally, I enjoy the problem solving. Debugging is fun once you’re good at it (and when there isn’t major time pressures).

    Professional software dev is also waaaaay more than just coding, too. And the more you do it, the less coding you’ll do. A junior dev might spend most of their time coding, but senior devs are spending a lot of time doing high level design, helping the juniors, and reviewing various kinds of things.


  • Some of these I get, but I don’t get the T9 thing. T9 was so bad! It took ages to type many words. Today’s predictive keyboards are miles better.

    Also, no software updates? Sure, every now and then there’s a shitty update, but most updates are great. New features and especially bug fixes are amazing. Used to be that if something had a bug, you just had to deal with it. There’s no guarantees it’ll be fixed today, but many companies do fix their bugs at least eventually. The ability to iteratively develop is huge for software quality. These days, unless you’re developing something that absolutely cannot fail (like a mars prober or radiation therapy machine), it’s widely agreed upon that iterative design is superior to “waterfall” design of trying to plan it out all ahead of time. Part of why is so you can get feedback continuously instead of only after you’ve committed to months of tech debt.