itsjustjordan

I just swapped all my Claude code spinner verbs to be Warcraft related and was thinking today how I could get it to say “Jobs done” when it needed my attention

Slightly related but today I learned if you Google a font the site changes to that font.

Curious as to how, assuming a successful push in this direction, will affect web design and browsers in general. I potentially see a future where, like responsive design for mobile devices we end up with an "llm-optimised" version of websites.

I was going insane doubting my SSH knowledge, stopped short of creating new keys thankfully!

Sold to CNN in 2016 for $US25M

Surely in 2024 we can't be classifying Stripe as just "a payment service"

That would be because their goal is tooling and not to be a framework? Bun is the worst example here cause it's literally now a runtime for Javascript! If rewriting all the Node APIs, directly executing TS files etc. isn't pushing a "paradigm" I don't know what is.

Small website bug, hovering over Make.com in the integrations tab on the homepage shows the link and icon for Zapier. Congrats on the launch!

I'll flesh out my comment a bit more with a small example of what I mean.

We have an inbox list that is a combination of three different entities (direct message, job request, support message), we display all of these in a unified inbox, rather than pulling all the data with REST and sorting through what fields to use to display as a title and what status maps to which styling/label etc. I can just use my InboxPageQuery and render exactly what it tells me to, being able to build or change entire pages just by pushing new server code really helps with speeding up our dev time.

  {
    "data": {
      "inbox": {
        ...
        "inboxItems": [
          {
            ...
            "subtitle1": {
              "__typename": "InboxStandardText",
              "accessibilityText": "Hi Jordan.\n\nSarah has posted a handyman job near you",
              "components": [
                {
                  "__typename": "InboxStandardTextComponent",
                  "text": "Hi Jordan.\n\nSarah has posted a handyman job near you...",
                  "type": null
                }
              ]
            },
            "subtitle2": {
              "__typename": "InboxStandardText",
              "accessibilityText": "You declined this job today",
              "components": [
                {
                  "__typename": "InboxStandardTextComponent",
                  "text": "Declined",
                  "type": "errored_text"
                },
                {
                  "__typename": "InboxStandardTextComponent",
                  "text": " · ",
                  "type": "errored_text"
                },
                {
                  "__typename": "InboxStandardTextComponent",
                  "text": "07/06/23",
                  "type": "errored_text"
                }
              ]
            },
            ...
          }
        ],
        ...
      }
    }
  }

Like most technologies it depends on how you're using it. When I first starting working in GraphQL, paired with a React frontend I used it in an a similar way to REST, pull the data and then do all the logic of what to display on the frontend.

For me I saw the most benefit when I used the schema to define what to display in the frontend, all the logic of what to display is done on the server and my frontend just becomes simple components that render the pulled schema.

Work daily on a Mac and use a mouse and trackpad simultaneously, I find the trackpad the quickest for navigation but need the precision of a mouse. Wonder how a setup similar to this would go instead of the trackpad.