Hello!

I work as a AAA game programmer. I previously worked on the Battlefield series.

Before I worked in the AAA space, I worked at Disneyland as a Jungle Cruise skipper!

As a hobby, I have an N-Scale (1:160) model train layout.

  • 1 Post
  • 42 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle










  • Counter-counterpoint: I’ve been using it since 2019. I think you’re exaggerating.

    • It aggressively tries to center itself, always. If you’re in a lane and it merges with a second lane, the car will swerve sharply to the right as it attempts to go back to the middle of the lane.

    • It doesn’t allow space for cars to merge until the cars are already merging. It doesn’t work with traffic; it does its own thing and is discourteous to other drivers. It doesn’t read turn signals; it only reacts to drivers getting over.

    • If a motorcycle is lane-splitting, it doesn’t move out of the way for the motorcycle. In fact, it assumes anything between lanes isn’t an issue. If something is partially blocking a lane but the system doesn’t recognize it as fully “your lane”, the default is to ignore it. The number of times I’ve had to disengage to dodge a wide load or a camper straddling two lanes is crazy.

    • With the removal of radar, phantom braking has become far, far worse. Any kind of weather condition causes issues. Even if you drive at sunset, the sun can dazzle the cameras and they don’t detect things that they should be able to - or worse, they detect problems which aren’t there.

    • It doesn’t understand road hazards. It will happily hit a pothole at 70 MPH. It will ignore road flares and traffic cones. When the lanes aren’t clearly marked (because the paint has worn away or because of construction), it can have dramatic behavior.

    • It waits so long to brake, and when it brakes it brakes hard. It accelerates just as suddenly, leading to a very jerky ride that makes my passengers carsick.

    The only time I trust FSD is when it’s stop-and-go traffic. Beyond that I have to pay so much attention to the thing that I might as well just drive myself. The “worst thing it can do” isn’t just detour; it’s “smash into the thing that it thought wasn’t an issue”.


  • Yet another reason why I prefer Kbin.

    The developers of Lemmy have been questionable for some time. See their post announcing Lemmy: https://www.reddit.com/r/communism/comments/cqgztr/fuck_the_white_supremacist_reddit_admins_want_me/

    https://web.archive.org/web/20230626055233/https://old.reddit.com/r/communism/comments/cqgztr/fuck_the_white_supremacist_reddit_admins_want_me/

    Hey all, longtime Marxist-leninist, recorder of left audiobooks, and megathread shitposter here.

    Posting this in light of a recent one week Reddit ban I earned for shitting on US police, as I’m sure many of us have gotten in recent weeks.

    So I’ve spent the past few months working on a self hostable, federated, Reddit alternative called Lemmy, and it’s pretty much ready to go. Unlike here we’d have ultimate control over all content, and would never have to self censor.

    Obviously as communists, we agitate where the people are, so we should never abandon Reddit entirely, but it’s been clear to all of us from day one, that communities like this stand on unsteady ground, and could be banned or quarantined at any moment by the white supremacist Reddit admins. This would be both a backup and a potentially better alternative. Moderation abilities are there, as well as a slur filter.

    Raddle isn’t an option obviously since it’s run by this arch anti tankie scum, ziq.

    I wanted to ask ppl here if they’d like me to host an instance, and mod all the current mods here.

    The instance that post mentions at the end became Lemmygrad. Lemmy.ml and Lemmygrad are the same people. This was their first post announcing Lemmy as a real thing you could go use. (It’s also why a good chunk of the Threadiverse is absolutely infested with tankies.)

    I never agitated for a fork because generally the Lemmy devs do an okay job at keeping their politics separate from their software. But the more I look at their attitudes and (frankly) the hazing they do towards contributors, the more I’m thinking that it may be better to push for an outright fork of Lemmy, give it a better name, a saner dev team, and excise the original devs entirely. Even if we ignore their politics (which is hard to do, but can be done), they’ve simply not been the best stewards of the project - it’s succeeded in spite of them, not because of them.

    That said, I think Lemmy as a piece of software is generally okay. Kbin has more long-term promise, I feel, but Kbin has its own issues and is much rougher around the edges. A lot of the issues Kbin has have already been sorted out by Lemmy, so I think it might be best to make a Lemmy fork and bring in features from Kbin into it (alongside performance fixes and whatnot that the Lemmy devs refuse to action on).




  • To be fair, you don’t get to be an expert at something by just reading about it. You become an expert by immersing yourself in it and knowing all the nuanced details of what you specialize in.

    For example, I’m a AAA gamedev programmer. My specialty is the Unreal Engine. I know tons of little quirks about the engine that many of my coworkers don’t - but that’s because I’ve been using the engine for over a decade at this point.

    I don’t devote every waking moment to learning about Unreal - I used to spend a lot of free time researching it before I got hired, but now I leave gaming stuff at work to avoid burnout.

    You don’t need to like hyperfixate on something to become good at it. You just need to work on it for long enough - and if it’s literally your job, you’ll spend 40+ hours/week engrossed in it, for years.


  • Here’s a video from an all-hands meeting the day after she quit. (Reddit, sorry.)

    The following is a transcript if you’d rather avoid Reddit:

    (speaker 1, Linus) So we called this meeting because it’s come to our attention that we need to have a quick chat about the best way to handle HR related feedback and rumors. We won’t be giving any names for what I hope are extraordinarily obvious reasons, but what we can do is give you the following guidelines for problem solving and conflict resolution.

    Sorry that this is all boring and corporate, but here we are. Number one, always stand up for what’s right. We’re only a team as long as we’re all working together and working for each other. That’s the most important one. Number two, always reflect on your own personal experiences and use your common sense. Few things in life are truly black and white. Number three, always wait to hear both sides of a story before passing your own judgment. Be cautious when you know that one side is bound by legal and ethical disclosure guidelines, when the other is not. Carefully consider what it says about the character of someone who would engage in that type of gossip against someone who has no power to defend themselves.

    Number four, always encourage openness and transparency. If you have a problem, you need to speak up. We want to fix it. If you receive feedback about somebody else at this company, the first response is, have you spoken with this person? Followed closely by, you need to speak with this person. We don’t solve interpersonal issues here, or really anywhere in your life, if you wish to live in a drama free zone, by engaging in water cooler politicking. So, if for any reason that individual is not comfortable approaching the person they’re having a conflict with, we have a chain that they’re supposed to follow.

    So first, you advise them to take the problem to their manager. Followed by me or Yvonne, followed by our third party HR firm. I hope that you all trust that we’re here to make this a safe, fun, and productive workplace, and we won’t tolerate mistreatment of any of our team members.

    If you have any reason to believe otherwise, then I refer you again to point number four, which is to address the issue with the individual directly, or bring it to me or Yvonne, or bring it to our third party HR firm. Since I’m not at liberty to share any details about what occurred, uh, all I can do is ask that you trust me and Yvonne.

    Um, some of you know us very well, I’ve been here a very long time, um, some of you have not been here for as long, but I like to think that whether you’ve been here for nine years or nine days, you’re here for a reason and you believe that we are utmost to run this company with integrity and compassion.

    Um, We can’t solve problems we don’t know about though, so on that note, I’d like to invite anyone who has concerns about a fellow team member or about a manager to submit their feedback either by speaking with their manager, me or Yvonne directly, or if you would prefer to provide your feedback anonymously, we have an option for that as well.

    It’s the manager and co-worker feedback form. Uh, Yvonne, if you’re not aware of it - show of hands who is not aware of it? Hey, a lot of people aren’t aware of it. Good, so now we all know. There’s an anonymous form, if for whatever reason you’re not comfortable either talking to me me or Yvonne directly about it - and that’s okay, that’s fine, we understand, that’s why we have these options - Yvonne’s gonna post it in the general chat.

    It’s a safe space to provide us ideas for improvement, or if you’re consumed by the holiday spirit and you want to say nice things, you can do that too. Does anybody else have any questions?

    Not a single question? Wow, that must have been a really good speech.

    (speaker 2, James) You gonna dance on that table, or just stand on it?

    (speaker 1, Linus) That’s it! So, um, Yvonne, did you have anything you wanted to add?

    (speaker 3, Yvonne) (inaudible) Somebody said (inaudible) if you guys want to sanitize your hands, help yourself with free (inaudible)?

    (speaker 1, Linus) Yeah, that was actually just totally random timing. It came up the stairs a moment ago. Dennis is on it. Alright. Thank you everyone. Have a wonderful and, uh, productive rest of your day. And weekend.





  • The idea is that it would be similar to hardware attestation in Android. In fact, that’s where Google got the idea from.

    Basically, this is the way it works:

    • You download a web browser or another program (possibly even one baked into the OS, e.g. working alongside/relying on the TPM stuff from the BIOS). This is the “attester”. Attesters have a private key that they sign things with. This private key is baked into the binary of the attester (so you can’t patch the binary).

    • A web page sends some data to the attester. Every request the web page sends will vary slightly, so an attestation can only be used for one request - you cannot intercept a “good” attestation and reuse it elsewhere. The ways attesters can respond may vary so you can’t just extract the encryption key and sign your own stuff - it wouldn’t work when you get a different request.

    • The attester takes that data and verifies that the device is running stuff that corresponds to the specs published by the attester - “this browser, this OS, not a VM, not Wine, is not running this program, no ad blocker, subject to these rate limits,” etc.

    • If it meets the requirements, the attester uses their private key to sign. (Remember that you can’t patch out the requirements check without changing the private key and thus invalidating everything.)

    • The signed data is sent back to the web page, alongside as much information as the attester wants to provide. This information will match the signature, and can be verified using a public key.

    • The web page looks at the data and decides whether to trust the verdict or not. If something looks sketchy, the web page has the right to refuse to send any further data.

    They also say they want to err towards having fewer checks, rather than many (“low entropy”). There are concerns about this being used for fingerprinting/tracking, and high entropy would allow for that. (Note that this does explicitly contradict the point the authors made earlier, that “Including more information in the verdict will cover a wider range of use cases without locking out older devices.”)

    That said - we all know where this will go. If Edge is made an attester, it will not be low entropy. Low entropy makes it harder to track, which benefits Google as they have their own ways of tracking users due to a near-monopoly over the web. Google doesn’t want to give rivals a good way to compete with user tracking, which is why they’re pushing “low-entropy” under the guise of privacy. Microsoft is incentivized to go high-entropy as it gives a better fingerprint. If the attestation server is built into Windows, we have the same thing.