A "full stack" Open Source enthusiast, creating http://olivetin.app, and other no-nonsense open source software.
Dad, hobbyist developer, open-source enthusiast and Red Hatter. Find my Blog, GitHub and contact details at http://jread.com
| Code, Containers & Cloud blog | https://blog.jread.com |
| GitHub | https://github.com/jamesread |
| Homepage, and more of me | https://jread.com |
OliveTin has been getting a lot of security scrutiny this week - as there’s been a relatively huge surge of security advisories come for the first time. I imagine that the project has been listed in a security forum or similar, and AI tools (and human eyeballs) are being used to looking for security vulnerabilities. This is a good thing, and I welcome more security reports, that will be patched, and will make OliveTin better.
AI tools are moving fast—from fancy autocomplete to fully autonomous development teams.
The real question isn’t whether to use AI, but how much autonomy to give it.
I put together a simple 0–5 model to describe these levels of autonomy in practice:
https://blog.jread.com/posts/ai-levels-of-autonomy-in-software-engineering/
AI tooling for software engineering has moved quickly from fancy autocomplete to the verge of fully autonomous engineering. Most people can see that AI adds value. The real question is no longer whether to use AI, but how much autonomy to give it. Capability alone doesn’t justify maximising autonomy everywhere. You have to match autonomy to risk. This post defines a simple scale of autonomy levels and where I draw my own lines.
Anytime an exciting new web technology starts to land in browsers, developers want to know “when in the world am I going to be able to use this?” Currently, the finalized syntax for Grid Lanes is available in Safari Technology Preview.
