• 0 Posts
  • 1.13K Comments
Joined 2 年前
cake
Cake day: 2023年6月21日

help-circle
  • I know I probably sound like an ass but it really is that bad

    Nah I work in shitty codebases on a regular basis, and the less I need to touch them, the happier I am.

    With regards to other localization changes, it’s not important to localize everything perfectly, but it’s good to be aware of what you can improve and what might cause some users to be less comfortable with the interface. That way you’re informed and can properly justify a sacrifice (like “it’d cost us a lot of time to support RTL interfaces but only 0.1% of users would use them”) rather than be surprised that there even is one being made.

    Also, user-generated content explains why these are in a DB, and now it makes a lot more sense to me. User-generated translations used as-is makes more sense than trying to force Project Fluent (or other similar tools) into it.


  • Localization is a hard problem, but storing your translations in the DB is a bit unusual unless you’re trying to translate user data or something.

    I’d recommend looking into tools like Project Fluent or similar that are designed around translating.

    As for the schema you have, if you’re sticking with it, I would change the language into an IETF language tag or similar instead. The important part is that it separates language variants. For example, US English and British (or international) English have differences, Brazilian Portuguese and Portugal Portuguese have differences, Mexican Spanish and Spain Spanish have differences, etc.

    Using an ID instead of the text content itself as part of the PK should be a no-brainer. Languages evolve over time, and translations change. PKs should not. Your choice of PK = (TextContentId, Language) is the most reasonable to me, though I still think that translations should live as assets to your application instead to better integrate with existing localization tools.

    One last thing: people tend to believe that translating is enough to localize. It is not. For example, RTL languages often swap the entire UI direction to RTL, not just the text direction. Also, different cultures sometimes use different colors and icons than each other.



  • it is the same code as you produce manually.

    LLMs do not create the same code that I would, nor do they produce code at the same level that I would. Additionally, LLMs are not deterministic (normally - there are ways to manually seed some but it’s rare). Determinism has a very specific meaning. Compilers supporting reproducible builds are deterministic. LLMs producing a different output each time are not.

    it is a task of a programmer to review it before publishing it.

    Tell that to my coworkers. It’s honestly insulting the code I have to review and contribute to. Having used these tools myself, I’m better off writing the code myself.



  • Same situation for me (lots of family and friends who have autism), and I agree. Talk to people with autism. They will be your best source of real information.

    Also, everyone has different needs, and autism differs quite a bit between male and female, so try to get a wide range of experiences.

    It also helps to consider what level your kid was diagnosed at because the needs for a nonverbal L3 are very different from a L1.





  • You can get something like a NexDock that has all of that built in. Just 1 cable.

    Maybe I’m missing something, but how is this more convenient than a laptop? It has the form factor of one, so you’re already stuck carrying around what is basically a laptop. Wouldn’t a super cheap Chromebook or similar be more convenient since it’s a full desktop experience with all you’d expect from a desktop environment?

    Anyway, working entirely on mobile is a thing these days, so if that works for you, keep doing what you’re doing. If all you need is a bigger browser, I’d also recommend a tablet with a detachable keyboard. If you want to keep the experience consistent between devices, honestly I’d suggest an iPhone and iPad (as much as I avoid Apple myself).



  • In all, the poll found that 70% of Democrats, 60% of independents, and 51% of Republicans opposed redrawing congressional maps in the middle of the decade, and that “large majorities” support the US Congress banning mid-decade redistricting.

    Want to know a good way to undo gerrymandering? Vote for someone who isn’t doing the gerrymandering. If enough people do it, it kinda fucks up their plan.

    Anyway, having lived in MO, this isn’t going to happen. A huge number of people vote R like it’s some kind of religious cult. I guess that’s not far off from what it actually is, though.



  • For what it’s worth, there are a lot of people across the sound who either work remotely or commute everyday (mostly to Seattle). The ferry, in travel time alone, is ~45m (from start of boarding to end of getting off, assuming you take the car you’ll need with this commute). This is of course assuming you make the ferry and don’t end up waiting for the next ferry or two due to traffic (each ferry carries only so many cars), and assuming no issues with their schedule (they are behind all the time).

    Brinnon is a weird example, but an example involving the ferry isn’t too far fetched. I have a friend at a big company who lives on that side, and I considered it myself (and would have, had I been able to afford the home I wanted anyway).

    Without traffic, Bainbridge Island to Redmond is ~1.5h. With traffic? Not happening.

    Good news about MS specifically is that it does have the connector (their commute busses). It doesn’t go everywhere, and definitely not across the sound, but does help with some commutes if you happen to be close to a stop.

    Anyway, RTO has historically been a terrible policy designed to shrink the workforce without layoffs and has resulted consistently in worse outcomes for companies.



  • But recently, players have found a version of Mono-Red that is rebalancing the scales. Not only is it more played on the MTG Arena ladder, but it has a better win percentage against the field and is knocking off Vivi Cauldron decks at a clip above 60%.

    People play mono red on Arena because it’s easy to craft, especially if you already crafted mono red the last time it was the best deck in standard. Also, mono red having a good winrate against Vivi means nothing. There were only two colors represented in the top 8 of the spotlight series, and all 8 decks had red. That’s not exactly a sign of a healthy standard.

    We believe Standard play may be hurt in the short term by one or two dominant decks. Long term, it is certainly hurt by banning decks out from under players in a surprise move.

    Long term, the format is hurt by players not playing it at all. Who cares about banning cards in a format nobody plays. RCQ players are supposed to be good at Magic. Let them adapt their strategies.

    While we acknowledge that high-level competitive Standard is lopsided, the majority of Standard play is not. The MTG Arena ladder isn’t nearly this distorted,

    MTGA ladder is a garbage test for the decks people play in standard. To begin with, matchmaking affects what decks you play against, whether it’s based on MMR or card scoring.

    and in-store play isn’t nearly this distorted.

    What in-store play? We’re talking about standard, right?

    Anyway moving the ban date up is good, but it’s still 2 months away, and this doesn’t address the core of the issue at all. Why do cards need to be banned this frequently? I think we all know why, but WOTC sure seems to not care.