Mika

I mean, I know you don’t have to. That’s what made the thread so funny. Mate got into murderhobo mood thinking that’s how durge needs to be played

Lmao reminds me that thread where dude said playing durge sucks because he had to kill Scratch and the game just isn’t fun anymore.

It’s in hundreds of millions and dude has like half a trillion. I’d say multiply by arbitrary number between 100 and 1000.

you’re a code monkey

You write your code manually and I set up infrastructure to avoid that, who of us both is a code monkey? :-)

I write tech plans too, from time to time.

concrete example

I already gave one. With jira & figma MCPs you just tell “read ticket <link>, read figma, make a separate component named XYZ. Look at file QWE to follow the same code style.”

This is literally in this thread.

Again, your solution should be already thought out and described in tickets and approved tech plan. If it’s not, SDLC problem.

And it’s not true that agents can’t help with edge cases, they can. If you know which points to look at, you task to analyze the specific interaction and watch which parts of the code would be mentioned.

I do write way less amount of symbols to LLM than I would when I write code. Those symbols don’t have to be structured and they can even have typos, so I can focus my brain activity on things that actually matter.

Plus, copilot is shit.

I rate your post as a skill issue.

This is necessary when working with 100% human code too.

deleted by creator

https://vger.to/piefed.ca/comment/2422544 mentioned here.

Dude are you a software dev? Did you hear about, like, tickets? You are supposed to split bigger task into smaller tickets at a project approval phase.

LLM agents are completely capable of taking well-documented tickets and generating some semblance of code that you shape with a few upcoming prompts, criticising code style & issues until they are all fixed.

I’m not theoretical, this is how it’s done today. MCPs into JIRA and Figma and UI tickets just get about 90% done in a single prompt. Harder stuff is done in “invesrigate and write .md how to solve” & “this is why that won’t work, do this instead” to like 70% ready.

Are you even reading what I say? You are supposed to have a professional approving generated stuff.

But it’s still AI-generated, it doesn’t become less AI-generated because a human that knows shit about the subject approved it.

So don’t accept code that is shit. Have decent PR process. Accountability is still on human.

Tbf AI tag should be about AI-generated assets. Cause there is no problem in keeping code quality while using AI, and that’s what the whole dev industry do now.