Mistral Vibe & Antigravity, Retro, HTTP/Vary, Critical Code, SSS

1. Vibe Coding - With a friend we tested Google Antigravity and Mistral Vibe CLI on different projects. Mistral Vibe CLI is excellent, but it requires quite detailed instructions and split into smaller tasks for execution. If you'll give it too high level instructions it seems to go into inefficient loops and or create absolute and complete mess. For very simple testing project both projects received instructions like make countdown timer, which runs N minutes until zero and shows message NOW, when time is up. When < 50% of time is left, text should be orange and when 25% is left, it should be red. As well as you should use large font for CLI like ASCII text / banner. Also include --test option, which allows the code logic to run without the delay, for testing the logic. All of that worked great as single shot development task. No, it didn't generate code all at once, but I enabled auto accept mode, which allowed it to work around problems, which it successfully did! Fun times, after the initial test program was written in Python. I just asked Mistral Vibe CLI to port it to Go, Rust and PowerShell for posterity. It required several refinement steps, so the Devstral-2 model doesn't do everything that's necessary. Probably trying to save resources, yet that leads to invalid outcome. Always make sure that the TEST PART and WHAT TO TEST and HOW TO TEST is quite detailed. Yet it did some interesting things, because Python version used pyfiglet to produce large ASCII font, it also prompted the font to PowerShell, Go and Rust, because I said it needs to works similarly, and there was no matching library available. - Fun times. And when it did that, it first messed up some numbers and then it messed up with white space. I had to again say, that you have to make sure that the output exactly matches, whatever it takes. Make sure that the white space is also matching, and if necessary, generate new test functions so you can easily test the digital rendered "font" outputs. Also as expected, escaping and special characters caused also secondary problems. Oh joy, I've often said at work, that escapes and or sanitization is more often wrong than right. So... Yeah... Not unexpected at all. And actually the white space seemed to be really hard for it. Maybe LLM / some layers somewhere strip some of the output for efficiency again. So you'll have to ask it to dump the output to file and xxd it or something like that, otherwise it misses some of the whitespace from outputs... - Legendary.... It just run loops before I said, use xxd to get the thing bleeping right...

2. Retro - People making "retro" videos with a terminal and smooth scroll - bleep that! They belong to the same club as those applying a VHS effect to videos. If you've repaired a few VHS decks, you know very well that isn't a true VHS effect. There are fundamental reasons why the hardware behaves the way it does. As usual, everything affects everything. The same applies to simulated camera views with microprism rings or split-image rangefinders. You can't just "add something" in the middle and think that's it.

3. HTTP Vary (@ Wikipedia) - The header, I think I've not been always using it when it should have been necessary. Oops. Well, now I've reminded my self about it. At least it didn't lead to any known issues. I just figured out when checking zstd related compression stuf with H/3 and Nginx.

4. Critical Code - Watched / Attended - Critical Code: Leading Secure Software Development – Webinar 2025-11-18 (Kriittinen koodi: Turvallisen ohjelmistokehityksen johtaminen -webinaari 18.11.2025)

5. SSS (@ Wikipedia): ssss, shamir-mnemonic (SLIP-39) and K-of-N-XOR-Secret-Sharing (https://github.com/alexsapps/K-of-N-XOR-Secret-Sharing) - Lovely. It seems that there's no single wide spread standard for secret sharing either. I guess the shamir-mnemoic is the best option popularized by crypto-currencies, but otherwise is known problem, with known solutions. But tooling and standards are really lacking. Yet I don't understand why that solution is made so limited on purpose. There's no reason to fix the K=3 and N=5 at all.

2026-05-24