happimess

> Conceptually continuous integration is generally integrating 2+ different lineages of code together

> 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?

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?

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.