hsn915

it feels like the kind of interface a devops engineer who hates AI would design

Grok does the same thing.

We'll discuss a feature implementation with various options for design, settle on one of them, and then it will write in the doc comment all the designs we considered but dropped.

This is weird though.

Obviously the best way to use AI to furnish your CV is to build your own project using AI.

Your comment was reductionist

> Where is the reasoning in linear regression?

The comment you are replying to was meant to expose you to your own reductionism.

It's not very hard to engineer software with these two constraints at the same time:

* Must feel very responsive * Network requests can take up to 500ms end to end

How do you predict without reasoning?

If you are going to advocate against something, the alternative you propose needs to be better in some important area, other than "not that thing".

What is the thing you hate about react, and what is the thing you require in an alternative?

I hate bloat and require lightness, so I use Preact.

I also hate complexity and difficult to read stuff, so when I look at the proposal here, I don't see anything appealing, other than "look! it's not react!"

I only read up to the "Petals around the Rose" exercise. I found it pretty easy to deduce (induce?) but the author is right, there's no general algorithmic method to do it .. except for intelligence.

So, the solution is "AI", and even then it's only a "probably".

I've seen many others on Twitter say that.

Grok Build with Grok 4.5 is the best coding AI agent I have ever had the pleasure of using. Stopped using Fable after it.

I think AIs generally "like" the API surface exposed by Shirei. They seem to understand it pretty well and are able to "vibe code" any kind of UI you ask of them using this framework.

To your general point though, yes, there's a lot of uncertainty about what things it makes sense to build in the AI era. I don't have good answers for what would make sense for 10 years down the road, but at this point of time, I think a project like this actually makes perfect sense.

Now that AI can write the code for us, we need better frameworks and libraries, because a lot of what we have now is quite honestly slop.

You could say that you could get AI to maintain 3 separate codebases of the same application UI, each one targeted to a different platform, and the AI will maintain the feature parity and you won't have to worry about it.

For now, AI can take care of coding, but it does not relieve you of having to pay attention to things. If you create 2 or 3 code bases for the different platforms you target, the maintenance burden still falls on you.

But I don't know for how long the situation will remain like this.

Last year I did not think I'd be using AI for coding. I dug up a few tweets I posted last year saying that LLMs have hit a plateau and will stop improving, and that AI coding is a scam being promoted by charlatans.