It’s such a shame that media (social and traditional) really plays up loss aversion. My local news is basically fear mongering. My local social media page is filled with people who have nothing better to do with their time than complain about all of the negative stuff happening in this town. They take every isolated incident and project it as some major pattern. It’s really sad.

It worked.

Unless negligence is involve (like an arborist being hired to condemn a tree), they’re generally considered and act of god. They’re the responsibility of the property they fall onto.

So, in the case of OP, the situation is unfortunate, but it’s on him to maintain his properties and his fence lines within his properties. It’s convenient the state has a fence along part of his property, but it’s not their responsibility to fix it for adjacent lots.

This positions them to compete directly against those

GitHub or Tuicr for code review. Still waiting for an agentic first review environment- which Jetbrains has missed the ball on.

For me, the things that made Jebteains great just don’t matter anymore.

The security problem is two fold: (1) companies want control over where their data goes. Figma allowing any MCP creates problems (2) open redirects can create phishing issues. If your using Pi, you’re probably thinking of this. Most users aren’t.

For us, we decided to do an allowlist pattern because it was a reasonable tradeoff. The solution is allowing per-tenant client configuration, but that comes with its own set of issues (dev time, support, maintenance, etc). When nearly all of the money is flowing through a handful of well-known MCPs there’s little reason to out effort into supporting every MCP.

I ended up building out tool an MCP server that I use as a bit of a psuedo harness for Claude. I have a variety of multi-step workflows that are basically micro-skills stacked on top of each other. This helps me make sure that I can get Claude to think in a repeatable and reliable manner.

For coding, I've found that I have a few specific steps that Claude needs to do before I'm comfortable letting it loose:

* It must extensively explore the code base (including certain areas that it misses)

* It must think about what it doesn't know or is making assumptions about

* It MUST scaffold out it's intentions. Essentially, it can write comments, classes, and method stubs - but no actual content. Very much like a spec, but since it's in and alongside other code, it's much easier to identify problems.

* It must spike and validate key assumptions. This, plus the prior step, are the only way I've figured out how to avoid it ending up in a confusion loop. Too often it looks at poor-quality code it's written and thinks it's a long-term solution. By avoiding writing code as much as possible, it knows that it's draft content.

* Only, then can I review it and send it it.

Said MCP server (missing the actual ops): https://github.com/clops-mcp/clops-mcp

I’ve always wanted it to be better, but it’s just terrible. It’s like working on a projector screen where the pixels never line up.

I have Xreal airs. And, while, I like them, they’re rather useless because 1080p just isn’t enough.

Don’t get me wrong, my “fun” car (an old, beat up Jeep) is going on 2 years with the same oil (I barely drive it), but I known I need to change it soon.

Oil degrade with oxygen. Every time you drive that car, the oil are being re-oxygenated and continuing to degrade (along with being exposed to combustion byproducts).

Also, the type of wear you get often isn’t noticeable until it becomes catastrophic. In my case, a 30 year old car that’s already on its last legs “catastrophic” is more like “time to finally drag it to the scrap yard”.

The other components just aren't as sensitive or exposed to as much abuse. Often, really only needing replacement if they’ve leaked out.

You don't want to be the reason your kids team lost. You don't want your kid getting kicked of their team for your behavior.

* All of the parents already know who the abusive parent is

* The first warning was the coach talking to the "entire group" (at a natural stopping point). The group dialed it back (there will always be some controversial calls), but that one parent didn't get the message.

* Finally, the game stopped suddenly (ball was in play, but in a neutral position) and they we're directly addressed by the ref.

This caught the abusers attention. This was an abnormal event. They were being addressed directly. Whether they realized they were the problem, they certainly recognized the social pressure. They recognized how embarrassing it was (sadly, they probably didn't realize how embarrassing it was for their kid) and decided to take the ref's suggestion to cool down.