(Typo in the title.)

Thanks, this is really interesting.

I feel like it adds more weight to my feeling that we should have a software building code. When you have software that's critical infrastructure, with a nutso security policy like "no embargoes / 0day me bruh", we should have some regulations in place to require the software be maintained properly (that is to say, in a sane manner) or you can't use it commercially or for safety-critical things. Which would inevitably force commercial entities to pay for the maintenance so it could be done right.... which they should be doing already, the same way any company that builds safety-critical infrastructure has to pay to do it right.

If we want society to be safe, we have to make a law that enforces it. That's how that shit works.

(as an aside: holy shit, you're a prolific HN submitter, and all from different sources. where do you get it all?)

It's not out of the box. It works on my omz shell, although I didn't do anything to specifically enable this since it never bothered me to type cd and I kinda hate "magic". On an out-of-the-ubuntu-box zsh, it doesn't work:

    % cd /
    % bin
    zsh: command not found: bin

    setopt AUTO_CD

Business leadership is technical, they create the requirements with technical leaders, those leaders build out the roadmap. I don't believe in 'agile' but I think 4-6week chunks of work broken off and worked on by a small team (2-4 people) works well. I like to see small design doc to ensure open questions are ironed out that gets signed off on by stakeholders - everyone should be committed on the vision and these signoff should happen relatively quickly, ideally comments resolved and go/no-go decision within a week.

The small team should have a lot of support in terms of an infrastructure platform, strong culture and tooling for development/testing, project management set up for them, an escalation path and check-ins where they can raise blockers. There is a template but essentially the small team is left to work how they want to work.

After the 'chunk' is delivered, there is a week of wrap up, and then a week of maintenance where people are allowed to work on whatever they think is the most pressing issue.

“when the user is fingered” ?

This sounds like it's not actually true? If it was, the French code page 646 that we used until Unicode finally won would have included a narrow space, but it doesn't. "Regular" computer text in French has only ever used a normal space, even if handwriting and/or "true" typesetting using typesetting solutions like TeX or PageMaker etc. allowed for a narrow space.

As the co-founder of Apache Jakarta and first hearing about this Jakarta EE thing just now, which also seems Java (tm) related, it seems like a weird overlap in naming.