Nah, just sort by date instead of topology, or vice versa.

git gud, son

Well, I do have MBSE on the brain, but the idea here is more like a low-code/no-code environment with an ABSOLUTELY ENORMOUS “pit of success”… so large that even GenAI can reliably fall into it. Numbered tabs, you go left to right answering questions and fiddling with with prompts, paint-by-numbers for working software.

I imagine that it is theoretically possible to successfully vibe-code, but probably not with a conventional project layout nor would it look much like traditional programming. Something like your interaction primarily being a “requirements list”, which gets translated into interfaces and heavy requirements tests against those interfaces, and each implementation file being disposable (regenerated) & super-self-contained, and only being able to “save” (or commit) implementations that pass the tests.

…and if you are building a webapp, it would not be able to touch the API layer except through operational transforms (which trigger new [major] version numbers]. Sorta like MCP.

Said another way, if we could make it more like a “ratchet” incrementing, and less like an out-of-control aircraft… then maybe?!?

https://consulo.io/ (Basically a liberated jetbrains intellij/rider thing)

That thumbnail image reminds me of hovercat: https://youtu.be/p1u-R4RVL70

IIRC, it opens a gui modal asking if you want to give the terminal permission to read the folder. Not quite the same, but still weird and jarring.

Imagine holding a null in your hand… hopefully they sent you only one, and not zero nulls, or worse… -1… and don’t even get be started on imaginary nulls.

Unit tests pass.

lol… if they had a job that was ONLY writing unit tests, I would take it!

Kind of the reverse… more lamenting the loss of QA and SRE roles in favor of mechanical (AI) code reviewers and non-technical persons rubber-stamping an increasingly deep pipeline that change requests must traverse.

With that typo, it sounds like a personal insult. :)

How’s that workin’ out for ya’, billy boy?

Maybe run a bandwidth speed test, and enable/set qos to 95% of that value… I found that’s an easy way to kill the buffer bloat (way better latency).

Can you imagine what it would be like if all the effort going towards spam mitigation instead went towards fixing (or replacing) email’s fundamental flaws?

A constant stream of value pours out of the fedora project.