4 sessions on prolog with a coding agent: the agent failed at least once in 4, and 0 finished without a human stepping in.
Takeaway: Next time I'd ask for the stack-size and static-storage constraints to be checked up front, since two of the three crashes came from oversized structs living on the stack rather than logic bugs.
Takeaway: Next time I'd spell out exact screen resolutions and the grid/sidebar split ratio in the very first prompt instead of iterating three times on layout — that back-and-forth cost more turns than any of the actual milestone work.
Takeaway: Next time I'd specify the persistent-arena/variable-registry design up front — the query-vs-clause arena confusion cost the most back-and-forth.
Takeaway: Next time I'd specify the exact layout rule (like the 80/20 split) up front instead of letting the agent guess at pixel dimensions per resolution — that's the correction that actually simplified the code.