It depends, do you want to learn or do you want to get something fast and don't care how?
If you want to learn don't let AI write anything. Ask it questions if you don't understand, ask it to explain, but wrte everything yourself.
If you want to get something that works and don't care how, make extensive tests. Use a minimum test coverage. Automaric AI reviewing the PR of the AI, And keep the agent going until it passes the CI.
To awnser your question specifically read the plans very carefully. Most of the time the agents execute the plan fairly faithfully, you don't need to correct the code much if you make sure to read the initial plan very carefully and make changes on where it made a mistake.
This does build on the fact that you can actually understand what its writing, if you can't, go with the first approach and don't use AI at all for writing code.
My 2 cents are that the issue is promotion not AI, if people started promoting stuff made without AI that would still be spam.
From the rules:
F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, your post is exempt from the 10% requirement. The exception does not exempt you from the account age requirement.
I would propose making this the requirement and not an exception, forbid all promotion of closed source, and allow the 10% requirement for open source projects.
Either the UI is defined in some DSL, that’s loaded (or compiled) and then you spend most of the time writing getElement(pathToElement) and wiring it up, or you have to boilerplate create each element and parent.addChild(element).
Im saying "there are no elements" because of what OP says here, the system i'm using now doesn't have that.
You have a panel+border+text “primitive” drawing functions. Nothing is stopping you from creating a single function that calls all 3 of those. You probably should, since it’s probably a common pattern. You could call it DrawBoxedText. There is no difference between a DrawBoxedText function and a BoxedText element with a draw() method.
yeah i could make a function for that, but i would argue that "here is no difference between a DrawBoxedText function and a BoxedText element with a draw() method." there is a big difference between these. Personally i find using a function like DrawBoxedText much easier.
I had my own library for UI that tried to have a element model, but it was bloated and didn't scale well.
Now im drawing everything via vulkan compute shaders and its fast and looks great.
I think the philosophy needs to switch from elements back to pixels, atleast that is what worked for me.
Depending what OP was using before but going from something like GPT5.2 to LLama 3 8B will be a massive difference (Although OP says to use it only for basic tasks so that does offset it)
LLama 3 already being a very old model doesn't help either
I run Qwen3.5-35B-A3B-AWQ-4bit which while leagues ahead of LLama 3 8B still is a very noticeable difference.
This is not to say open source is bad, if one had the resources to run something like Qwen3.5-397B-A17B it would also be up there.
It won't take any work, Luca has confirmed the image works on both Fairphone 6 and Fairphone 6+
https://wiki.postmarketos.org/wiki/Fairphone_(Gen._6)_(fairphone-fp6)
its on the wiki now too