With OPA you can easily create policies that take tens, hundreds or even thousands of millisecond.

That comes at the expense of a lot of power though, so much of the complex logic that you can write in OPA simply isn't achievable in CEL.

A simple EU regulation that requires offering real-time distribution of user data to third parties would massively level the playing field.

I just tested that and got 4 left and 2 right so it works pretty well.

When I received my first (and only) BeMyEyes request I spent the first minute or so figuring out how to work the app and the video delay.

“Let me turn the volume up” “Oh wait it’s on my AirPods” “Could you move it more to the left?” “No your left.” “No; not that far”

I’m quite confident that I was a less than optimal assistant and an AI might’ve well done better than me.

Okasaki fleshes out a couple of examples and explains his thought processes and heuristics for developing such data structures quite well; but they're very much still notes on the early-stage exploration of the concept.

From a historical perspective it's still a fascinating read though and definitely recommend it if you want to read up on the origins of immutable data structures.

That was until I noticed that if I picked up the discussion again the next day he had internalized yesterday's conversation. From then on I worked perfectly fine with him building up shared understanding one point at a time.

I really wish for him, and me, that there was a word he could've used to describe his style of thinking. I'm sure it would save everyone many a frustration.

So... an overflow bug caused the mountain to overflow.

Still one of my favourite real-life bugs of all time.

I think both eventually found their niche and now have plenty of developers that stuck around write appropriate code in it. But when they were shiny and new they indeed both created their fair share of failures.

So why not just start selling battery cargo trailers which can provide your main car with extended range when needed?

It's also much easier to swap and rent out physically, financially and emotionally than your main car.

It's one of the biggest longitudinal qualitative studies on work life and company succes. It has given me by far the most valuable insight into what really matters in building happy and effective workspace.

[1] https://www.goodreads.com/book/show/11721498-the-progress-pr...

That in combination with switching to a Lisp (Clojure) almost made it feasible for me to code with RSI.

I just became a manager instead because I couldn’t work from home and talking like that in the office was a no-go for me.

If that’s your cup of tea you’d be surprised at how happy upper management is to have someone who’s actually good at technology be willing to engage with them.

The book actually explains quite well which negotiation tactics don’t work when faced with life and death situations (hostage negotiation) and goes on to explain which ones do and why they actually work better in everyday negotiations as well.

I still remember my father ‘explaining’ me Pythagoras theorem when I was around 5 to show me how to draw the roof of a house on our hand-soldered Philips Apple II clone.

I’ve been hooked ever since.

The best thing was that 25 years later I opened a Logo emulator again and when faced with having to clean the screen somewhere deep, deep from my muscle memory the right command sprang forward: CLEAR