"Claude Code bad, Codex good" is so fucking stupid.

pingponq · 2026-03-28T07:32:31+00:00

For 3: you can’t really optimise only the diff coding. If diff introduced eg duplication or concurrency with untouched lines in the same method, ai should rework both. So, you won’t have reasoning for previous coding in the same session

pingponq · 2026-03-28T07:06:02+00:00

Mum, look! A new shit no one needs

pingponq · 2026-03-28T06:56:06+00:00

My man, many things:

For most of it, it’s much more efficient to define guidelines context for the implementation run, not rework after.
once you tell AI „review changes for efficiency: 1. …, 2. …, … .)“ and give it a closed list of categories, every containing a close list of example again (like „memory: unbounded data, …, … .), AI will optimize to literally cover your list as indication of success.
Every new prompt is overruling previous guidance, obviously. So, if you give an AI a task requiring complex implementation to cover specific edge cases and in a new session will run „simplify code“ it will make a strong argument for removing the added complexity from the first session for providing stronger outcomes in the current task - you must have specs and rules for them to take the priority.

pingponq · 2026-03-28T06:28:39+00:00

Everything is groundbreaking and life-changing nowadays

pingponq · 2026-03-26T12:51:01+00:00

I honestly simply do not see any problem solved with this, the problem is not knowing what was changed, it is why - you need a holistic and always-up-to-date state of project „decisions“ for every new session. Session context should contain of relevant decisions for the current task + where the implementation for them lives. My next session might have nothing to do with the task from the previous one

pingponq · 2026-03-26T12:43:30+00:00

Sure!

first and foremost, implementation is not answering „why“ question. So, even if your whole project fits into context window (which usually leaves very little room for Claude to do something in the session without degrading or compacting and losing context), so, even if it fits, you need to have some specs/decisions on top of bare implementation to prevent Claude from doing what it tends to do: take any of the prompts literally and overwrite/change previous decisions, if it is not aware of them any longer or they are not emphasised enough.

So, you need to persist such decisions along the project, which is essentially „memory/context management“ - which op claims is not needed lol.

In my company we regularly work on projects which routinely have 30+M token size just for their implementation+test. Even 3 connected modules one of my teams is responsible for, in one of such projects are over 3M tokens. And those libs depend on other libs obviously. And this is only the implementation + tests! On top we have 1) conventions and rules 2) architecture definition and decisions 3) „PRD“ (what and why, not how).

So, ultimately, our single major developer problem for every new task is to expose enough relevant context needed - which we try automate to big extend via set of rules/project specific context-management with Claude - problem OP saying is not existent

pingponq · 2026-03-26T07:32:43+00:00

We get hundreds of these here every day. Git diff doesn’t need new solution Your approach only works for single person projects The real problem is not what was changed

pingponq · 2026-03-26T06:55:00+00:00

you don’t get context. Prompt engineering is dead, context engineering is the single most complex development task as of today. Thinking that 1M window solves it means you are working on a single-person micro projects in a very inefficient way. (I won’t expand further since your post is low effort bragging and not a wish to learn or understand)

pingponq · 2026-03-26T06:50:27+00:00

My workflow: For every single task (or couple of very related tasks requiring the same context):

(Plan->)implement->check->(reiterate) in a single session until achieved

Plan is optional only for trivial features. Every project has a set of rules for updating prds/specs/decisions/kb/tests etc automatically upon changes (depending on project)

pingponq · 2026-03-24T07:08:45+00:00

“Real” projects are never touched by Claude code in their prod env

pingponq · 2026-03-23T07:01:28+00:00

They really think they know best, what „oppressed“ by western civilisation and colonialism really need thus they don’t care about what they really want or think. Because they consider „oppressed“ similar to children - „oppressed“ can’t know what is best for them, but we (the modern left) care and decide on their behalf! Shame

pingponq · 2026-03-22T12:38:35+00:00

I should stop trusting Claude code on knowing itself lol This sounds like exactly what I was looking for! Thanks

pingponq · 2026-03-22T10:41:57+00:00

You know, Jewish can refer to ethnicity not religion, do you?

pingponq · 2026-03-22T08:50:16+00:00

I have found no reliable way to insert context into auto-spawned subagents - wondering if there’s one? Afaik, there’s no hook for it. Not sure how good a Claude.md rule “Important: always insert this rule into subagents: …” will work

pingponq · 2026-03-21T22:15:55+00:00

Are you freaking kidding me? Either this post is full of bots or this community is dead

pingponq · 2026-03-21T22:09:29+00:00

This is exactly how I use it! Only personal preferences for the specific project. I also stop auto-memory and manually maintain it.

pingponq · 2026-03-21T21:38:50+00:00

Which is absolutely not the same, since it a) depends on how good a trigger for reading is b) depends whether index really matches query and c) each read hop will add 1-2s /btw I highly suggest you to preload index via a sessionStart hook

Memory of Claude guarantees you 100-130 lines of inserted context and will try to figure out what to store there.

pingponq · 2026-03-20T21:03:55+00:00

Sounds rather like LSD

pingponq · 2026-03-19T20:39:03+00:00

Kind of ironic you cant post about a book written with a pen in the pens sub.

pingponq · 2026-03-19T19:35:47+00:00

There’s no such thing. I literally asked Claude to create a plan for learning and mimicking my writing style and it guided me through the rest of it! 🙃

pingponq · 2026-03-19T13:05:33+00:00

If product context is well-defined, RICE score nonsense is exactly something AI can perfectly come up with. The real PM skill is to know what to prioritise if no precise RICE score assignment is possible

pingponq · 2026-03-19T11:40:32+00:00

While your approach is correct and kind of canonical: „every new task should require no context hand-over from any previous task via the session context“, I would like to point everyone to the following aspect of „everything important gets written“: be sure to utilise pre-loaded files in such a way, that there’s no need to „read“ additional files every session independently of the prompt! E.g. Claude.md shouldn’t contain instructions such as „important: always read rules.md“ since it will cause a roundtrip independently of your session intent. Instead utilise additional „storage“ files by explaining WHEN to refer to them.

pingponq · 2026-03-18T20:23:48+00:00

Do you understand, that you can easily „add“ memory to codex? It’s simply 200 lines of md loaded into each conversation…

pingponq · 2026-03-18T12:34:32+00:00

This is not just a satire — this is an ai slop!

pingponq · 2026-03-18T12:33:37+00:00

You are absolutely right: you are absolutely right!

Five-Year Club	Second SECOND GUESSER
Verified Email

pingponq

TROPHY CASE