happimess

My objection to 'clanker' is simpler: LLMs don't clank.

I wonder how they came up with that. Was it a human idea, or did the AI stumble upon it?

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

I've heard it described as the "exculpative voice".

I suspect that each player has a bowl of stones, and they have 1 lid that covers those bowls. After taking a turn, the player puts the lid over their own bowl so that the other player can easily see that its their turn.

"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 have a monorepo with any tech stack you'd like.

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.

I think you're conflating the coders with the code. I read the upthread comments as advocating against dedicated FE/BE coders, not against dedicated FE/BE code bases.

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.

This is an hour long survey of the accumulated wisdom of a software developer who clearly cares a lot about the craft.

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

This is a really great write up. Kudos for the obvious effort, both on the technical side and sharing the process with the rest of us.

A former boss told me that this is how you make sure only to hire lucky people.

I also bought a house with an ice maker in the refrigerator. I can confirm that it gave us constant trouble until it gave up the ghost. I use ice cube trays in the freezer.

I switched (back) to Firefox a few years ago, and love it.

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?

It seems true, according to [0]

      ".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 have been using nushell for work for about 4 months, ever since I inherited a windows-only project and was looking for a decent shell experience. I'm not doing any extensive scripting, but I do live in my terminal.

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.

Many years ago, I worked next door to a porn shop. A very similar law was passed in our town that would have required the shop to move out to the middle of nowhere.

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_...

The abstract doesn't mention anything about grafting this to human skin.

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

I do, and I really value the time I spend at a cafe near my house. I go to the same cafe (and typically sit in the same spot) every workday for between 1 and 4 hours.

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.

The most secure option is to bury everyone's computer in concrete.

I don't know anyone who watches 5.5 hours of football 7 days a week for 2 years.

Nail polish is very handy for this sort of thing.

I think that the author is speaking about their world, in which they regularly encounter a specific use of trigonometric functions which would be simplified (conceptually and computationally) by skipping the conversion from and into radians.

redefine the known world around a favourite detail

I think that's a good way to think about software optimization. Deep inside nested loops of a game engine (TFA's example code comes from Godot), that's often what you need to do to squeeze some performance characteristic into your hardware.

    s/per-calculus/pre-calculus/g

I think the difference is that if Figma's website goes offline, you lose all of your figma stuff. If penpot gets acqui-killed, then you can just clone a version that you were comfortable with and keep going.

That's right, but "business process" is a much larger solution space than "texture shaders for video games."

It's a pun. The chicken gets hit by a car and dies. It reaches The Other Side.

these are day-camps.

Many summer camps require that you be available to retrieve your kid if e.g. they start showing Covid symptoms. I'd love to drop them off and forget about it, believe me.

I am also a parent coming on the end of a summer, and whitelisting people who _may_ contact me about my child sounds like a nightmare.

Often people simply choose bad abstractions or wrong ones

When writing software, ideally I'd like to make all the right choices and use simple implementations of abstractions that do not impose unwarranted limitations.

I think that it's sometimes worth it, early on, to do things the quick way despite bad abstractions. This can get you to a place where it's easier to reason about good abstractions.

Sadly, I've been on teams where a bad abstraction was adopted because it was just assumed that that would be quicker. Instead of doing it the quick way, we just did it the bad way.

The firmware is open source, and the manufacturer provides a really smooth desktop app for managing different versions.

Presumably, that header graphic is not to scale.