The solution here might be the appeals court, since there is a deed restriction. The city agreed to it when they paid $10 for the land. The article mentions that Texas courts tend to be pretty serious about enforcing deed restrictions.
Was there ever a deed restriction? The government says no, but they say there was something else which I don’t understand.
> In the notes about the grantee, the cash warranty deed states that the property was to be held in trust for future use as parkland by Williamson County, Texas. This was not a deed restriction.
Encumbrances and easements tend to follow the land even if they aren’t explicitly mentioned in the deed in question from the most recent transaction. They must be explicitly struck. Source: land attorney when asked this question about a deed restriction from a past deed. It was about NH real estate law, but I was told this was a general principle. It’s part of the reason title searches are done. The effective deed is a fold over the sequence of deeds.
I went through the deeds the other night. The first transfer from Bland to Texas Parks and Rec Foundation had a restriction to be held in trust for a city park (or for parkland or something). The transfer from tp&r to williamson county park foundation only said to be held in trust. The transfer from the park foundation to the city didn't mention it.
I don't know enough about texas real estate law to know if the restriction would tend to follow or not. I also don't know if the city would have done title research to have seen the restriction, so they may not have knowingly violated it (which may or may not matter; and maybe they should have known).
Also, fwiw, the 'one month later' sale reported in the article was more like a few months later, in case you date restrict deed searches.
AFAIU, the people suing have no privity; they're just a neighbor and don't have any right to enforce the covenant. (If the covenant had granted them an interest, they could have.) Presumably the original property owner who granted the land, or their successors in interest, could sue to enforce the covenant, but they haven't.
It's fine as long as t-bill rates match or exceed inflation. Then you can avoid losing purchasing power by just putting your money in the world's safest investment. Over the past century, t-bill returns have slightly exceeded inflation on average, though there have been periods when they didn't.
Stash paper cash in your safe and sure, you lose purchasing power. Use fiat money the way it's designed to be used, instead of using it like gold coins, and it works better.
Us debt as a fraction of GDP has doubled this century and roughly quadrupled in my lifetime. It would seem to me that eventually t-bills will not be safe.
Among modern EVs, the Aptera will probably be closest. I don't think they're opening the software but they're going all out on right-to-repair for the hardware.
Steve Yegge wrote about this in his book Vibe Coding. He says it takes about a year of experience before you're consistently getting good results. He writes about lots of different techniques for doing that, but also says a lot of it comes down to just getting a feel for when the LLM is going to go haywire.
> but also says a lot of it comes down to just getting a feel for when the LLM is going to go haywire
That has been my experience too. The days when I'm very focused, being extra deliberate and constantly questioning/examining/challenging things, the results are much better. Autopilot days just go through in a daze and the outcome is objectively worse. This has made me much more hands-on and pushed me towards models which are actually not that "clever" like codex at effort=low but fast. Given that I'm doing the meat of the thinking, might as well not be slowed down by the model and lose the flow.
+1 to all of this. The challenge can be staying focused and thinking when the AI assistant is (1) moving very fast and (2) often times doing multiple things at the same time.
I know I have struggled to keep up, and fall into the trap of approving things (either commands or recommendations) without taking the time to really process and think about them.
It's a bit like the age old problem of "it's super easy to ask questions, and can be super hard to answer many of them". So the economy of the conversation gets out of whack fast.
It's been 4 years of using them for me, before writing a book I'd wait to have a decade of experience to share with others, otherwise it would have the same value as a book on a react tutorial
I'd say closer to 6 months for me but probably still some room to improve.
I think getting a decent setup with a fast feedback loop for the agent combined with context (in repo markdown)+memories goes a long way.
After having Claude Code "remember" my preferences and tools, it's more efficient.
It has a tendency to copy existing patterns so a good AGENTS.md with best practices and architectural goals goes a long way to prevent it from duplicating patterns you're trying to get rid of.
Plenty of interesting sci-fi later, though. Gattaca, Ex Machina, Her, Interstellar, Inception, The Matrix, Contact, Arrival, Eternal Sunshine of the Spotless Mind...
reply