dolmen

Go programs listening on TCP have multipath enabled.

> it also helps to split refactoring work into three buckets: business logic changes, performance changes (same output as before but faster) and cosmetic changes (rename files/folders/classes, breaking large files up, add logging/comments, domain layering etc).

Do you have a specific skill to guide an agent to scope the work of an agent so it stays in one particular bucket? Would you mind sharing it?

Some people still want to receive content on their TVs in the old fashion way, using radio waves, even in their more modern form, DVB. Unfortunately a Faraday cage blocks both input and output.

3) Two features of a TV vs monitor:

- built-in audio output - remote control (signals are transmitted on HDMI link, so a PC can listen to them)

What is stopping you?

ESBMC: https://esbmc.github.io/

I think that the issue is not the XSLT implementation (that could be contained), but its deep intégration in the XML stack which is part of web pages processing. Think about XML "processing instructions".

A good plan... if you can afford to maintain your fork forever.

In an XML document a "processing instruction" can trigger the XSLT processor to transform the document in another format.

So an XML document would be parsed and processed by the XML engine, trigger XSLT processor, which would then trigger again the XML processor again and the HTML processor.

So XSLT processing for XML/XHTML is deeply embedded. Dropping it removes a lot of corner cases that AI is good at exploiting.

No. Keep using XSLT server side.

Cool project. Empty repo? https://github.com/justjake/fujimod Not much interested in the code, more in the development process (prompts, skills).

That other thread is interesting as it raises issues about how the organization is managed money-wise: https://news.ycombinator.com/item?id=50082093

Link!

Schedule the morning coffee in HomeAssistant?

If the washing machine is on the network, its manufacturer is already aware about its age.

Could you post the Twitter link?

Because the article is also full of 238 advertisers.

In fact, that festival is apparently named after a man burning on every occurrence. So the casualities are at least 1 every year, and there is a bias towards males.

> because it does ignore, that they are going to react differently to pathogens, food or medication.

But claiming the US 5-races system is more significant as a categorization of people than other dimensions for health issues is definitely racist, and is propagating that systemic racism.

I'm glad to be protected by GDPR.

Like there are people in charge of cows to produce milk and/or meat.

Art and music? Ok for live performance. But recorded performance is directly in competion with genAI for revenue streams, with content used without permission for more genAI training.

> Comparing programmers to farriers is definitely strange on the surface.

Just for another datapoint: two of my great-great-grandfathers in two family branches, in the same small village in France, were respectively farrier and black-smith, while I'm a software engineer. One son of the black-smith continued the trade as a side activity of being a plumber. So I had to think about how my career choice (and those of my siblings, uncles, cousins) relates to theirs.

My own perspective on those trades is that transforming metal was the top engineering scale in the countryside in their era. In those times (XIXth century, early XXth), learning the job required to go work with different masters around France ("tour de France" had another meaning before cycling). While it was still manual work, it was highly skilled job which required both technical skills and creativity, which are also key skills for software engineering.

> You don't need a two pizza team anymore.

Note that AI hasn't yet solved making pizzas.

Similar pain as upgrading a module to a new major version (eg: v1 -> v2) [1], but at scale, because of modules dependencies: every module in the domain are affected at once as they must change namespace, like if everyone changed its major version.

https://go.dev/doc/modules/major-version

If the first part of the module path is without dot, it is assumed to be stdlib.

Many tools will fail if you break this contract.

yourname.internal/mymodule is even better. But don't expect to Go toolchain (especially "go get" or "go mod download") to work.

https://datatracker.ietf.org/doc/draft-davies-internal-tld/

Or if your goal is to open source code, think about the lifetime of the entity owning the domain: the source code might be of interest to users beyond the control of the domain name. Domain controled by an individual or a company? What if the domain is not renewed, or taken over by an hostile entity?

Deepcopy [1] is a Go package that is still heavily used despite its creator has disappeared 9 years ago. At least GitHub is a stable and trusted host as a distribution point and communication point for users.

[1]: https://pkg.go.dev/github.com/mohae/deepcopy

This issue is mentioned on the Opus 5.5 post [1] from Anthropic (no idea if it has been added after your rant):

  > Don’t ask it to show its reasoning in the reply
  >
  > What to do. Remove requests to reproduce its internal reasoning in the reply from your prompts and instructions.
  >
  > Why it matters on Opus 5.5. A request to reproduce its internal reasoning in the reply can be declined. It’s one of the flag categories.
  >
  > How. Ask Claude for what you need instead, for example, “Explain why you chose this approach in three sentences.”

[1]: https://claude.dev/blog/getting-the-most-out-of-opus-5-5/

How long before an AI bribes one of its human operators?

This will happen earlier than AGI.

From the article:

> So I had a decision to make. I could dive back into PHP after almost a decade away, hand the package to one of the people who’d offered, or let it keep sitting there.

We are in the AI era. As a maintainer of an open source project that I haven't touched for years, I would first start by asking an AI to produce a fix for the issue and check what it proposes. This definitely reduces the mental load and risk of breaking an old codebase that so many users depend on.

Deprecating the project is playing the open source game in an other dimension: tell the word that depending on this project was a bad idea in the first place and that everyone should move on. But releasing a fix on a deprecated project is fine too.

So both actions are on different dimensions, this isn't a choice between 2 options.