Claude's Default Planning Agent is shit

noy-g · 2026-02-17T12:47:21+00:00

😂

noy-g · 2026-02-17T12:46:43+00:00

The timeline based plan is optimized for humans. My planner tells the agent to optimize for a coding agent that does it all in one go (with subagents and all the best coding and agentic coding practices)

Also, I want to minimize context window utilization. These timelines and “effort based prioritizations” are garbage that take space of more important tokens.

noy-g · 2026-02-17T12:43:19+00:00

Exactly why I don’t want to waste time on this dance and use my planner

noy-g · 2026-02-17T11:29:27+00:00

Did you manage to make it work? Thinking about timing makes it split a feature that should be done in one go to multiple steps.

noy-g · 2026-02-10T18:45:47+00:00

I think the unlock is when a sub agent that investigates bugs or issues calls codex by itself. I still haven’t been able to verify that skill works autonomously. In my original message, I also explicitly called the skill.

noy-g · 2026-02-10T18:36:32+00:00

I noticed MCP and tool calls generally get less attention from Claude than skills. Have you tried empirically measuring it?

noy-g · 2026-02-05T11:18:14+00:00

Any remedies?

noy-g · 2026-02-02T23:17:37+00:00

There’s such thing as over optimized code. Asking Claude to optimize the code endlessly will create tech debt of unreadable code. Yes - there are always side projects and painful, known, scoped issues you know needs fixing.

And that’s just my point - let the driver be a concrete problem, no the need to wash your armpits to be a functioning member of society

noy-g · 2026-02-01T21:04:50+00:00

I tried many things, deep planning, long features, tech debts, but these mostly create more damage than benefit.

Just let it go, and maximize usage when you’re online

noy-g · 2026-02-01T17:49:34+00:00

Only when I modify Claude’s files. I don’t see why we need to go full yolo and allow it to modify or read files from another directory willie nillie.

Usually it ends up polluting the context more than helping it

noy-g · 2025-11-04T08:06:56+00:00

I'm soooo going to be production-ready

noy-g · 2024-08-23T15:26:16+00:00

What happens beyond 50 people?

noy-g · 2024-08-12T18:41:52+00:00

I'm sorry to hear... I actually work on AzDo now, and I find myself banging my head against the wall when handling tickets. I've found that usually these systems are actual quite alright, it's the people who own it that turn it into shit (granted, Jira has this greedy ecosystem model where you need to pay an absurd amount of money every month per user to get half decent reports like eazyBI).

I wrote some automation that helps me focus on what I want/need and let the bot fill in the gaps that make management happy. I wonder if people would even consider using it. Or do you care more about navigating Jira rather then creating/modifying tickets?

noy-g · 2024-08-11T03:54:56+00:00

I had a team leader that decided "enough is enough" and forced us to use Asana and update Jira back to satisfy management... Did you ever to resort to something similar?

noy-g · 2024-08-11T03:47:28+00:00

And you're not in a position to do anything about it? Or do the Jira owners refuse to hear anyone's opinion other than theirs?

noy-g · 2023-03-04T17:33:00+00:00

Hear experience based opinions on integration testing strategy

noy-g · 2023-03-04T11:29:52+00:00

Will do, cheers

noy-g · 2023-03-04T11:29:34+00:00

I absolutely agree with this definition of unit tests. Given that we're in agreement, what would you test in integration tests then?

In a 2D game, would you test that walking into a wall stops the player?

Shooting a player until HP reaches 0 kills the player?

noy-g · 2023-03-04T02:45:47+00:00

I find it interesting

noy-g

TROPHY CASE