- Take the most recent sale prices of all neighboring parcels within a quarter mile

- Take the land-area weighted average price per square foot

- Assess the given property as its land area times that average

Practically, this can be assessed without ever visiting any of the properties, and there are no games for either the assessors or the owners to play to manipulate it. Each neighbor serves as an example of the potential use (and therefore value) of local parcels. Yes, your hole-in-the-ground gets taxed the same as a skyscraper of the same size. Have you considered building something useful on it?

(Yes, as usual, parks, churches, and other non-economically-extractive community amenities would be exempt from _paying_ the tax, but that doesn't change the assessment)

Of course, him mentioning "Don't do this" suggests that lead water pipes into the home were common enough to need a warning against.

You can have a policy of waiting for overwhelming proof of harm before banning anything. But there are an awful lot of chemicals added to our food and environment, with precious few studies competently and honestly tracking their effects. I want a much more careful policy - don’t put unknown chemicals in my body without convincing me the benefit.

How can we draw apps into using a common data backend owned by the user?

It does mix up Crystal and Ruby, but the compiler catches it.

LLMs were fantastic for writing a project[0] in a new, niche language[1]. They help write any missing libraries. They help iterate when I get stuck on language aspects. They explain concepts as well as the median SO post, and much better than the posts that don't exist.

[0] https://github.com/TedSinger/chatfile/

[1] https://crystal-lang.org/ - quite pleasant

  #@
  hi

This turns out to be quite convenient! Text feels smoother in my editor than a webpage, and I can run it from a shortcut. I can prune history and retry as I like. Shell commands give the model exactly the context I choose.

I know there are other people like me on HN who demand close control over their tools. To broaden the audience, I've extended `chatfile` to use multiple model providers and sanded off some of the rough edges. I hope you find it useful!

Comments URL: https://news.ycombinator.com/item?id=44101002

Points: 1

# Comments: 0

Errors in the initial design should be assumed as the default. Wise software engineering should make change easy.

Constraints on natural keys are business logic, not laws of mathematical truth. They are subject to change and often violated in the real world. The database as record-keeping engine should only enforce constraints on artificial keys that maintain its integrity for tracking record identity, history, and references.

Your database may not be primarily a record-keeping engine, and your tradeoffs may be different.

Agreed that this author and the industry as a whole go too far in the direction of finance for finance's sake.

I guess it depends on the cows

- Plutarch

Structure recognition should be pushed as far down in the subconscious as possible. Rainbow parens help, but it’s not nearly enough to stop other expression fragments from jumping into attention. Likewise clojure’s different bracket types for data structures, likewise the editor highlighting the paren matching the one at the cursor. Better than nothing, but incomparably worse than just having visually distinct syntax in the first place.

C-style is fine. Python-style, ML-style, SQL-style, BASIC, shell: all fine for structure recognition. But lisp is just a soup. Or a fog.

Same problem with elasticsearch queries, too.

Followed by another company introducing their "Plus Ultra" model.

Took me a lot of searches to find something meeting my requirements

All feedback/control systems are like that.