• errors handled by truthy if or try syntax
• all 0s and nils are falsey
• #if PORTABLE put(";}") #end
• modifying! methods like "hi".reverse!()
• GC can be paused/disabled
• many more ease of use QoL enhancements
it's placed into a flap that is cut into corneal tissue.
the flap size itself keeps the lens in place; the elasticity of the underlying tissue itself, until it heals into an encapsulation.
the surgery videos of that procedure make me squeamish unlike other surgery videos. Watching an eyeball get deflated/inflated with liquid pressure from the surgeon is just un-nerving to me; not as bad as watching a glaucoma surgery -- but up there.
The place I had it done cuts the flap in one room, then has you walk (suddenly legally blind) to another room for the actual correction. A very interesting experience that cannot be adequately captured on video.
That would be a huge red flag for me. How is that even sterile or safe? What happens if you fall and need hospital care on the walk from one room to the other? Are you now blind until the hospital care is complete?
did anyone manage to cross the chasm between floats and reals doing proofs about algorithms in actual code? It might be a skill issue but I'm always stuck at reals not being decidably comparable
More likely the original version of Claude sometimes refused to cooperate and by putting "you're absolutely right" into the training data they made it more obedient. So this is just a nice artifact
"LLMs won’t magically make you deliver production-ready code"
Either I'm extremely lucky or I was lucky to find the guy who said it must all be test driven and guided by the usual principles of DRY etc. Claude Code works absolutely fantastically nine out of 10 times and when it doesn't we just roll back the three hours of nonsense it did postpone this feature or give it extra guidance.
I'm beginning to suspect robust automated tests may be one of the single strongest indicators for if you're going to have a good time with LLM coding agents or not.
If there's a test suite for the thing to run it's SO much less likely to break other features when it's working. Plus it can read the tests and use them to get a good idea about how everything is supposed to work already.
Telling Claude to write the test first, then execute it and watch it fail, then write the implementation has been giving me really great results.
https://github.com/pannous/goo/
• errors handled by truthy if or try syntax • all 0s and nils are falsey • #if PORTABLE put(";}") #end • modifying! methods like "hi".reverse!() • GC can be paused/disabled • many more ease of use QoL enhancements
reply