• 0 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: September 15th, 2025

help-circle





  • The analogy is perfectly accurate.

    An imperfect, simpler form of security vs a higher, more cumbersome form of security.

    Where is the problem with that analogy?

    Biometrics are not “bad practice for anyone concerned about security”. They are one type of security that is sufficient and effective for certain risk profiles but not others. Users should make informed decisions based on their needs and the features of the security implementations they are considering.

    Your hyperbole is, in fact, dangerous as it pushes people who do not understand security to blindly accept policies that are not good for their risk profile. We have proof that proper usage of biometrics is more consistent with end-users than proper usage of passwords. It’s not just about convenience. It’s also about adoption and proper compliance.

    Absolutist policies and positions like yours do harm. Just look at how NIST recommendations have moved away from things like frequent password change enforcement because it leads to bad behavior (writing down passwords, etc)




  • This has big “don’t use a standard deadbolt on your front door; it’s not as strong as reinforced titanium doors with time-release locks” energy

    Like, not technically wrong, but does not fit the standard risk profile, it’s overkill for most situations.

    Also to everyone talking about US law enforcement, this is just so easy to protect from, not worth ditching biometrics: if you see cops approaching and are worried about a device being unlocked, just reboot it. If you need to do it surreptitiously, just hold the power button to force shut it off after ~10s. This will always require a password to unlock after


  • I think it’s important to mention why this is:

    Your credit score is NOT a measure of just “how likely are you to pay off your debt”.

    It is a measure of how likely you are to earn creditors money rather than lose them money.

    Successfully keeping up with 4 monthly payments indicates you’re a likelier source of profit than only having one line of credit you pay each month. You likely have more expendable income, you’re more likely to pay interest instead of paying down extra principle, you’re clearly accustomed to carrying debt, etc.



  • I’m primarily a subs person, despite the fact that I prefer dubs if they’re actually good enough.

    Cowboy Bebop and Fullmetal Alchemist are phenomenal dubs. I’ve watched both subbed and dubbed and think they are equally good, and thus prefer the dub so I can pay more attention to the animation and action.

    The only recent dub I’ve thought was okay was ReZero. I don’t love it, and prefer the sub, but it is one of the better ones I’ve heard. Maybe there are other great ones but I stopped even trying to find them after a while 😂


  • Good dubs have always been a rare gem.

    IMO the key to a good dub is two things:

    1. Actors and direction that prioritizes caricature without becoming “campy”. This is something JP VO is ridiculously good at. They identify a character’s personality, crank it up to 11, but still make the emotional delivery feel genuine, even if extreme

    2. Direction that understands the characters as intended by the author. This is where a lot of dubs fall horribly short. They do not consult with the original content creator, and wind up with voices and characterizations that may seem to work on the surface but are lacking the depth of understanding for a character needed for the performance to make sense over time as we learn more about them.

    Just my 2c, but IMO this is where most of the problems with dubs come from, and why they wind up sounding either generic or campy.


  • EDIT: In the US this is covered by the Fair Labor Standards Act, which is extremely simple when defining what is considered on-the-job work. If it is mandatory, work-related, and for the benefit of the company, then it is on-the-job work and you should be paid for the time. So congratulations; you’ve likely participated in wage theft by onboarding people who aren’t being paid for their time. Obviously it wasn’t knowingly or with intent, but that doesn’t change the fact that, based on your response, your employers have had you or your coworkers participate in failing to pay people what they are owed.


    Except for the other reply that starts “you are right. you cannot onboard a new job before you leave your old one”??? They may go on to say that accepting an offer isn’t onboarding but since I never tried to argue that it was, that’s kind of irrelevant.

    Lots of people don’t know their rights or their obligations. Wage theft is the #1 from of theft in the US by a lot. Coordinating with an IT department for onboarding without getting paid for it is straight up wage theft and being taken advantage of. Doing so while still employed by another company is moonlighting under most contracts.

    People do shit like that all the time. Doesn’t make it right. Doesn’t make it safe.


  • If you’re talking to the IT department about workstation configuration without signing a contract and getting paid for it, you’re being taken advantage of.

    Yes, it’s reasonable, and smart, to ask people during the interview process about their tech stack. But there is no way I’m coordinating with IT on the setup and configuration of my workstation without a contract in place or before my start date.





  • neatchee@piefed.socialtoProgrammer Humor@programming.dev•No Microslop for me
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    21
    ·
    edit-2
    8 months ago

    In the overwhelming majority of situations you cannot begin the onboarding process with IT while still working for a previous employer. Especially at this level of software engineering that would run afoul of moonlighting policies.

    is what your describing technically possible? sure. Is it even remotely probable? Absolutely not.


    EDIT: I am absolutely flabbergasted at how many people don’t know their rights.

    In the US this is covered by the Fair Labor Standards Act, which is extremely simple when defining what is considered on-the-job work. If it is mandatory, work-related, and for the benefit of the company, then it is on-the-job work and you should be paid for the time.

    Stop perpetuating wage theft, people. It’s the #1 form of theft in the US by a wide margin. Learn your rights and demand pay for your work.


  • Logically terminating resources does not imply a terminating logic loop. Clever wordplay, though.

    Recursion has a specific definition. It means solving a problem by breaking a process down into smaller and smaller self-similar pieces until reaching the “base case”. In programming, it (almost) always means a function that calls itself as part of its internal logic. Depending on what the function does and the conditions for returning a value from the function, it may do that one time, many times, or not at all. A classic example is the Boggle solver.

    I did say I was being pedantic :P