Winter storms tend to come in cold stretch’s that can cause major freeze havoc.

Ideally, these teams have processes and standards that they use to enable other teams.

If someone says “I have this cool new food product”, regulatory teams say “Amazing, here’s how we can help bring that to market.”

* School at 7am

* Sports practice after school. Game days were basically all night events.

* might take an hour or two break

* 2 to 3 hours of homework

For junior and senior year, I worked 16 hours on the weekends as well.

Instead, I view that team as saying “Customers expect safe food. Our job is to help you deliver on that”.

I’ve come to realize that I don’t actually care what your code looks like. I’m going to need to learn it from scratch every time I use it. It’s going to look weird and foreign to me no matter what. It’s not worth my time nit-picking things that simply do not matter.

ADHD, for example, is correlated with both sleep cycle issues and worse outcomes in life (including higher rates of crime and participation in risky activities).

For me, physical communication is quickly becoming a signal that someone actually put effort into things.

In my view, software development is mostly skimming and pattern recognization. Very little actual, deep reeding in my opinion.

For me, the value of notes is writing down what’s important to me/the participants, including the actual process.

The problem is really how much energy is actually available.

Chronically:

* I my energy levels were dropping. * I had terrible brain fog. * My moods were less stable and I was often very irritable. I felt way less resilient to stress. * My joints were constantly hurting * GI symptoms comparable to IBS

Acutely, I would get flare ups between 2 to 48 hours after eating food that were essentially a mix of flu and allergic reaction symptoms (despite not having allergies to these foods). I felt feverish, dizzy, light-headed, joint pain, head aches, diarrhea, nausea. There were a few times that it knocked me out for 24+ hours.

Three's also this "bucket" theory that I resonate with. Symptoms can fluctuate according to how "full" your bucket is. If you have an empty bucket, you might be able to tolerate whatever triggers with limited reaction. If you have filled bucket and overflow it, your symptoms cascade horrendously.

This part actually made self-diagnosis extremely hard because the same food wouldn't consistently trigger issues. This is on top of triggers already feeling a bit random. Pizza, for example, is wildly hit-or-miss by brand. Despite it all being essentially the same ingredients, some of it, I tolerate incredibly well. Some of it, I flare up terribly. Even more confusing, the cheap/low quality places (like Little Ceasars) sit perfectly fine with me, but many "fresh" or "high quality" ones completely crash me.

AI helped me figure out my symptoms were related to histamine issues. This was really hard to track down. I started to tune into chicken and eggs causing me issues, but (1) I wasn’t actually allergic (2) chicken and rice is a standard safe diet (3) chicken is low histamine itself, but can trigger histamine release . It was further complicated because a bunch of foods didn’t consistently trigger reactions.

It was only after I tracked a bunch of foods and tried a bunch of different remedies that Claude was able to track down the pattern. From there, I was able to understand what foods would trigger my issues.

I don’t think this is about advertising an MCP at all. All of this can be accomplished with plain old HTTP requests. I want to be able to tell users “tell your LLM do go to https://example.com/only-bots”.

There’s absolutely no need for an MCP, because the website will tell the LLM everything it needs to know, including other actions and endpoints available.

Here's our use case: During the sales cycle, the buyer and seller need to exchange a bunch of information then analyze it (which is increasingly agentic). The problem with MCP is the initial setup friction is far greater than users login in themselves and grabbing the information they need. MCPs are great for regular, frequent interactions - but create a lot of problems for these quick one-off sessions.

We'd really love a way to do something like this:

* In Claude: "Grab documents from X, Y, Z"

* Claude hits that website, it returns (1) basic usage information (2) a login link that the user can open in their browser

* User auths in their browser (annoying, but mindless)

* That callback returns a unique, short-lived, one-time token that gets exchanged on all future requests to the site.

Now, we can quickly auth users AND maintain a session state as they do things.

I've been considering a similar approach for the web. Essentially, do a short-lived, one-time use token exchange for every single call back and forth.

* LLM: "I'd like to interact with your site"

* Site: "Great, here's first token. I will exchange it for a new one on the next call. Do not share with with another site. You can authenticate in your browser with this link: [example.com]"

* Then you can go back and forth.

It'd be rather annoying to auth in the browser every time, but it would enable a low-touch flow.

Long term, it'd be ideal to have some sort of out-of-band credential store/tool available, but this would start proving the concept out. Don't use it for highly sensitive stuff, but it would enable a lot of agentic flows that are currently blocked by high-lift MCP setup.

If you don’t control equity, you cannot control the outcome, value, or liquidity of it.