Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)EX
expr @programming.dev
Posts 0
Comments 244
Is my punctuation correct?
  • It depends on the country. This is true in American English and it's what we teach in schools. In British English (which, in my experience, is what most ESL learners outside the US end up learning), they go outside the quotes. Source.

  • Deep Fried Ranch
  • It's actually hot sauce specifically that has a tendency towards intentionally weird names. Don't know how it started exactly, but at this point it's a pretty common marketing gimmick.

  • If it ain't broke
  • Speak for yourself. I don't use LLMs and never will.

    It always irks me when people talk about it like it's universal and inevitable when that's very far from the case. There are many, many issues with them and many developers wisely choose to ignore the fad.

  • Trying to understand JSON…
  • It's about making APIs more flexible, permissive, and harder to misuse by clients. It's a user-centric approach to API design. It's not done to make it easier on backend. If anything, it can take extra effort by backend developers.

    But you'd clearly prefer vitriol to civil discourse and have no interest in actually learning anything, so I think my time would be better spent elsewhere.

  • Trying to understand JSON…
  • As I already said, it's very simple with JSON Patch:

    [
      { *op": "replace", "path": "/Name™, "value": "otherName"}
    ]
    

    Good practice in API design is to permissively accept either undefined or null to represent optionality with same semantics (except when using JSON Merge Patch, but JSON Patch linked above should be preferred anyway).

  • Trying to understand JSON…
  • The semantics of the API contract is distinct from its implementation details (lazy loading).

    Treating null and undefined as distinct is never a requirement for general-purpose API design. That is, there is always an alternative design that doesn't rely on that misfeature.

    As for patches, while it might be true that JSON Merge Patch assigns different semantics to null and undefined values, JSON Merge Patch is a worse version of JSON Patch, which doesn't have that problem, because like I originally described, the semantics are explicit in the data structure itself. This is a transformation that you can always apply.

  • Trying to understand JSON…
  • Zalando explicitly forbids it in their RESTful API Guidelines, and I would say their argument is a very good one.

    Basically, if you want to provide more fine-grained semantics, use dedicated types for that purpose, rather than hoping every API consumer is going to faithfully adhere to the subtle distinctions you've created.

  • Trying to understand JSON…
  • Only if using JSON merge patch, and that's the only time it's acceptable. But JSON patch should be preferred over JSON merge patch anyway.

    Servers should accept both null and undefined for normal request bodies, and clients should treat both as the same in responses. API designers should not give each bespoke semantics.

  • Seriously, where do I go?
  • Omaha is a lot less left-leaning in my experience. It's very purple. Lincoln is solidly blue.

    I just recently purchased a house in Lincoln. Just quickly looking on Zillow for Omaha and home prices look to be very similar to what I was seeing here in Lincoln. Property taxes in Omaha are also a fair bit higher than Lincoln.

    There's other stuff too, like lower crime rate in Lincoln, better/more parks, LPS being generally a lot better than OPS, etc.

    I guess it ultimately depends on what you're after. If you want something more big city, then Omaha obviously has Lincoln beat. But for a more relaxed pace of life and for raising a family, Lincoln is where it's at.

  • Firefox user loses 7,470 opened tabs saved over two years after they can’t restore browsing session
  • Your history is already sorted by most recently used. If you just open the history search drop-down without typing anything, you can tab through your most recent pages.

    History search works with more than just the title, it's also can match words in the description, keywords in the page, or I believe just about any piece of HTML metadata. After using this feature for years as a software engineer viewing plenty of obscure or obfuscated webpages, I've never had it fail to find me the page I want. I simply type a word associated with the thing I want to view, and every time I can easily find the page I'm looking for.

  • Seriously, where do I go?
  • There are a number of blue cities in the Midwest. What's the lowest temp you want? I live in Lincoln, Nebraska and it's pretty great: nice weather most of the year, low cost of living, blue city, tons of parks. Only downside is dealing with red state bullshit from the state government.

  • Firefox user loses 7,470 opened tabs saved over two years after they can’t restore browsing session
  • I can easily do that in a day of work because I often have to reference documentation from many different sources.

    I'll probably have 1-3 tabs for jira boards/tickets, a couple for gitlab merge requests, at least a few for the documentation of different third-party libraries I'm using, a few confluence pages, a few for different specs, 1-2 for Figma designs, a handful for different admin panels I need access to, a couple production dashboards/logs, in addition to whatever searching I need to do. I usually clear them out at the start of the next day, but they can add up pretty quickly.

  • Firefox user loses 7,470 opened tabs saved over two years after they can’t restore browsing session
  • You can search through your open tabs by typing % followed by space in the search bar. I often do that since I tend to reference a lot of documentation/merge requests/admin interfaces/etc. and end up with quite a few tabs in a working session (usually clear them out the next day). Nowhere near 7000, though. Maybe 50.