Jenk

Every time you run `wsl --install <distro>` you are creating a new VM. Every time you run `wsl --unregister <instance id or name/>` your are removing a VM.

It is these two operations at the heart of OP's app.

    diff --side-by-side

or use `-y` for short-hand.

Unfortunately not. Git clean still tries to, well, clean it. Unless I goofed it, which is a >0 possibility, I will happily concede.

Since using jj I'm on the lookout for some kind of setting that will exclude the .jj folder from the repo _and_ any operation including git clean, without having to add it to the repo. I.e., make it completely invisible to git including `git clean -xdf`!

At the moment I'm making do with aliasing `git clean -e .jj`

> In the 20 years I've worked in software. I've never even seen a shop that works this way. From 20 person teams to 10,000 employee companies. Maybe I've been lucky. but to me it reads as a straw man. Something to punch against that doesn't really exist

30 years ago it was the norm. It really is true that the industry (standard) has shifted a lot in that time.

But I work at a place like this right now. I was hired by the new CTO to help them change this, having spent the previous 20 years actively avoiding places just like this.

Project-based planning by a roomful of not-technical people: Funding, scope, design, shape of team, deadlines, tech stacks, vendors etc. all "locked in" before any engineer is even approached, let alone asked for input.

I cannot overstate how uncanny it feels to be working here - like I have actually time travelled back to the 90s.

Frameworks are a category of development tool. Things that developers utilitise to be productive.

They licensed Brassic, it was filmed for Sky One, not Netflix.

I've worked at many big banks and corporations. They are all held together with the proverbial sticky tape, bubblegum, and hope.

They do have multiple layers of redundancies, and thus have the big budgets, but they won't be kept hot, or there will be some critical flaws that all of the engineers know about but they haven't been given permission/funding to fix, and are so badly managed by the firm, they dgaf either and secretly want the thing to burn.

There will be sustained periods of downtime if their primary system blips.

They will all still be dependent on some hyper-critical system that nobody really knows how it works, the last change was introduced in 1988 and it (probably) requires a terminal emulator to operate.

It started long before that. Cloud meant they were under drastic threat of being abandoned, because the cloud was (and still is) dominated by linux compute.

DotNet were shook, and shook bad. They went all out to make their runtime "cross-platform" because they faced an existential thread from lamdba+node.

The rise of the MBP also saw their dotnet ecosystem under thread from the other end of the stick - the developer end. Visual Studio cannot run on macos, so competitor IDEs that can were rising in their numbers. Hence the push for VSCode to try and claw back some IDE market.

> It was the correct paradigm all along

Debateable.

I can see value in this. I use which-key already and could see a graph, al be it a differently arranged graph, being a useful visual aid. Perhaps a static (printed?) Cheat-sheet or even a dynamically generated visual - though not sure how effective it would be in a TUI :)

I explain it to my peers as "exploiting Cunningham's Law[0] with thyself"

I'll stare blankly at a blank screen/file for hours seeking inspiration, but the moment I have something to criticise I am immediately productive and can focus.

[0]: https://en.wikipedia.org/wiki/Ward_Cunningham#Law

> The best way to get the right answer on the Internet is not to ask a question; it's to post the wrong answer.

Advertisement.

You may be interested in the Glove80[0]. I moved from the Moonlander to it for the very same reason. I have since moved on to a very small form-factor (Pteron36, which has just 36 keys) as I my hands started to tire from reaching for the keys on the perimeter so chopped right down.

Or get the soldering iron out and build one of the many kits available[1]

[0]: https://moergo.com

[1]: https://golem.hu/board/list/low-profile

Does Attaullah Baig?

It can also be that the repo was modified after a release.

That double wall thing is a red herring. The water system already protects against intrusion because the water itself exerts pressure on the pipes. Thus leaks are typically of the water getting out and not contamination of the water (most of the time, anyway.)

Contamination rarely happens outside of the source of supply, and not somewhere along the pipeline.

SEO already killed the www.

> They never fix the defaults

Not strictly true. They did change the default push behaviour from "matching" to "simple" in Git 2.0.

Why shouldn't "causuals" (and/or "professionals" for that matter) be allowed to use AI for some reasoning or whatever?

One of Claude's "categories" is literally "Life Advice."

I'm often using copilot or claude to help me flesh out content, emails, strategy papers, etc. All of which takes many prompts, back-and-forth, to get to a place where I'm satisfied with the result.

I also use it to develop software, where I am more appreciative of the "as near to pure completions mode" as I can be mot of the time.

Firends who are windsurf employees tell me the in-office opinion is that the founder(s) were paid $.5bn each, and the rest was distributed amongst the researchers they poached.

_Huge_ payday if true.

What about

    ln -s AGENTS.md CLAUDE.md # repeat for all

?

You may be interested in https://www.chezmoi.io/

.. or just

    type MergedType = TypeA & TypeB

The one paragraph that helped jj begin to click for me was this one from Steve's Jujutsu Tutorial[0]:

> If you want to replicate git's behavior, typing an additional command after each change is done feels like overkill. But I would argue this is not the right way to use jj; as you'll see, we'll be either re-writing commits at the tip of branches, or doing multiple steps of work before updating where a branch points. In practice, it means I check the branch status before pushing code, rather than as I work. That is, the branch name tends to sit at the same change as the remote server, and when it's time to update the remote, that's when I update things locally.

[0]: https://steveklabnik.github.io/jujutsu-tutorial/sharing-code...

(emphasis mine)

That, as I interpreted it, is to mean one should begin to "forget" git in order to appreciate jj with a sense of new beginning.

Previously, I was continuously translating jj to git, and vice-versa. After reading this paragraph, I now mentally model the jj-git relationship as a kind of 3rd stage of the workflow, rather than previously assuming jj as an abstraction on top of git.

    document.querySelectorAll("[type='checkbox']").forEach(c => c.checked = undefined)

Adjust the selector as neccessary, sometimes I'll use `#id-of-cookie-banner [type='checkbox']`

Probably useless for mobile though, unless you can punch it in the omnibar with `javascript:` prefix

Extra nitpick.. green isn't even a primary colour. Red, Yellow, Blue are the primary colours that our eyes perceive. Perhaps this contributes to why the RGB numbering doesn't meet human perception of green?

Or the quartermaster with a penchant for nifty gadgets from MI6.

I'm not the person you asked.

The below type definition (TS) fits the ECMA schema for JSON:

    type JSON = 
      string |
      number |
      boolean |
      null |
      JSON[] |
      {[name: string]: JSON}