Andy Balaam

@andybalaam
1.8K Followers
414 Following
5K Posts
Makes coding videos, podcasts, free software.
Homehttps://artificialworlds.net
Bloghttps://artificialworlds.net/blog/
Videoshttps://video.infosec.exchange/a/andybalaam/video-channels
OpenPGP078C05BC7BC6CD49A8D83441FC8DD3B1BA7F5E13

🚀 We’re pleased to showcase the work of our software engineer summer intern, Skye, in this technical deep-dive blog post.

Skye’s work on encrypted state events helps ensure sensitive room information stays hidden from homeservers.

Internships are part of our culture. In fact, around 20% of our engineering team first joined us as interns đŸ’Ș

https://element.io/blog/hiding-room-metadata-from-servers/

Hiding room metadata from servers

Every year, Element takes on a small number of summer interns to work on various research and development projects. Internships are a significant part of our culture, and ~20% of the current Element engineering team has completed some form of internship with us before joining permanently. This year, our interns

Element Blog

Since when was vibe coding not an insult?

https://www.theverge.com/news/787076/microsoft-office-agent-mode-office-agent-anthropic-models

“Today we’re bringing vibe working to Microsoft 365 Copilot with Agent Mode in Office apps and Office Agent in Copilot chat,” says Sumit Chauhan, corporate vice president of Microsoft’s Office Product Group. “In the same way vibe coding has transformed software development, the latest reasoning models in Copilot unlock agentic productivity for Office artifacts.”

Microsoft launches ‘vibe working’ in Excel and Word

Microsoft is launching new AI tools in its Office apps. A new Agent Mode comes to Word and Excel, alongside an Office Agent in Copilot chat.

The Verge
F-Droid and Google's Developer Registration Decree | F-Droid - Free and Open Source Android App Repository

For the past 15 years, F-Droidhas provided a safe and secure haven for Android users around the world tofind and install free and open source apps. When cont...

Happy Petrov Day to those who celebrate. On September 26, 1983, Stanislav Petrov made the correct decision to not trust a computer.

The early warning system at command center Serpukhov-15, loudly alerting of a nuclear attack from the United States, was of course modern and up-to-date. Stanislav Petrov was in charge, working his second shift in place of a colleague who was ill.

Many officers facing the same situation would have called their superiors to alert them of the need for a counter-attack. Especially as fellow officers were shouting at him to retaliate quickly before it was too late. Petrov did not succumb.

I've attached a short clip from a reenactment of the situation in the documentary The Man Who Saved the World.

The computer was indeed wrong about the imminent attack and Petrov likely saved the world from nuclear disaster in those impossibly stressful minutes, by daring to wait for ground confirmation. For context one must also be aware that this was at a time when US-Soviet relations were extremely tense.

I've previously written about three lessons to take away from Petrov's actions:

1. Embrace multiple perspectives

The fact that it was not Stanislov Petrov's own choice to pursue an army career speaks to me of how important it is to welcome a broad range of experiences and perspectives. Petrov received an education as an engineer rather than a military man. He knew the unpredictability of machine behavior.

2. Look for multiple confirmation points

Stanislav Petrov understood what he was looking for. While he has admitted he could not be 100% sure the attack wasn't real, there were several factors he has mentioned that played into his decision:

- He had been told a US attack would be all-out. An attack with only 5 missiles did not make sense to him.
- Ground radar failed to pick up supporting evidence of an attack, even after minutes of waiting.
- The message passed too quickly through the 30 layers of verification he himself had devised.

On top of this: The launch detection system was new (and hence he did not fully trust it).

3. Reward exposure of faulty systems

If we keep praising our tools for their excellence and efficiency it's hard to later accept their defects. When shortcomings are found, this needs to be communicated just as clearly and widely as successes. Maintaining an illusion of perfect, neutral and flawless systems will keep people from questioning the systems when the systems need to be questioned.

We need to stop punishing when failure helps us understand something that can be improved.
I spend all my day in neovim and it makes me happy. Today I'm using an IDE and the code is in a little window in the middle. Every time I move my mouse something pops up at me. It's painful.

Jez and Andy write a parser

https://video.infosec.exchange/w/hEriRbWo4Q35h8K9xfUtGr

After we finally finished gossiping, Jez started on a parser for my made-up language Cell, in Rust.

#video #rustlang #programming

Jez and Andy write a Parser

PeerTube

@andybalaam Had to handle a couple of error cases we don't have tests for in js-cell or p-cell 😼

https://birmingham.jezuk.co.uk/forgejo/jez?tab=activity&date=2025-09-25

Jez Higgins

Forgejo is a self-hosted lightweight software forge. Easy to install and low maintenance, it just does the job.

JezUK Ltd: Software created, extended or repaired

Nvidia and openAI are talking about building a 10GW data centre.

So. We gots a big number. Let's look at it.

How much is 10GW? Well the UK has a typical day time electricity consumption of ~40GW. Meaning that this one single data centre is looking to use the same amount of electricity as a quarter of the UK. In a single installation. A quarter of the electricity of the 6th largest economy in the world. A single data centre.

Or put another way. It needs power from 3x sizewell C nuclear plant.

Today I am mocking things I do not understand.

^ programming status, not life status