• 1 Post
  • 209 Comments
Joined 1 year ago
cake
Cake day: June 7th, 2023

help-circle
  • Also never been a fan of Biden (but voted for him, and will again, if I have to). You’re falling into a Sunk Cost Fallacy. Yes, anyone chosen to replace Biden would be a gamble. But, Biden is a losing horse. The right time to replace him was last year. But, just because we missed that opportunity doesn’t mean we should throw good time after bad. He should be replaced before things get so late it literally cannot be done.

    This wasn’t some otherwise strong candidate, who just had a bad day. Biden is already struggling in polling. While the economy hasn’t been fantastic, it’s good enough that he should be crushing Trump. Even in 2016, Clinton was polling ahead of Trump and still managed to snatch defeat from the jaws of victory. Biden isn’t winning. He’s maybe tied and maybe losing in current polling. Trump had already proven that he can be convicted in court and not lose support. There’s just not much left to hurt Trump. And Biden doesn’t seem to have anything left to gain support. Things are not going to get better for Biden.

    Biden is losing this race. It’s time to follow the rats off the ship, before we’re trying to escape a ship on the bottom of the ocean.








  • Maybe, though if you think about it, the idea is basically:
    Hey, we borrowed all this money to buy up lots of companies. But rather than pay it back ourselves, we are going to put all of that debt on this one company we also bought (probably with some of that debt), because thay actually make money.

    It’s a shell game to allow Embracer to walk away with all the profits and never have to pay their investors back. If Asmodee manages to pay off the debt, that’s nice for them. Other than the fact that they will be hamstrung by servicing that debt, rather than re-investing in the company. If Asmodee folds and gets auctioned off in Chapter 7, that ends up having no material effect on the leadership of Embracer who made the decision to take on all that debt. Either way, Embracer is jettisoning all responsibility for the choices the management of Embrace made.

    This sort of leveraged debt buyout, loot the company, then jettison the debt tactic has been used over and over to destroy otherwise profitable companies in the name of short term profit for vulture capitalists.





  • While Chism may be a worthless leech, he isn’t completely wrong. Valve’s ownership of Steam does put it in a privileged position, which could be abused in a lot of anti-competitive ways. The fact that it isn’t doing that is really only because GabeN isn’t the same type of leech which Chism is. He’s what a lot of people seem to want, a benevolent dictator. That said, when he finally kicks the bucket, or gets tired and sells the company, the future direction of Steam would be an open question. There may be a very good argument for Valve to be put under the microscope of the FTC for possible anti-trust breakup.


  • It’s down to the expected use case.
    If you have some reason to want portability, like you travel for work or expect to want to game at a place other than you home, then a laptop is likely the right choice.
    If you only expect to game at home and don’t have a need to constantly move your system around, a desktop is usually a better “bang for the buck”.

    Personally, I don’t travel and don’t have a need to move my gaming rig around. I also like having the ability to upgrade in a piecemeal fashion. So, I have a desktop. This particular PC of Theseus has been going for a decade and a half now and shows no sign of stopping.




  • I just kinda “fell” into IT. In terms of college, I hold an Associates Degree in Math/Science from a community college; so, slightly more than nothing, but only just. I was very lucky in that my father spent an insane amount of money in the early 80’s to buy a computer and then turned me loose on it. I was doing simple programming in GW-Basic by the time I was a teenager and got pretty good at making boot disks to play games. I just became that kid who “knew computers”. After leaving college, a friend of mine convinced me to put a resume in at the company he worked for. They needed a computer tech and I fit the bill. From there it was a long sequence of job hops every 3-5 years until I ended up as a sysadmin dealing with mostly Windows systems, Active Directory, Exchange and SQL. Plus, anything else which just needed someone to “figure it out”. That eventually landed me at a gig working as a sysadmin at a US FedGov site (which is why I got my CISSP). There I often worked closely with the cybersecurity team, as they would need stuff done on the domain, and I would get it done. When they had an opening on their team, they did everything short of drag me into the office to apply for that spot. I worked in cybersecurity for that site until a bit after the COVID pandemic when I got a message on LinkedIn about a “FULLY REMOTE” (yes, the message put that all in caps) position. I was curious and applied. I now work from home, reading other peoples’ email and trying to keep the network secure for a Fortune 500 company.

    The best advice I can offer is: keep learning and never be afraid to just try.
    A lot of my career is based around “oh shit, it’s broke. Here sylver_dragon, you figure it out.” I loved logic puzzles as a kid and now I basically do them for a living. I would also recommend nurturing professional relationships and don’t burn bridges you don’t need to. That friend, who got me my first IT job was also pivotal, about a decade later, in getting me to apply to a different company he worked for at the time. When I put my resume in, it passed through the hands of several different people, people whom I had worked with at that first job. Between my performance and them knowing what type of person I was, everyone one of them said, “yup, hire this guy”. Having good working relationships now can pay a lot of dividends in the future.





  • I currently work in cybersecurity in a Senior Incident Response role. Fair warning, my opinion is biased by my own route into cybersecurity and the fact that I deal with incidents and not managing people. Though, I do get involved in interviewing and hiring. I’d say you have a good start at it. While I am sure I will be accused of gatekeeping, I much prefer working with analysts who have spent time in help desk and even as a sysadmin/netadmin. It helps if you have a good understanding of how systems and networks work. I don’t expect new analysts to just jump into Wireshark and start reading through packets with me (I’m a weirdo who really enjoys that), but I will assume that I can talk, at a high level, about TCP/UDP, LDAP, SMB/CIFS, RDP or SSH and they won’t be completely lost. Though, no one is expected to know everything and we all have our weak spots; so, don’t be intimidated if any of that acronym soup isn’t instantly familiar. Everyone is Googling stuff constantly. You’ll memorize some of it due to repetition, but never be afraid to ask questions.

    The last time my company was hiring for the SOC, the number one thing I was looking for in interviews was some evidence of an inquisitive mind. Someone geeking out over their home lab, TryHackMe or stuff like that was a sure-fire way to get my vote. I tend to be ambivalent about certs. I had some Windows 2000 certs (technically, those don’t expire, but ya…), a Sec+ (it’s expired) and an active CISSP (mile wide, inch deep, only useful for impressing hiring managers). I took a week long, in person training for the CEH but never took the test due to the COVID pandemic. Also, if the course (an official EC-Council course) was anything to judge by, that cert is just high-grade bullshit. I also have dealt with far too many “paper tigers” in my career to fall over swooning when someone has a bunch of alphabet soup behind their name. So, while I would recommend getting some certs, hiring managers love them, don’t get too caught up on them. You’ll learn far more just breaking stuff and troubleshooting it. The Net+/Sec+ duo is usually a good start.

    On coding skills, I do recommend getting some ability to read/write code. The language isn’t super important. Python is a good one to have some literacy in, it gets used everywhere. But, unless you are going to push heavily into security development, you don’t need to be at the same level as a developer. If you can pop open exploits in exploit-db.com and make sense of what they are doing, and be sure the code isn’t going to root your test box, that’s usually enough.

    Let me also recommend that you work to keep your communications/writing skills sharp. A lot of what one does in cybersecurity revolves around getting other people to do stuff. You will be regularly writing reports and needing to convince people to do stuff and/or explaining why you just kicked their system off the network. It really sucks to read incident reports from someone whose grasp of the language is lacking. Get in the habit of documenting what you do, taking screenshots, and writing in clear, concise language. You don’t need to be Shakespeare, but at least get your spelling right (spell check exists, use it), and get the basics of grammar down. If you hand me a resume with there/their/they’re mixed up, you’re going to walk into an interview with negative marks already against you.

    On the upshot, now is a fantastic time to be getting into cybersecurity. Organizations are desperate to hire trained people and some will be willing to roll the dice on a less experienced analysts who shows potential. Feel free to ask questions, I enjoy what I do most days and am happy to talk about it.