My AI agent was burning my tokens to produce garbage.
Hallucinations. Useless tests. Bad code.
The problem wasnโt the agent.
It was context engineering.
I learned how to fix it and put everything into a free guide ๐
@itsvishaltwt My take: Experience.
Recruiters still filter on it first, and it is the only signal that proves you shipped under real constraints:
deadlines, reviews, production bugs, and teammates who depend on you.
Experienced roles have a clear advantage
Mine is called "hitl cli."
It's kind of coupled but, I start thinking it is a good idea to make a tool others can use.
Let's see if I've got the time ๐
Hey, boy.
Stop opening full claude or codex to commit or run an action.
Set up a command that does that for you instead of opening the whole thing.
Keep reading ๐
This is not only useful for generating commits with Ai But other amplified commands like opening a PR, resolve pr comments, etc...
You can program the cli tool or see if someone else created a command launcher for your OS.
@itsvlady Same here, man.
This week has been insane with all the work I've done with the same subscription. Now it is hard to reach the weekly limit.
Not only that. Ultracode now works for hours with fewer interruptions because of the 5-hour limit.
This Opus is amazing
I'm noticing Opus 5.5 is quite creative and proactive when it shouldn't.
Its code adds things it shouldn't touch (ignoring the spec constraints) and applies the Boy Scout rule when it sees the opportunity...
I can't believe I'm prohibiting the Boy Scout rules in my AGENTS.md ๐
Yesterday, I started spending more time than used to reviewing code in my job.
While this is an advantage for vibe coding, it means shortening the leash for agentic engineering and adapt.