jackschultz

Odd to see this here but I’ll comment! From Milwaukee, live here still, watch >95% of Brewer games all season and this is by far the best team I’ve ever witnessed. Entire year after the 13-13 start while some of the team was recovering from the Venezuela WBC win, we won at an absurd rate. Still had the worry about playoff mini choking, but every part of our lineup from batters and pitchers were all so good.

Best thing for me about this is we were the best regular season team, best in the playoffs, and considered deserving and the clear winner. Doesn’t happen too often and that makes it feel a lot better than just getting hot at the right time.

I just love baseball, love the Brewers, and can’t believe they won.

Friend works for a fairly large law firm on the business running side. She told me how they pay a ton for Harvey and yet, they don't even have a claude for her and those not doing legal work. They think Harvey is great and have no clue that all it does is wrap around models and have safety checks like this repo does. Some of it might be yes, that there's legal work around who gets blamed, but I see mentions of Harvey and it's a joke at what the legal industry does. I see law firms as having no clue on how things work other than paying giant contracts to places that like to schmooze them because that's what they like to do as well.

I can agree with this as well. But I'll do a follow along for who says management has the best and correctly decided plans for the company? What if in the future, engineers become product, and those then become management because who's to say that's more difficult?

For the way orgs are currently set up, yes, conflict between engineers and management can cause issues. I'd put somewhat of a bet that those types of org setups won't be the way in the future.

I’ll claim the ones in the end that will have that responsibility will be engineers. LLMs add the ability for engineered to build quickly enough that there’ll be enough of them to morph into product roles as well. I trust us/them much more than product owners who use models to code.

Much easier to engineers to move to product than product to move to engineers. Or at least the minimum amount needed to fill all product roles. I’m seeing we can do that now and it’s _much_ more efficient to not have to have back and forth communication as in the past with that communication being by far the slowest part of build processes.

Thank you, and one in the above comment, for sharing this. I feel comments like these need to be seen more frequently by people not in your situation. Hard claim I can even imagine what it feels like.

I built a tool similar to this end of last year with the idea of making it easier for agents (and humans) to work with postgres and do things like getting summaries when they want to. But then, I realized that these models are trained and really know how to use all parts pg and it was easier to let them do that. There can be cases for this, but the cost in extra tokens and steps using pg vs a tool are so little, it wasn't worth it to keep going.

> We expect demand for Fable 5 to be very high, and difficult to predict. On the Claude API and consumption-based Enterprise plans, Fable 5 is fully available from today. For subscription plans, we’d rather give access sooner than later, so we’re rolling out more conservatively, in stages:

> - From today through June 22, Fable 5 is included on Pro, Max, Team, and seat-based Enterprise plans at no extra cost. > - On June 23, we’ll remove Fable 5 from those plans. Using it after that will require usage credits. If capacity allows, we’ll extend the included window. > - After this point—when sufficient capacity allows us to do so—we aim to restore Fable 5 as a standard part of subscription plans. We intend to do this as quickly as we can.

I really wonder what their compute layout is for this. My guess from my understanding is that they know how to restrict during peak times and are willing to do this. Meaning we expect not the most fast responses and they can delay the inference to not have the service be down. Then, if that delay time is too annoying for token payers, they're saying they should be allowed to remove cost by taking away the subscription users.

Be Here Now network, which started with Ram Dass, still does mostly weekly videos from Goldstein and Kornfield. Search for their names where you listen to your podcasts. Incredibly good to listen to.

Other ones I listen to are in the Thai Forrest Tradition, started from Ajahn Chah and now talks from Abhayagiri, Amaravati. Other one from Mahayana, which has so many talks and probably the best book I've read, Seeing That Frees, is Rob Burbea. He died from cancer in 2020, which is incredibly sad given how young he still was and much he's produced for us.

All of these people give different angles on the teachings of the Buddha. I highly suggest listening and reading from these people and the differing traditions all talking for similar goals of how to look at the world for the acknowledgement of dukkha (pain / suffering) and how to deal with it. You don't need to sit and meditate either to get the benefits.

Very much agree. Gave a presentation on AI to a group earlier this week and I spent a third of the time talking about the Opus 4.5 inflection point in AI history. First time using that model the day it was released it was so clear that it knew what it was doing at a different level. People still jump around to different models or tools or time frames when talking about AI and usefulness, but those have no meaning if they’re not using the Opus 4.5 and 4.6 models and anthropic harnesses of Claude code or cowork.

I’m interested in the studies along with the history of AI and if they’re going to realize that was the point when things changed, because for us devs, that was the moment.

I literally did this yesterday and had the same thought. Older computer (8 gigs ram) with crappy windows I never used and I thought huh, I wonder how good these models can take me through installing linux with goal of docker deploys of relatively basic things like cron tasks, personal postgres, and minio that I can used for self shared data.

Took a couple hours with some things I ran across, but the model had me go through the setup for debian, how to go through the setup gui, what to check to make it server only, then it took me through commands to run so it wouldn't stop when I closed the laptop, helped with tailscale, getting the ssh keys all setup. Heck it even suggested doing daily dumps of the database and saving to minio and then removing after that. Also knows about the limitations of 8 gigs of ram and how to make sure docker settings for the difference self services I want to build don't cause issues.

Give me a month and true strong intention and ability to google and read posts and find the answer on my own and I still don't think I would have gotten to this point with the amount of trust I have in the setup.

I very much agree with this topic about self hosting coming alive because these models can walk you through everything. Self building and self hosting can really come alive. And in the future when open models are that much better and hardware costs come down (maybe, just guessing of course) we'll be able to also host our own agents on these machines we have setup already. All being able to do it ourselves.

Reread Story of Your Life again just now, and all it made me want to do is learn Heptapod B and their senagram style of written communication.

Reading “Mathematica - A secret world of intuition and curiosity” as well and a part stuck out in a section called The Language Trap. Example author gives is about for a recipe for making banana bread, that if you’re familiar with bananas, it’s obvious that you need to peel them before mashing. Bit of you haven’t seen a banana, you’d have no clue what to do. Does a recipe say peel a banana or should that be ignored? Questions like these are clear coming up more with AI and context, but it’s the same for humans. He ends that section saying most people prefer a video for cooking rather than a recipe.

Other quote from him:

“The language trap is the belief that naming things is enough to make them exist, and we can dispense with the effort of really imagining them.”