> In practice, CI [often means] "automated test server"

Could you say more? I use "CI" to refer to the automated processes that run tests and (maybe) deploy code as it is merged to some blessed branch. It's what continually integrates the new code into the existing code. What am I missing?

Given that it was inside a 9-step text preprocessing pipeline, it would be surprising if the AI had that much autonomy.

"Drive by" game, to me, sounds like they've got the board set up somewhere in the house, and make moves over the course of a day (days?), rather than sitting across from each other and having dedicated time for the game.

You can write your front-end and back-end in the same language.

No shade to you for finding a productive setup, but Next.js tightly couples your front-end and back-end, no question.

Of course you want your embedded C separate from your CSS! The critique, I think, is that you don't want a front end team, because if your front end is in good shape, then they'll change things just to keep busy.

I listened to it this morning while doing my stoutness exercises, and there's a lot of good wisdom here. I'll probably chase down some of the books he mentions. If you're not concerned with the philosophical preamble, skip to the 5:15 mark.

brief snark: drink when he name-drops Linkedin

My only complaint is that it forces me to restart the program occasionally, for updates. Does anyone know why this is done? Is it a technical necessity? Why can't I postpone it for a few hours?

      ".test" is recommended for use in testing of current or new DNS related code.
      ".example" is recommended for use in documentation or as examples.
      ".invalid" is intended for use in online construction of domain that are sure to be invalid and which it is obvious at a are invalid.
      The ".localhost" TLD has traditionally been statically defined in DNS implementations as having an A record pointing to the back IP address and is reserved for such use.  Any other use conflict with widely deployed code which assumes this use.

I really like it despite its quirks. I love the implicit $in variable. I find the library easy to understand. I'm only using it interactively so if I have to restart my terminal every once in a while I'm not bothered by it. I trust that those sorts of things will get straightened out --- the git repository is very active.

I saw the maintainers in this thread, so shout out for your good work.

The owner bought a crate of enamel pins (this [1] kind of thing, but for long-forgotten social events) from some estate wholesaler, numbering maybe 15,000 distinct pins. He put it in front of the register and gave them inventory IDs as-needed when (if?) he sold one.

[1] https://i.etsystatic.com/25263485/r/il/04c3f8/3721109924/il_...

I believe the researchers are proposing a fungal substrate for PCBs.

It lets me have a bunch of loose acquaintances, both staff and other regulars. I also like seeing people on lunch dates and kids with the day off school and what books people are reading. A bonus is that everyone there is working on different stuff --- artists and video editors and music promoters are all there at various points, doing various things.

I used to have a membership at a coworking space, but I like this better, and in the end it costs about the same.