Its like a lot of people really want pgrust to fail.

There maybe a chance this was cheating or it may have been a misunderstanding. But now since there is an open source version, why is there still this strong sense of negativity.

Unfortunately my conclusion is that Climate Tech companies in general have been delusional thinking the mission is enough and there is no requirement to be a business.

The reason I am saying this is not to discourage from working in Climate Tech. The reason I say this is to please not go in with eyes closed which is all too common.

Climate Tech needs to grow and be sustainable both for the mission as well as a business. And for far too long I feel business smarts have been missing completely in this sector.

And my issue is always, how do I review so many files. Is the purpose just to go from 1 requirement prompt to so many spec files? How do I know the specs actually reflect the requirement?

I always feel I come away from projects like this even more confused.

It feels so intimidating. There's so much stuff going on. Maybe it is good for agents who can just motor through that volume, but me personally, I would want something simpler, maybe an `OpenClaw-lite`

The same set of things like skills, and custom tools etc can actually be used to get faster to the a product that kind of fits 1000 customers. But the change is that one can build even more custom things for some customers with those skills and tools.

Last year I built a custom integration for a customer in 2 weeks. Now I can probably do it in 2 days. What does that mean for the future, I have no idea, but surely getting custom solutions like this would be more of a moat not less.

Universities use all kinds of hard to setup stuff which are often custom built. Slurm configs, custom configured HPC servers etc. All of this pays off though if you need to do heavy computations which a local machine won't do.

IMO it would be better to make Claude build out something that makes interacting with the HPC much easier. A web UI, Tailscale whatever.

I guess that makes sense since the harness is the product in the case of Cursor.

Instead what I read was typical issues about Agentic CLI's in general dubbed as `alarming`. I would have been happy if the title was just `Annoying` which a lot of `OpenCode` is. But adding the `alarming` made it what it became, something that attracts enough eyeballs to get to the front page of HN.

On another topic, I also feel like quansight blog is usually a high quality resource for Python related stuff. Usually its more for numpy/scipy kind of stuff, but this one is an example of more general Python related stuff.

I don't know where I need to sign up to try it out. What is pricing? Is it API or subscription, what?

I had the exact same experience with Grok 4.5 as well.

I don't really understand what Grok Build is? Is it an API? A CLI? What?

I do think that there should be a protocol such that using these tools becomes more standardized.

For example I know that cmux is trying to support a tmux based setup so it feels like tmux could be most of that protocol.

There are a lot of tools like this popup and I really think making switching easier is the only way I will try a different tool.

But then they introduce bugs leading to lots of complaints. Usually the complaints are about models being dumbed down but almost always the labs say they are doing no such thing.

So I am thinking if we believe the labs then they have a very error prone optimization effort going on.

I keep thinking the most obvious analogue is we need some way to represent documents the same way we can represent structured data in parquet. Parquet allows easy range bases queries and there is so much tooling built around Arrow.

But for documents I keep hitting a wall to figure out what the right abstractions are. Parquet allows filterable metadata. But what such metadata is there for documents. Then there is the arbitrrariness of chunking, vectorization.

If we could just do this in a 2 step process where every document to process can be represented in a parquet like data format then I think we will atleast have the semblance of a solution.

Did they just give up?

The terminal agent threads allow me to run in multiple projects. They always run in a project scoped tmux session so they are always on.

And of course Zed does remote via ssh so the agents can run without me needing to keep my laptop on.

But this is all hypothetical until I get to test it out.