joranvar

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.

That is an interesting source. Thanks for the link!

I like that I can hear that omitted space there.

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.

Falkor energy.

Might be doing swiss ball knee tucks without access to a swiss ball.

I would suggest pronouncing "pain killers" in a nice French accent (pan keelUHRZ) when telling the joke. Writing it down might not be necessary then.

ETA: not a native English speaker (nor French). Nor a dad. Also, I tried saying it out loud a few times, and it still misses something. I do see potential, but it might need someone better qualified to fix this completely.

I like the use of the phrase All rights reversed when talking about copyleft.

That depends on what you want to do, and how you define "can it". If your exchange has an API, you could build something that calls that API and shows the results in emacs. It is, in its core, a programmable TUI, after all.

Edit: TUI as in Textual User Interface.

Was going to say something similar. Wit bolletje translates to white little ball, so not far from roll.

We also call them zachte bolletjes or soft little balls. Or just zacht broodje which means soft little bread. As opposed to harde broodjes (hard little breads) which I guess refer to keizerbroodjes (little emperor breads (the bread being little, not the emperor)) which are emperor rolls.

My family is from Limburg, Netherlands, but we may also have been a bit weird. This is just Dutch, by the way, not Limburgish.