Note that I'm not saying the agents are useless. They certainly write a lot of code and sometimes it is good. But I don't think you can get away without touching code yourself simply because at some level it is often the most concise way to get your idea across. I find it best to implement a core set of changes by-hand, and then ask the system to e.g. replicate them to other dependencies. I genuinely don't understand how anyone can work on a system with any complexity, and get the results they actually want, without touching code.

I don't understand how people are making anything that has any level of usefulness without a feedback loop with them at the center. My agents often can go off for a few minutes, maybe 10, and write some feature. Half of the time they will get it wrong, I realize I prompted wrong, and I will have to re-do it myself or re-do the prompt. A quarter of the time, they have no idea what they're doing, and I realize I can fix the issue that they're writing a thousand lines for with a single line change. The final quarter of the time I need to follow up and refine their solution either manually or through additional prompting.

That's also only a small portion of my time... The rest is curating data (which you've pretty much got to do manually), writing code by hand (gasp!), working on deployments, and discussing with actual people.

Maybe this is a limitation of the models, but I don't think so. To get to the vision in my head, there needs to be a feedback loop... Or are people just willing to abdicate that vision-making to the model? If you do that, how do you know you're solving the problem you actually want to?

I don't know that 'removing' these as bus-stops would actually change anything. I think a larger question is whether route changes should occur.

There was a large effort in Philly called the 'Bus Revolution' [1] that aimed to re-balance routes (I have a map from the 50s on my wall and the bus routes are the same, including numbers, as they are today). The problem there was that there was a funding crisis that massively delayed the implementation [2]. These services are massively under-funded, and that's the primary issue; implementing the article's suggestions are not free.

[1] https://wwww.septa.org/initiatives/bus/ [2] https://www.nbcphiladelphia.com/news/transportation-and-tran...

I also don't understand your second paragraph at all.

I'm not sure I'm convinced of the benefit of lowering the barrier to entry to scientific publishing. The hard part always has been, and always will be, understanding the research context (what's been published before) and producing novel and interesting work (the underlying research). Connecting this together in a paper is indeed a challenge, and a skill that must be developed, but is really a minimal part of the process.

[1] https://news.ycombinator.com/item?id=44526912