Victorian brick houses are all lime based, pointing (mortar between bricks), render outside and internal plaster. (Ours is 140 years old ish).
Lime is also more flexible (these houses have minimal to no foundation and constantly move), it’s breathable (no/less damp) and as such it also improves air quality indoors. It’s annoying to do because drying times are days/weeks not hours, but long run it’s a far superior material for small buildings.
It does burn though if you accidentally get it on your skin!
It wears down quicker than concrete (you can scratch it easily with a nail and minimal pressure). But we’re still talking 50+ years (before repointing brick, in my case). As long as maintained it’ll last forever (our home is 140 years old, I just re-did the pointing, should be good till I die).
- https://pyinfra.com - Python infrastructure management, been picking up pace recently trying to keep on top of PRs!
- https://kanmail.io - always plugging away at Kanmail changes, no one uses it really except me but that’s fine :) new site designed by fable blew my mind
- https://verified.fyi - first side project started initially as a vibe coding experiment, but it’s become quite good at sussing out dodgy websites
Indeed! (I am that original contributor :)), lots of work ongoing to address this, we now have a small maintainers group and are sharing out review and release loads.
This! Been trying to find the best (least worst) solution to this since 2015 when I started pyinfra. Done ast parsing/hacking, done weird context managers instead, tried rewriting statements to context managers. _if is the latest, and I think least worst, option right now.
Basically a flaw of the entire model where you write code as if executing a single host which is then executed on many in parallel, forcing the two step diff and deploy that causes this.
Funny thing is since v3 this behavior (diff then execute) is even desired with the yes prompt like terraform.
Absolutely zero sympathy. You’re responsible for anything an agent you instructed does. Allowing it to run independently is on you (and all the others doing exactly this). This is only going to become more and more common.
One silver lining this is finally going to push me to switch to a dedicated camera and some niche unrestricted Linux or graphene device as a phone. Goodbye iPhone. (I say this as someone with an Apple account old enough to auto “qualify”, how lucky).
Also parent in the UK - strong disagree, it’s part of our parental responsibilities to set this up, not doing it is the same as not watching a newly walking baby on the stairs (/etc). Compromising everyone’s privacy for a subset of lazy parents is a failing of society.
All of these agent wrappers/claws/whatever seem to encourage wildly irresponsible usage of AI. Sure it can get stuff done in what is effectively a simple loop but without review we’re just playing with fire.
I was experimenting with Claude code doing similar (don’t need wrappers really) and the result was a huge amount of mediocre code and my weekly limit burnt. The code “works” but oh my the duplication and potential bug surface is off the chart.
Stopped my experiment and back to human in the loop plan->execute cycle which is way more effective.
Thankfully I don’t think we’re at jarvis levels yet.
Blog: pointlessramblings.com Email: nick@<username>.com