[object Object]

Autocorrect hates me, I am sorry.

  • 0 Posts
  • 47 Comments
Joined 1 year ago
cake
Cake day: July 20th, 2025

help-circle
  • I just can’t communicate why or how an average user should use passkeys.

    I use them, I like them even, they’re a decently easy flow with good trust boundaries.

    Yes, passkeys are hard/impossible to phish, but the fallback flows are exactly as easy to phish as passwords today and are basically a requirement if you implement passkeys.

    I can’t recommend using passkeys in Chrome’s password manager, for lock in and portability reasons (plus every browser should have an ad blocker). I can’t recommend the OS based ones because frankly nobody should install windows anymore, and macOS is on the precipice of enshittification. That just leaves password managers, which I think are a good idea, but also a single point of failure.




  • No, I doubt really use it for launching apps. On most OSes now you press cmd/windows/super button and it opens a text field to launch apps.

    Mostly I use CLIs or TUIs in the terminal for 80% of my computer use, and a many apps that are just browser tabs now.

    My vim config has dozens of custom hot keys and functions for all sorts of things. Same with tmux and my dot files or user local script bin, they’re full of utilities and scripts and customizations.

    That’s never going to help me organize a photo album or be a good existence for checking my email (I know I can check my email from a tui, but I don’t want to)



  • It would be nice.

    Most of my complaints about unions are:

    • Seniority is a terrible system to build a foundation from. It just is. I don’t give a fuck who got there first, seniority systems grow complacency, punish competence, and lower labour mobility. I was in a union as a teenager, the company offered lump sum payments for the older union members to literally sell out the younger ones with delayed wage increases, and they all voted for it since it was harming someone else.
    • There are many unions that are just greedy pigs. You pay dues in, the union gets fat, but they spend all their time defending the wrong people.
    • Unions can add a lot of extra process to things that don’t require it

    However, that does not mean we shouldn’t have unions. We should maybe try to improve how we do them, so they work better for everyone.

    I just want a union that looks out for unfair labour practices, forced unpaid overtime, keeps the company competitive on salary and benefits, and is willing to fight for workers who are unduly fired or sidelined.


  • I really like the terminal, most of my use is a web browser or terminal with tmux.

    I use hot keys like cray, but I haven’t found a tiling window manager I like yet (I don’t like when things shift automaticallly, it breaks my mental model), and I haven’t found a Linux desktop with the keyboard ergonomics of macOS.

    But 95% of my time is with full screen terminals, so I’m actually pretty okay. I have customized vim and tmux to the hilt, and I like that.







  • I’ve always hated AI comments. They’re the bastard fusion medium blog spam and data labelling from underpaid and exploited people seeping into the slop.

    Comments are for why, edge cases, and caveats. They should help explain unintuitive behaviours that usually must be learned the hard way, they help expose a larger structures, they explain an optimization, a shim, or a complex regex, or they explain where a temporary measure exists. Things of that nature.

    Self documenting code is about thinking of the reader. I’ve worked in places that uphold self documenting code as gold and banned code comments at all and I’m convinced that’s wrong. It’s a burden on readers to have to go through history to find the addition, but the file has changed names or moved without a proper git mv and it’s a waste of time.

    On that note, learning objective C and Swift did a lot for how I think about what naming could be. I try to focus on clear verbs and nouns so the action and target are always clear, avoid side effects, include examples in my docs, and embrace typing structures like nanedtuples in untyped languages.