This is moving in the direction towards a final interface, very good.
There aren't enough digital french cleat systems.
The true benefit of a French cleat isn't storage or organizing the way a fiddly pegboard and hanger approach uses, it's the ability to move all tools for a specific project onto a single rail without having to fiddle around, reducing friction for engaging and re-engaging with a project.
owl_might_ · 2026-10-25 19:39:50 UTC
Just out of curiosity, what is a French cleat? I've only found references to building (real) shelves on Google.
Jtsummers · 2026-10-25 19:44:23 UTC
That's what it is, it's basically two boards with angled cuts to match. One mounted to the wall, the other to the thing you want to hang from the wall. No fasteners needed other than for those two attachments (or more if you use more boards). Gives you some flexibility in arranging things in a shop (or, that's my reason for using it with our 2-car garage).
owl_might_ · 2026-10-25 21:25:27 UTC
I misunderstood the original message, seem's like my English isn't that good. Thanks for taking the time to explain!
zahrevsky · 2026-10-25 19:34:21 UTC
> We built a rich interface around the pi coding agent
I'd have to be _strongly_ convinced to leave oh-my-pi and Paseo.
InsideOutSanta · 2026-10-25 20:15:17 UTC
Yeah, now that agents are doing most of the work, and we want to give them as much freedom as possible to run code, take screenshots, click on things, etc, it really doesn't make much sense to have a setup where all of this happens on your local computer. IMO it makes more sense to have this hosted somewhere, and then have UIs that make this visible to you on your devices.
aliasxneo · 2026-10-25 20:28:19 UTC
Exactly. They sit in their little world in my homelab and I control everything through networking and virtualization restrictions. They run on a beefy VM, can spawn their own VMs (Ubuntu, Debian, Fedora, Arch, Windows, even macOS on an old mac mini), run their own browsers, access their own secrets, etc. There's no way I would go back to agentic development on my local machine anymore.
cromka · 2026-10-25 22:39:30 UTC
Any good writeup on how to set this up? Not that it's a rocket science, but would be good to have a bootstrap how to with good practices and a general showcase.
aliasxneo · 2026-10-25 22:48:51 UTC
Not that I can find. I'm a Senior SRE so it's more or less an extension of my domain. The hardest part is really just knowing the "best" way to do something which generally just comes from experience. But most frontier agents can probably get you close enough without too much experience.
simpaticoder · 2026-10-25 20:29:58 UTC
This sounds like a short-term strategy at best
You only need an agent to click things long enough to build an API on top of the thing it's clicking on. And running a full windowed virtual machine is expensive!
I'd also caution against saying things like llms are doing most of the work I don't think that's true. And where it is true it shouldn't be. These things are still new tech and they need a lot of hand holding and oversight still.
InsideOutSanta · 2026-10-26 13:02:48 UTC
> You only need an agent to click things long enough to build an API on top of the thing it's clicking on
To be clear, it clicks things to do things like test software. If you build an API, you're not testing if the clicking actually works.
mcrowder65 · 2026-10-25 20:26:53 UTC
Paseo!! :goat:
dr_kiszonka · 2026-10-25 20:33:45 UTC
I am curious about Pi, but my experience with a seemingly more fully-featured Hermes has been endless tinkering and fixing minor issues. Have your experience been at all similar?
aliasxneo · 2026-10-25 20:51:37 UTC
I've been using it without thinking much about it for 3 months now. Have yet to run into any bugs or strange behaviors. But bear in mind I'm using oh-my-pi, not Pi. I found the latter to be mostly useless in terms of what I needed for my day to day work. I'm sure I could tinker with it to get it right, but that's literally what oh-my-pi is doing for you. And like I said, zero problems thus far.
cromka · 2026-10-25 21:09:27 UTC
Do you use Paseo as a layer over oh-my-pi or alongside?
VMG · 2026-10-25 19:42:27 UTC
It feels like the day after I got comfortable with jj everybody become obsessed with git worktrees
mpalmer · 2026-10-25 19:43:30 UTC
The latest version of jj supports colocated git worktrees as part of its workspaces feature.
phildenhoff · 2026-10-25 19:53:43 UTC
Finally!! Can’t wait for git lfs support to land, and I can move back to mostly using jj
nicce · 2026-10-25 20:16:55 UTC
What are the benefits of jj if in the end everything is still on git backend?
sunshowers · 2026-10-25 20:46:02 UTC
It is more powerful and easier to use, for both humans and agents.
yoz-y · 2026-10-25 21:07:49 UTC
To me the main difference is that there is no staging (so no stashing needed), and conflicts are first class citizens. In practice this means that you can usually halt your work halfway, switch a commit, rebase everything onto head and continue working even if one of the branches off your commit has conflicts. In git you would have to resolve those before the rebase can finish.
Since conflict resolution these days mostly boils down to “hey LLM, resolve conflicts” this is much nicer.
Also jj tracks every change to the repo so undo works much better and is more readable than reflog
saghm · 2026-10-25 21:32:48 UTC
My favorite feature is the built-in distinction between what's mutable and what's immutable in my history. I can freely modify any commits I make locally without issue, since no one else would be able to depend on them, but if I push something or fetch it from a coworker, I have the safety of not needing to be careful when doing the equivalent of an amend or rebase because it will fail with an error telling me to use a flag to bypass the immutability protection if that's what I actually want.
Not having to stage changes in lieu of them automatically getting picked up was a bit of a learning curve for me, but now that I've gotten used to it I like it a lot better and I don't think I could go back. The equivalent of the reflog pretty much always has my changes in it if I accidentally lose them without manually saving due to the snapshotting, and I have no need for a stash because commits and branches are essentially just recording a checkpoint rather than being things that feel "heavyweight".
As an added bonus, dealing with conflicts is a lot less annoying because each commit records its conflicts separately, so fixing them doesn't require doing a stateful pipeline of changes in a big rebase; I can just do them piecemeal, in any order I want, and even just check out other stuff and work on them before coming back later if I feel like it.
I was "that guy" who would sometimes have coworkers come for help with git problems (https://xkcd.com/1597/ alt text). I've forgotten most of that knowledge (and all of that muscle memory) and didn't have to learn nearly as much to replace it with the ability to do a lot more with a lot fewer mistakes.
IshKebab · 2026-10-25 20:26:21 UTC
Are they just going to copy LFS? That's a real shame. I had some hope they would do something that isn't as shit. Oh well.
I guess they'll just copy submodules too. Kind of feels like there's little point using it if it's just going to copy Git's mistakes.
saghm · 2026-10-25 21:26:33 UTC
I didn't even realize those were recent! The first time I tried to look for how to use worktrees in jj, they were already available
It's a wrapper around git, compatible with git repos but supposedly easier to use
sunshowers · 2026-10-25 20:45:26 UTC
No, jj is not a wrapper around git. It is a source control system of its own that has git as one of at least two production backends. This distinction matters because git wrappers don't tend to have fundamental concepts of their own like the operation and evolution logs.
shepherdjerred · 2026-10-26 00:23:13 UTC
jj is in practice a wrapper around Git
it is built, though, that the Git backend can be swapped for another backend.
I'm not sure where you're getting two production backends from. I guess you're referring to the Google internal one that nobody can use?
> There is currently only one production-ready builtin commit backend: the Git backend. <omitted> Google also has its own cloud-based backend.
No, git-branchless is a wrapper around Git. jj is an independent source control system with git compatibility. jj can, and does, function entirely without git.
> I'm not sure where you're getting two production backends from. I guess you're referring to the Google internal one that nobody can use?
Lots of people within Google use it!
shepherdjerred · 2026-10-26 03:43:03 UTC
Yes, if you are lucky enough to work at Google you don't need Git to use jj. Most people do not work at Google.
If you work at Google, jj can and does function without Git.
If you do not work at Google, jj is a Git wrapper.
shepherdjerred · 2026-10-26 00:21:17 UTC
I started using jj right when agents became viable. If I were still actually writing code rather than directing agents I would use it day-to-day
I don't think harness like Claude Code or Codex support jj very well for working in parallel
troupo · 2026-10-25 19:44:03 UTC
It's interesting to see that the README is much less CLAUDE-y than the abomination that currently runs at https://thinkrail.ai/
How is this llm-vomit "specs that are ground truth" etc.?
woadwarrior01 · 2026-10-25 19:49:49 UTC
The README has plenty of Claude-isms too.
hsuduebc2 · 2026-10-25 19:46:09 UTC
This is a great step. JetBrains integration of AI agents inside their ides is horrendously clunky.
tclancy · 2026-10-25 19:59:39 UTC
I have multiple CLAUDE.md instructions about why using the terminal in JetBrains will burn the agent badly.
WesleyJohnson · 2026-10-25 20:13:55 UTC
Can you expand on this? I genuinely don't know and I use claude code in a terminal in PyCharm daily.
tclancy · 2026-10-25 22:34:59 UTC
It's probably sorted, but for a while there was an escaping issue. Then our company forced us to use Claude via CoPilot in PyCharm and that may have been the other issue. I just stick to a command prompt in a shell now unless there's a pressing advantage to doing it in any IDE.
yoyohello13 · 2026-10-25 19:54:43 UTC
Looks interesting, but they need to clean up the claudese in those bullet points holy crap. It's like they purposely want the "what you get" section to be as obtuse as possible.
collimarco · 2026-10-25 19:58:55 UTC
Running agents outside containers seems crazy to me... It should at least launch a sperate microVM or container for each agent / task.
oDot · 2026-10-25 20:00:35 UTC
I do not get the appeal of web-based GUIs now that we have LLMs.
Migrating my screenwriting software[0] from OpenTUI to Roc thought me what were once rough edges that take a lot of time are now just a prompt away from a solution.
It now uses 10x less RAM, bundle is half the size, and my initial implementation is 700-800 fps for scrolling and 200 fps for writing.
Granted, a TUI is less complex than a full-blown GUI, but I built a Roc Iced platform just as easily that abstracted Iced flux away
for people who still code. why do you need them not to?
oDot · 2026-10-25 20:18:19 UTC
I do code -- the app logic. I also am well aware of what the infrastructure code does, I just don't type any of it myself.
Even if I wanted not to code it I couldn't. LLMs are still incapable of creating code up to any decent standard.
Also, while I do the get the joy of programming, we sometimes forget to focus on the user. You being happy to have typed the whole thing once, and have it run everywhere via the magic of browsers may not be the best strategy if this means your user's lap will be overheating.
In the end as much as I like coding I would prefer my users' experience to be the best it can be. LLM assisted code delivers this better and faster than hand-typing it all (which in turn is better than completely vibecoding it)
14u2c · 2026-10-25 20:39:39 UTC
Jetbrains software is not web-based.
reisse · 2026-10-26 00:05:20 UTC
Eh, have you checked the repo? Thinkrail is Typescript + Bun + Electrobun, and UI is written in React, which is pretty much web stack.
14u2c · 2026-10-26 00:53:26 UTC
I should have done so, that’s unfortunate. Doesn’t bode well for their Java stack.
gjvc · 2026-10-26 00:37:10 UTC
teamcity, youtrack, ...
Aurornis · 2026-10-25 20:51:54 UTC
JetBrains UIs aren't web-based, unless this is an exception.
JetBrains tools are heavier and can take a few seconds to launch, but they also have some of the most responsive typing out there. They did some good work on zero-latency typing modes when that was a big topic and they were very good at typing latency relative to most editors.
They will never be the right tool for the personality type that gets angry when their IDE takes a few seconds to launch at the beginning of the day or when an application takes more than 1GB of RAM, but I am not that type of person so I enjoy them.
I think the TUI people are well served by vim or emacs and should just stay there and be happy.
The rest of your post feels like an injected ad for your project underneath a topic where it's not relevant
oDot · 2026-10-25 21:04:29 UTC
This post is about a TypeScript repo, which is what I commented on. It may as well be a necessity since Pi is using a JS runtime as well. It has nothing to do with JetBrains and everything to do with the codebase in the link.
It also has nothing to do with TUI vs. GUI, since my comment addressed both (anecdotally).
If anything, your mentioning of their performance work is exactly my point.
rfgplk · 2026-10-25 20:06:37 UTC
> TypeScript followed by a myriad other (objectively) slow languages
JetBrains, explain concisely why this isn't written in C/C++/Rust?
yoyohello13 · 2026-10-25 20:10:16 UTC
Very likely because Pi is written in TypeScript and Pi plugins are expected to be TS. TS is becoming the one true language. Best get used to it.
troupo · 2026-10-25 20:38:56 UTC
Because it's just slapping web-based Monaco editor on top of pi which is written in Typescript.
exizt88 · 2026-10-25 20:13:08 UTC
I refuse to take a repo with an AI-generated readme seriously. If you haven't bothered to write a readme, what else have you not bothered to do?
(100% AI according to Pangram btw)
asteroidburger · 2026-10-25 20:28:15 UTC
Why does AI-generated imply "not bothered" to you? If I take all of my design docs/specs, all of the existing repo, and I tell an agent that I'd like to make a readme that contains things X, Y, and Z, what's the problem?
Rejecting slop doesn't imply rejecting all AI-generated text wholesale.
FridgeSeal · 2026-10-25 20:34:32 UTC
The problem is that it’s market or care and respect. If you can’t even be bothered to while a simple readme communication your intentions, what else can’t you be bothered doing properly?
It’s a marker that the project is likely to be low-effort slop, which may or may not just be abandoned at the deep of a hat.
troupo · 2026-10-25 20:35:02 UTC
Because AI-generated README means that the person doesn't care about the audience. It means that the author never read the README themselves to see that the "load-bearing ground truths" actually reflect what the project is about, and not some hallucinated bullshit.
There's a famous Jobs story in which he insisted that even the insides of the computers be made beautiful. Because that shows care. Now people are arguing that even the outsides can be as ugly as they want, who cares.
ChrisClark · 2026-10-25 20:40:43 UTC
What if they read it and concluded it was correct?
JumpCrisscross · 2026-10-25 20:49:47 UTC
> What if they read it and concluded it was correct?
Then I’ll probably hear about it again from someone I trust. I don’t need to be the first in my circle to test if this one is different.
matkoniecz · 2026-10-25 20:54:56 UTC
If they read it and were fine with blatant llmese, then I do not trust their review abilities at all.
davidbanham · 2026-10-26 02:46:10 UTC
It may be correct, but was it good? If it's obvious that someone has plopped some slop in that file and then said "Yeah that'll do, ship it", then that gives the reader information about how much the author cared about the project. If someone's first touchpoint to your project is a billboard that yells "I DIDN'T REALLY GIVE A TOSS ABOUT THIS" then don't be shocked if they don't engage.
JumpCrisscross · 2026-10-25 20:47:51 UTC
> what's the problem?
I can do it. Anyone can do it. Probably better for my/their own needs than someone else’s agent can.
The README is meant to communicate substance and intent. Without the latter it’s an overly-verbose landing page.
TiredOfLife · 2026-10-26 04:35:34 UTC
I can see. Anyone can see.
sigotirandolas · 2026-10-25 20:50:09 UTC
> Why does AI-generated imply "not bothered" to you?
1. AI generated text is just hard to read and verbose, if you worked so hard on your docs/specs, why would you want your README to be unreadable?
2. There's so much garbage written with AI that I'm just going to assume yours also is. Would you sign up to a gym with broken windows? It could be the best gym ever, but I wouldn't count on it.
bdangubic · 2026-10-26 02:13:23 UTC
there is a lot more garbage written by humans, you assume the same for humans?
phoghed · 2026-10-26 03:39:06 UTC
> hard
Skill issue, it’s easy for a guy like me
matkoniecz · 2026-10-25 21:13:18 UTC
> Why does AI-generated imply "not bothered" to you?
If it is blatant unfixed llmese, then it means that no effort whatsoever was put into making this text.
davidbanham · 2026-10-25 21:14:12 UTC
If it wasn’t important enough for someone to take the time to write, it isn’t important enough for me to take the time to read.
hoppp · 2026-10-26 01:04:53 UTC
This is true.
I think generated code really shines as internal tooling and not something shared.
user43928 · 2026-10-25 22:20:55 UTC
We all know AI does not write well today.
What JetBrains needs is nothing short of a revolutionary product, which they would need to sell with an excellent introduction.
Instead they phoned it in and pasted that slop:
> Once a GitHub PR is open it shows the CI checks and review decision, and lets you mark it ready, hand failing checks or a diverged branch to the agent, merge it with the repository's last-used method, reopen it, or delete the remote branch.
vconnor · 2026-10-25 23:08:52 UTC
Why does AI-generated imply "not bothered" to you? If I am not bothered to write the content, so I ask the agent to do it for me, what’s the problem?
davidbanham · 2026-10-26 02:42:58 UTC
The fact that you didn't feel it was worth your time to make sure it was excellent is a strong signal that I shouldn't bother to read it.
MiroslavPokorny · 2026-10-26 08:38:37 UTC
Whats my favourite ice cream ?
The answer is very short.
But given you dont know me, im going to guess you wont be foolish enough to try and guess especially considering there are at least 100 different flavours.
Software is even more complicated. How is any person even the smartest software type in the world or AI going to know all the exact details of your wish if nobody tells them exactly every painful detail ?
smallnix · 2026-10-25 22:16:04 UTC
But why read it? Just point your agent at it and use your personalized project exploration skill.
quasarj · 2026-10-25 22:28:15 UTC
Not sure why it matters? I can't tell the difference, personally, but even if I could the AI is much more likely to have given complete and accurate information than any human..
vconnor · 2026-10-25 23:04:59 UTC
Do we have to
explain in every bloody thread why human-generated Readmes, with their faults and omissions, are preferable to overly verbose and flowery AI slop prose?
Conciseness and highlighting relevant points is much more important than word count. Machine generated readmes are anything but. Sorry you can’t tell the difference between that and human prose, you should try reading more human content.
hoppp · 2026-10-26 01:04:06 UTC
It really depends on the human input. Prompt the LLM to give a short but dense explanation.
rgoulter · 2026-10-26 01:15:45 UTC
> overly verbose and flowery AI slop prose
This is a useful criticism.
Left to themselves, LLMs prefer writing that's really atrocious. e.g. The writing will try and make everything sound profound.
The other problem I've noticed is e.g. LLMs will write in stuff that's inappropriate for the content of the text. e.g. Writing out stuff that looks like a chat reply, in commentary or descriptions or whatever.
I'd distinguish, though, between "sloppy writing" & "LLM generated writing". I'd agree if you didn't put in the effort to check the writing is of high quality, then perhaps the other parts are also not high quality.
I don't think just because "AI" wrote it it's bad. I wouldn't prefer e.g. sloppy human writing over well-crafted LLM-written text.
This readme the main thing which sticks out is the "what you get" bullet points are rather dense/verbose for bullet points. But aside from that it seems fine.
alexjameson · 2026-10-26 12:23:06 UTC
I'm a technical writer and I use agents a lot for my work and personal projects. I also created a basic open-source preset for agents to create end-user documentation.
During the preset testing, I created dozens of READMEs using agents. Although I can't say that any of them were perfect for me, most of them were good enough.
README is a very special kind of document. For small projects, it's often the only one that potential users will read. The README should explain what the product is, what problems it solves, how to get started, provide some examples, and explain the restrictions. It should cover all these topics in a concise way so that even readers who aren't used to read long texts can easily read through it. It's definitely up to human to make it clear and easy to understand.
pjmlp · 2026-10-26 08:11:31 UTC
Yes, because apparently accepting the vibe generated junk code is alright, only the Readmes seems to be a problem.
tasuki · 2026-10-25 22:28:45 UTC
> I refuse to take a repo with an AI-generated readme seriously. If you haven't bothered to write a readme, what else have you not bothered to do?
I care whether the readme is any good, not who wrote it. If you haven't bothered to critique the readme and instead critique its suspected creator — something entirely in your head — what else have you not bothered to do?
> (100% AI according to Pangram btw)
So what? Who cares about Pangram? I certainly don't! You cannot detect AI — it's impossible. Perhaps it's just Kenyans?[0]
> I refuse to take a repo with an AI-generated readme seriously.
Well, good luck in professional development then. Love it or hate it, this is the way everything is moving.
sergiotapia · 2026-10-25 22:42:17 UTC
there's no need to announce this. might as well announce you don't eat meat, or you don't like electricity.
maxdo · 2026-10-26 00:44:00 UTC
majority of people here, have to read ai for work. that's why you're getting paid nowadays, read, understand, steer and fix errors produced by ai. this is an ai product. It's a bit weird why readme of ai product has to be written by human?
GuB-42 · 2026-10-26 00:54:35 UTC
It is an "agentic IDE", a tool intended for people who don't bother writing a readme.
If you care about these things you are either not the intended target or you are a hypocrite.
chenzhekl · 2026-10-26 00:58:23 UTC
The README looks clear to me. What do you think went wrong?
stingraycharles · 2026-10-26 01:02:04 UTC
I'm more worried about all PRs being reviewed and accepted by AI as well.
hoppp · 2026-10-26 01:02:33 UTC
I am fine with AI readme as long as it has what I need.
whatthejesus · 2026-10-26 01:41:59 UTC
If anything spend your time on the code and let AI make the readme. If you’re basing the code quality on the readme maybe look at the architecture is a better way to judge a project. Seems a bit superficial like judging a book by its cover…
Comments
There aren't enough digital french cleat systems.
The true benefit of a French cleat isn't storage or organizing the way a fiddly pegboard and hanger approach uses, it's the ability to move all tools for a specific project onto a single rail without having to fiddle around, reducing friction for engaging and re-engaging with a project.
This is exactly what I was missing
I'd also caution against saying things like llms are doing most of the work I don't think that's true. And where it is true it shouldn't be. These things are still new tech and they need a lot of hand holding and oversight still.
To be clear, it clicks things to do things like test software. If you build an API, you're not testing if the clicking actually works.
Since conflict resolution these days mostly boils down to “hey LLM, resolve conflicts” this is much nicer.
Also jj tracks every change to the repo so undo works much better and is more readable than reflog
Not having to stage changes in lieu of them automatically getting picked up was a bit of a learning curve for me, but now that I've gotten used to it I like it a lot better and I don't think I could go back. The equivalent of the reflog pretty much always has my changes in it if I accidentally lose them without manually saving due to the snapshotting, and I have no need for a stash because commits and branches are essentially just recording a checkpoint rather than being things that feel "heavyweight".
As an added bonus, dealing with conflicts is a lot less annoying because each commit records its conflicts separately, so fixing them doesn't require doing a stateful pipeline of changes in a big rebase; I can just do them piecemeal, in any order I want, and even just check out other stuff and work on them before coming back later if I feel like it.
I was "that guy" who would sometimes have coworkers come for help with git problems (https://xkcd.com/1597/ alt text). I've forgotten most of that knowledge (and all of that muscle memory) and didn't have to learn nearly as much to replace it with the ability to do a lot more with a lot fewer mistakes.
I guess they'll just copy submodules too. Kind of feels like there's little point using it if it's just going to copy Git's mistakes.
it is built, though, that the Git backend can be swapped for another backend.
I'm not sure where you're getting two production backends from. I guess you're referring to the Google internal one that nobody can use?
> There is currently only one production-ready builtin commit backend: the Git backend. <omitted> Google also has its own cloud-based backend.
https://docs.jj-vcs.dev/latest/glossary/?utm_source=chatgpt....
No, git-branchless is a wrapper around Git. jj is an independent source control system with git compatibility. jj can, and does, function entirely without git.
> I'm not sure where you're getting two production backends from. I guess you're referring to the Google internal one that nobody can use?
Lots of people within Google use it!
If you work at Google, jj can and does function without Git.
If you do not work at Google, jj is a Git wrapper.
I don't think harness like Claude Code or Codex support jj very well for working in parallel
Also, reading through their "SPECS".... https://github.com/JetBrains/thinkrail/blob/d299f20d2ba014f3... or https://github.com/JetBrains/thinkrail/blob/d299f20d2ba014f3...
How is this llm-vomit "specs that are ground truth" etc.?
Migrating my screenwriting software[0] from OpenTUI to Roc thought me what were once rough edges that take a lot of time are now just a prompt away from a solution.
It now uses 10x less RAM, bundle is half the size, and my initial implementation is 700-800 fps for scrolling and 200 fps for writing.
Granted, a TUI is less complex than a full-blown GUI, but I built a Roc Iced platform just as easily that abstracted Iced flux away
[0]: https://blisswriter.app/
Even if I wanted not to code it I couldn't. LLMs are still incapable of creating code up to any decent standard.
Also, while I do the get the joy of programming, we sometimes forget to focus on the user. You being happy to have typed the whole thing once, and have it run everywhere via the magic of browsers may not be the best strategy if this means your user's lap will be overheating.
In the end as much as I like coding I would prefer my users' experience to be the best it can be. LLM assisted code delivers this better and faster than hand-typing it all (which in turn is better than completely vibecoding it)
JetBrains tools are heavier and can take a few seconds to launch, but they also have some of the most responsive typing out there. They did some good work on zero-latency typing modes when that was a big topic and they were very good at typing latency relative to most editors.
They will never be the right tool for the personality type that gets angry when their IDE takes a few seconds to launch at the beginning of the day or when an application takes more than 1GB of RAM, but I am not that type of person so I enjoy them.
I think the TUI people are well served by vim or emacs and should just stay there and be happy.
The rest of your post feels like an injected ad for your project underneath a topic where it's not relevant
It also has nothing to do with TUI vs. GUI, since my comment addressed both (anecdotally).
If anything, your mentioning of their performance work is exactly my point.
JetBrains, explain concisely why this isn't written in C/C++/Rust?
(100% AI according to Pangram btw)
Rejecting slop doesn't imply rejecting all AI-generated text wholesale.
It’s a marker that the project is likely to be low-effort slop, which may or may not just be abandoned at the deep of a hat.
There's a famous Jobs story in which he insisted that even the insides of the computers be made beautiful. Because that shows care. Now people are arguing that even the outsides can be as ugly as they want, who cares.
Then I’ll probably hear about it again from someone I trust. I don’t need to be the first in my circle to test if this one is different.
I can do it. Anyone can do it. Probably better for my/their own needs than someone else’s agent can.
The README is meant to communicate substance and intent. Without the latter it’s an overly-verbose landing page.
1. AI generated text is just hard to read and verbose, if you worked so hard on your docs/specs, why would you want your README to be unreadable?
2. There's so much garbage written with AI that I'm just going to assume yours also is. Would you sign up to a gym with broken windows? It could be the best gym ever, but I wouldn't count on it.
Skill issue, it’s easy for a guy like me
If it is blatant unfixed llmese, then it means that no effort whatsoever was put into making this text.
What JetBrains needs is nothing short of a revolutionary product, which they would need to sell with an excellent introduction.
Instead they phoned it in and pasted that slop:
> Once a GitHub PR is open it shows the CI checks and review decision, and lets you mark it ready, hand failing checks or a diverged branch to the agent, merge it with the repository's last-used method, reopen it, or delete the remote branch.
The answer is very short.
But given you dont know me, im going to guess you wont be foolish enough to try and guess especially considering there are at least 100 different flavours.
Software is even more complicated. How is any person even the smartest software type in the world or AI going to know all the exact details of your wish if nobody tells them exactly every painful detail ?
Conciseness and highlighting relevant points is much more important than word count. Machine generated readmes are anything but. Sorry you can’t tell the difference between that and human prose, you should try reading more human content.
This is a useful criticism.
Left to themselves, LLMs prefer writing that's really atrocious. e.g. The writing will try and make everything sound profound.
The other problem I've noticed is e.g. LLMs will write in stuff that's inappropriate for the content of the text. e.g. Writing out stuff that looks like a chat reply, in commentary or descriptions or whatever.
I'd distinguish, though, between "sloppy writing" & "LLM generated writing". I'd agree if you didn't put in the effort to check the writing is of high quality, then perhaps the other parts are also not high quality.
I don't think just because "AI" wrote it it's bad. I wouldn't prefer e.g. sloppy human writing over well-crafted LLM-written text.
This readme the main thing which sticks out is the "what you get" bullet points are rather dense/verbose for bullet points. But aside from that it seems fine.
During the preset testing, I created dozens of READMEs using agents. Although I can't say that any of them were perfect for me, most of them were good enough.
README is a very special kind of document. For small projects, it's often the only one that potential users will read. The README should explain what the product is, what problems it solves, how to get started, provide some examples, and explain the restrictions. It should cover all these topics in a concise way so that even readers who aren't used to read long texts can easily read through it. It's definitely up to human to make it clear and easy to understand.
I care whether the readme is any good, not who wrote it. If you haven't bothered to critique the readme and instead critique its suspected creator — something entirely in your head — what else have you not bothered to do?
> (100% AI according to Pangram btw)
So what? Who cares about Pangram? I certainly don't! You cannot detect AI — it's impossible. Perhaps it's just Kenyans?[0]
[0]: https://marcusolang.substack.com/p/im-kenyan-i-dont-write-li...
Well, good luck in professional development then. Love it or hate it, this is the way everything is moving.
If you care about these things you are either not the intended target or you are a hypocrite.