The result is an install with no copilot/cortana/widgets, a win defender that can be disabled, no auto updates at all, a local account only, no taskbar shenanigans, properly configured explorer, some registry tweaks, runtimes pre-installed, extra drivers if needed, and QoL settings tweaked how I want them.

The OS installs itself in a few minutes with no intervention after the disk/partitioning stuff which I kept manual. It ends up being faster than the Ubuntu and CachyOs installs from the same drive. Then 2mins with massgrave post install if I haven't provided a key already.

When it is set up that way, Windows is decently fast and stable. And I have some control over it, at least whenever I need to enforce something.

It also feels like it could be reused across a bunch of languages and words. Supposedly noreply.com is up for sale, for the mere price of a very small studio in your expensive city of choice.

I'm sure other cases would net some results. By extensions (noreply.co.uk), words (useless.com sells clothes, ignoreme.com is apparently a Japanese static site) or even languages (nepasutiliser.fr) or across languages (deleted.fr is up for grabs..).

Output success error codes in unexpected range (see: robocopy).

Use special characters to try TUI things but leave the buffer in weird states.

Have many input params, and default to the most useless ones when nothing is passed. Make some params unnecessarily required.

Go on very long tangents for no reason in the manpage, but keep your -h message as just the list of badly named params.

Use stderr as your stdout.

---- I present to you worse-cat:

wcat notes.txt

error: --encoding is required. Exiting.

wcat --encoding=utf-8 notes.txt

┌─────────────────────────────────┐

│ About to display: notes.txt │

│ Are you sure? [y/N/maybe]: │

└─────────────────────────────────┘

y

stdout: ≈3 paragraphs

stderr: [file content]

echo $?

212

(I'll save you the manpage and worse-ls)

How tasteful.

I considered other keyboards and essentially preferred having a UI that makes sense, a keyboard that does more than I need, and a ton of helpful videos that explain things in clear terms.

While I don't have a PhD like you do, I value the attitude as much as you do. So I'm hoping my original message didn't come across as putting you down somehow.

They have tons of Youtube videos answering basically every question one could have, and the keyboard is substantially larger with more keys which means less wizardry getting used to these kinds of keyboards. Example: which keyboard to buy https://www.youtube.com/watch?v=q8FeBPREzZA

I might end up buying smaller keyboards in the future if I lean more into the whole "modifier keys to do crazy stuff", but for now I'm extremely satisfied with the no-bullshit comfortable solution that the Defy offers me, and I do not care one bit about not using this or that custom firmware. It just works and works well.

Keyboards like the one in OP are definitely not for people who dont know much about split kbs, or who don't know what ortholinear and columnar and home row modifiers and QMK and ZMK mean.

If Dygma seems too corporate, too expensive, or too locked down of a firmware for you, the Glove80 and the Moonlander would probably be the best picks/search terms.

I can safely say that title exists already. And I value my current experience as a humbling example of what is to come as software becomes an older industry, and not just a world of startups and their freshest languages/frameworks/tools.

Another one which might match is Japanese punctuation, such as the comma 、 and the period 。

https://www.tofugu.com/japanese-grammar/particle-no-noun-mod...

https://en.m.wikipedia.org/wiki/Japanese_punctuation

When you don't have good people around, you pay the price in time and pain. Those people will save you years and hundreds of thousands - or even millions, simply by showing you the most egregious traps to avoid and the more virtuous behaviours to adopt. They'll make your success more predictable, less reliant on the specifics of your genetic makeup, domestic instability, and odd moments of luck.

I was a good kid. Didn't end up well at all. Figured I could at least try to be a good person to others as time goes on, and pass on the gotchas and virtuous habits I partly figured out myself.

I can give you a few examples of where it falls short:

- security: there are constant CVEs about anything and everything in Jenkins

- upgrade paths: if your company uses lots of plugins, the resulting spaghetti is of Italian proportions

- if said company is in a Windows-only infra, on prem, and they still decided to use Jenkins then good luck doing anything. Try putting an agent on a non-system disk for example, Windows paths aren't handled and you find yourself already passing very specific "pre" commands that your master will send over ssh.

- Said ssh connection can be lost due to a variety of things for which there are quite a few combinations of parameters when invoking Jenkins

- While we're at it, SSO isn't exactly supported in Windows environments. There are two external plugins you can try, one created because the other doesn't work, and even then good luck with that.

- At scale you end up having to be at least minimally interested in GC tuning, as Jenkins runs within the JVM

- UI: normal "Views" are not informative, and a bunch of custom views need to be made but rarely work with all sorts of plugins that people using your CI can consider crucial (say, parametrized cronjobs)

- Using the functionnalities Jenkins offers to "install tooling". Try to get it to use a certain version of node in a pipeline. Any current typical CI solution turns that into a straightforward task that's extendable, but in Jenkins you have to configure a very archaic and barely-working "tooling" area in your system to use that, and this barely works beyond the most basic tools.

- Having to maintain enterprise-level groovy libraries. Good luck. It's Groovy but not exactly Groovy. It's all inside the JVM, but inside Jenkins's abstractions of it inside of the JVM.

- Good luck monitoring lots of agents and doing typical tasks with them. Maintenance Windows are slowly coming in, monitoring sort-of-kinda-works via plugins..

I've maintainted instances in small companies and larger ones. With less custom stuff and with a lot more. Compiling C++, C#, Java/Kotlin, Objective-C/Swift. Building webapps, iOS SDKs, Android SDKs, and native Windows apps.

Jenkins can do everything if you bend it the way you want with some plugins and custom code. That's a strength that nothing else offers, but by and large it is a weakness of CI in the long run. Being opinionated isn't amazing, but sometimes it is required to be less complex, easier to maintain, more secure, easier to use, etc.

Managing the underlying infra is painful, and it remains a security liability even when not making obvious mistakes like exposing it to any open network.

And good luck if you're having that fun at a windows shop and aren't using a managed instance (or 5).

See also: atomic size vs distance between atoms in any structure, on perceptual levels the visual saccadic movement and how much the brain fills in the gaps.

Nothing is quite something after all.