441–450 of 498 posts
Tried to use this to create a minimal bootloader and kernel that prints hello world in x86 There was never a point in which it successfully did anything. 1. Tried to use macOS’s toolchain (m2 laptop so this is not going to work to build x86 binary) 2. It tried to fix that and failed multiple times. 3. Eventually I gave up on it trying to fix itself and told it to just use a container with Fedora Linux on it to work a…
Earlier quoted context omitted.
This is why you will have to pry vim and my own brain out of my cold dead hands. It’s not just the IDE but the ML model you are selling yourself to. I see my colleagues atrophy before me. I see their tools melt in their hands. I am rapidly becoming the only person functionally capable of reason on my own. It’s very very weird. When the model money dries up what’s going to happen?
I dunno. There's also a good chance that you just end up being left behind like graybeards that only wanted to code in C and assembler. I too am old enough to have seen a lot of unnecessary tech change cycles, and one thing I've noticed about this industry is no matter how foolish a trend was, we almost never unwind it.
This looks really cool except for having to learn a new syntax (is gherkin that bad?) however, something has been bothering me with all of these Agent AI based workflows. At what point do you actually do engineering? This was a great demo for a project manager. Lead your “team” through feature development. But without proper architecture, development really does become spaghetti. There’s vibe coding - and then there’…
It depends. A lot of projects / features really don't require a ton of engineering thought. Add a new table that has some foreign keys with existing tables, add a new page that lets you modify that table, add a new set of REST CRUD handlers that do some validation and store the data, add a new message queue that does whatever needs to happen when the data gets changed. If AI can handle things like that, then let AI d…
Yuk. That’s pure project management.
> If, in the future, PMs can launch whole features without engineers writing a line of code, that's awesome.
No it’s not! Because then, there is no incentive to engineer anything anymore. Just let the AI do it, Yey! Need new features? Let the AI do it! Need to fix your infrastructure, AI has your back! Has your product gotten so unwieldy that you have context rot and AI can’t do it anymore? Pivot, throw it away, rebuild with AI, who needs engineers.
Earlier quoted context omitted.
False. In order to maintain high quality I often rejected the first result and regenerated the code with a more precise prompt, rather than taking the first result. I also regularly used "refactor prompts" to ask Kiro to change the code to match my high expectations. Just because you use AI does not mean that you need to be careless about quality, nor is AI an excuse to turn off your brain and just hit accept on the…
> precise prompt If there was such a thing you would just check in your prompts into your repo and CI would build your final application from prompts and deploy it. So it follows that if you are accepting 95% of what random output is being given to you. you are either doing something really mundane and straightforward or you don't care much about the shape of the output ( not to be confused with quality) . Like in th…
I am not, and don't expect to be able to do that for many years yet. The models aren't that good yet.
I would estimate that I accepted perhaps 25% of the initial code output from the LLM. The other 75% of output I wasn't satisfied with I just unapplied and retried with a different prompt, or I refactored or mutated it using a followup prompt.
In the final project 95% of the committed lines of code in the published version were written by AI, however there was probably 4x as much discarded AI generated code along the way that was also written by AI. Often the first take wasn't good enough so I modified it or refactored it, also using AI. Over the course of using the project I got better at providing more precise prompts that generated good code the first time, however, I rarely accepted the first draft of code back from Kiro without making followup prompts.
A lot of people have a misguided thought that using AI means you just accept the first draft that AI returns. That's not the case. You absolutely should be reading the code, and iterating on it using followup prompts.
Earlier quoted context omitted.
The above is saying more precise not completely precise. The overall point they're making is you still are responsible for the code you commit. If they are saying the code in this project was in line with what they would have written, I lean towards trusting their assessment.
I am not doubting 95% acceptance rate all. I've pure vibecoded many toy projects myself. > in line with what they would have written, point i am making is that they didn't know what they would've written. they had a rough overall idea but details were being accepted on the fly. They were trying out bunch of things and see what looks good based on a rough idea of what output should be. In a real world project you are…
Earlier quoted context omitted.
There should be a standard rule format in a standard place, like ~/.config/llms/rules.md
this. We need a common file for all these tools. It's not like they can not read the format of each other.
Earlier quoted context omitted.
Q CLI has so many issues though, injects so much junk into you shell profiles it can slow down your terminal invocations by seconds, and it doesn't support standard streamableHttp / SSE MCP servers.
just turn those off, it's just 2 includes one at the top and one at the bottom of your shell... file a ticket about making it optional or not. I believe that the shell integration / autocomplete is where they started the product so it's probably one of those core features in the product team's minds. I generally like the integration but in some cases it's getting in the way of other ai that is runnin q to quit and al…
Earlier quoted context omitted.
Q CLI has so many issues though, injects so much junk into you shell profiles it can slow down your terminal invocations by seconds, and it doesn't support standard streamableHttp / SSE MCP servers.
That's for the shell auto-complete feature which I turn off.
Earlier quoted context omitted.
I don't know if this is feedback for Kiro per se or more feedback for this category of applications as a whole, but I've personally noticed that the biggest barrier holding me back from giving an earnest look at new coding agents are the custom rules I've set up w/ my existing agents. I have extensively used Copilot, Continue, Cursor, Cline, Aider, Roo Code, and Claude Code. I've just finished porting my rules over t…
It would sure be nice to have some standardized conventions around this. AGENTS.md etc. It seems insane to have to have multiple files/rules for essentially the same goals just for different tools.
Earlier quoted context omitted.
I don't know if this is feedback for Kiro per se or more feedback for this category of applications as a whole, but I've personally noticed that the biggest barrier holding me back from giving an earnest look at new coding agents are the custom rules I've set up w/ my existing agents. I have extensively used Copilot, Continue, Cursor, Cline, Aider, Roo Code, and Claude Code. I've just finished porting my rules over t…
Agents.md is at least used by both codex and GitHub copilot. VSCode has its own thing for instruction files and Claude.md is also its own thing :(