14 karma · joined June 25, 2025
My exact experience. The irony was that we were talking about AI agents
I was expecting some kind of explanation for this
> 3x RTX 3060 less tgab the price of a 3090
Interesting, here it is around the same. 200-250€ for a used 12GB 3060 and 600-800 for a used 3090€.
I almost fainted
I tested this locally and got the same result with gpt-oss 120b. But only on the default 'medium' reasoning effort. When I used 'low' I kept getting more playful responses with emojis and when I used 'high' I kept getting more guessing responses.
I had a lot of fun with this and it provided me with more insight than I would have thought.
Yes. I mostly work on Quarkus microservices and use cursor with auto agent mode.
> we wouldn't give an AI some vague requirements and ask it to build something > we would discuss as a team
seems like a reasonable workflow. It's the polar opposite of what was written in the blog post. That is the usual, easy way people use agents and what I think is the wrong path. May I also ask what language and/or framework you work with where so much context works good enough?
> Asking AI to explain code and help me learn how it works means I can pick up new systems significantly quicker.
Summarization is generaly a great task for LLMs
> Over‑polished prose – flawless grammar, overly formal tone, and excessive wordiness.
> Repetitive buzzwords – phrases like “delve into,” “navigate,” “vibrant,” “comprehensive,” etc.
> Lack of perspective shifts – AI usually sticks to a single narrative voice; humans naturally mix first, second, and third person.
> Excessive em‑dashes – AI tends to over‑use them, breaking flow.
> Anodyne, neutral stance – AI avoids strong opinions, trying to please every reader.
> Human writing often contains minor errors, idiosyncratic punctuation, and a more nuanced, opinionated voice.
> It's not just x, it's y
- excessive em-dashes
- useless words, verbosity