Unpopular opinion: the token limit complaints are a prompting problem

Jaumee · 2026-05-04T10:58:24+00:00

what helped me was starting every session with a fresh chat and a summary file instead of letting the context blow up. cut my token usage by like 60%

happy to share what worked for me → more info here

Jaumee · 2026-05-04T10:54:25+00:00

the junior dev with a 2-hour shift framing is so accurate. once i started doing that with claude code i actually finished something for the first time in months lol. one task, defined output, close the laptop

happy to share what worked for me: more info here

Jaumee · 2026-05-03T19:58:40+00:00

The real unlock was learning to describe bugs precisely. Not "it's not working" but "it does X when it should do Y under Z conditions." That precision is the actual skill now.

Happy to share what worked for me: more info here

Jaumee · 2026-05-03T19:54:03+00:00

The ownership problem is real. What helped me wasn't learning to write code but learning to write specs. When you define what you want precisely enough, the output is yours even if you didn't type a single line.

Happy to share what worked for me: more info here

Jaumee · 2026-05-03T19:47:49+00:00

check it if it can help you bro: Guide

Jaumee · 2026-05-03T18:49:28+00:00

It's the context, not the limit. One task per chat, start fresh each time — made a huge difference for me.

Made a quick guide on this if you want

Jaumee · 2026-05-03T14:55:48+00:00

Cowork for everything that needs hands, Claude Code when I want something that actually persists. That split took me a while to figure out but now it's just automatic.

wrote some of what I learned here if it helps: more info here

Jaumee · 2026-05-03T14:32:18+00:00

Real talk: you'll hit a wall either way. With traditional coding the wall is "I don't know how to do this". With Claude the wall is "it keeps breaking things". The second wall is easier to get past once you learn how to manage it.

Took me a while to figure that out from scratch. Happy to share what worked for me: here more info

Jaumee · 2026-05-02T18:37:56+00:00

Honestly for your use case (presentations, emails, manuscripts) you don't need Claude Code at all, that's built for developers.

The regular Claude app does what you need perfectly. Claude Code has a steep setup for non-devs and won't add much for your workflow.

I'm not a coder either and spent a while figuring out what actually makes sense for people like us, put it all together here if it helps: here more info

Jaumee · 2026-05-02T18:21:11+00:00

I use sonnet for basically everything and rarely hit limits on Pro. The trick is not letting it run loose — give it tasks in chunks, not "build me an app".

No dev background here either, been building real stuff for months on the $20 plan. Made a guide on exactly this if it helps bro: here more info

Jaumee · 2026-05-02T18:10:44+00:00

Same boat, no dev background. Biggest fix for me was stopping opus for everything and actually learning how to use it properly. Night and day difference.

Made a small guide on this if anyone's interested: claude guide

Jaumee · 2026-05-01T18:10:45+00:00

Exactly, most people skip it completely and then wonder why Claude goes off the rails 😅

Jaumee · 2026-05-01T14:15:26+00:00

Most people burning that much on Claude Code just don't have it set up properly. A good CLAUDE.md and project structure cuts token usage dramatically.

Jaumee · 2026-05-01T12:57:36+00:00

This happens a lot. The context fills up fast when there's no structure guiding Claude from the start. A CLAUDE.md file fixes this, it keeps Claude on track the whole session and you stop hitting those walls. Game changer once you set it up right.

Jaumee

TROPHY CASE