Is there a generic (non-brand) name for these boiling-water faucets? (That’s not a mouthful like “boiling-water faucets”). I think we call them quookers here, which is also a brand name, and I slightly dislike that practice. I mean, “brand name for generic thing” is very common, but the brands and things differ per country, so it’s like a layer of jargon to decipher.

I do my time tracking in org-mode, and export it to JIRA once a day or so. It is quite a specific/tailored setup, written in a mix of elisp and, well, org-mode (specific names and tags are used to configure some settings), but I’d love to look at this tool to see if I can extend my workflow by using it for the “massaging into a nicer shape” part. I might end up writing some extensions for either side (org-mode input format and JIRA REST calls output format).

My current tooling quantizes everything by rounding start and end times to the nearest full 15 minutes, and starting a new task at the end time of the previous one when clocking in, so that my team lead does not have to report so many fractions of hours to higher layers.

I hear the GOAT is even better.

No need. Only the average Dutchman. And he’s only average, so…

Was the solution there to just boot an older/previous kernel?

Probably understood that in the wrong direction. Ze (eng. phon.) would be spelled more like “sie” (ger. phon.) and would sound like “the” with a German accent. They would become either dey (eng. phon.) or zey (eng. phon.), spelled like “deej” or “seej” (ger. phon.), or even without the y (or j) at the end.

I think. I’m neither native German or English.

As Flatfire mentions, another issue can arise if plugins can modify the config. I assumed config to be read-only for the software, only editable by the admins, and never by the tools themselves.

I’d try to share the config space as much as possible. Options 1 and 3 make sense then.

What feels “right” to me, when using NixOS and its module system, is that all config has the same shape, and is therefor easily moved to a different section, or to a section that is shared by a subset of plugins.

Con: It could lead to bad practices like strengthening dependencies between plugins (if they hard code to use a specific config option of another plugin).

Pro: But if you can discourage that, or use “deprecated pointers” to the new location of an option, the ease of moving shared config options to a more generic level can make it easier to maintain the total configuration. Developers of the separate plugins can build on what others have already done, and even synergize functionality (add a convenient integration if they see another option configured).

If some options are “secret”, though, and you don’t want those shared, they should either be in their own config (easier), or you’d need some access control on the configuration storage/file for each plugin (more work). Allowing a plugin to have a separate file for credentials, for instance, could be a good choice.

That is an interesting source. Thanks for the link!

This is still salvageable by pronouncing it as “an earl”.

I agree, and I love how it has these younger words with a vivid etymology, how it shares so many common roots with English, German, the Scandinavian languages, and a serving of French, but also sprinkles of many other languages from its seafaring and otherwise trading history. And I love the grammar rules that allow one to be precise and concise in many things (but there we must definitely bow to German).

Water bearer makes much more sense, thanks! I did notice the images where a guy carries a jug, but as a kid, I always imagined the water man to be some kind of elemental, and I never consciously challenged that idea. Haha.

In Dutch we don’t use the Latin names for zodiac signs (and we call them “sterrenbeelden”, which means “star images” or maybe “star statues”). Aquarius is “waterman”, which I guess would translate to (surprise) “water man”.

Why? Not sure, but it might be because of Simon Stevin who insisted we use Dutch words for mathematical concepts, and thought up some words like “evenwijdig” (“same distancey”) for “parallel” and “wiskunde” (“certainty knowledge”) for mathematics.

👏👏👏👏

git was designed to be decentralized. Everyone can (technically, but it is not too hard to set up if you have some affinity with servers) fork/clone another git repository and serve it up. It has built-in ways to synchronize with any other server. In fact, that synchronizing is what most developers do when they use git.

Of course, that would make it harder to know which repository has the “official” version, but in a way, that is maybe also a benefit of decentralisation. Knowing what code is authentic can be done by signing the commits.

The hubs that we see, are usually a combination of git and a way to serve the code, along with documentation, roadmap, bug tracking, automatic testing and building and the resulting binaries in a visually pleasing way. That does not need to be a part of decentralizing the code, and it is not the only way to do it.

Some of that can also be done with git built-in tracking of files, and the building and testing can probably also done in other locations, as long as there are files describing how to do that bundled with the code (which practically all projects already do).

Sourcehut (https://sr.ht) is one hub that helps developers use simpler tools for those workflows, and I think that’s a good place to find some inspiration.

I will never not read LTT as Lews Therin first, of whom, as a lover of both FOSS and EotW, I definitely prefer being reminded.

E: my brain forgot that the series is called WoT. EotW is just the first book, indeed. But I’m rambling very much off topic here.

At least the sawhorse resembles a horse :)

Like the Dutch “ezel” (which is the same word used in Dutch for painting-supporters which in English are called “easel”).

You can see the wololo-waves radiating from a cross if you put it in the earth.

Don’t worry about feeling angry. That is a normal emotion when things happen out of your control that you would like to be able to change. It is the emotion that tries to give you an extra impulse to move from a state of inaction or fear to a state of action to change it or prevent it in the future. Normal emotion. But just not always helpful if the thing you want to change is still outside your control.

Just do not let that anger turn via blame into hatred. That can happen if it is hard to change the things you would like to change, and the anger starts getting directed at the things or people that you feel as “doing nothing to help”, “doing the opposite of helping” or even “the cause of this problem” and stays there. Again, it is normal to feel anger or blame here. That can help to find ways to change something, but from there it can slide into seeing those things or people as “enemies”, the root cause of everything you would like to be able to change, the opposers and blockers and the evil that wants to keep your thing from ever to change. That is where hatred lies. Anger that cannot be resolved unless something or someone else changes.

You can also use that anger and blame to find constructive ways to make the change. As other people mentioned: grieve together. Find out that they are as helpless as you to change what is past. That they are as afraid as you of things outside your control. That they also feel the pain of loss, and would also like to prevent this from happening again. Bring food, talk, listen. Everyone wants to feel seen, heard, and trust that they won’t have to keep fighting or be forgotten if their needs aren’t met, but be able to find support and care in the people around them. By sharing and showing these kindnesses, you can build or strengthen these bonds of trust in the community.

Anger is a call to action, and blame can be a way to find the places where those bridges of support may have weakened, where those mutual and basic needs are likely to be unmet. The action can be to rebuild them.