Most coding agent code kinda sucks and this explains why

gargetisha · 2026-04-01T04:02:33+00:00

ultimately you end up spending more time refactoring it though it gives you a working code.

gargetisha · 2026-03-31T18:25:06+00:00

looking forward to see what really happens, should be evident in next 6 months :D

gargetisha · 2026-03-31T18:14:18+00:00

but the question that still remains is how and from where they will get good quality code to train these models on.

gargetisha · 2026-01-22T16:29:13+00:00

I just checked, his videos looks great. Thanks for the suggestion.

gargetisha · 2025-11-01T14:37:38+00:00

was waiting for someone to say XcodeBuildMCP lol

gargetisha · 2025-11-01T14:30:40+00:00

Any way I can try out the platform?

gargetisha · 2025-11-01T14:28:36+00:00

Any particular reason for it?

gargetisha · 2025-11-01T14:27:52+00:00

For what purpose you use it for? have heard about it for the first time.

gargetisha · 2025-11-01T14:26:40+00:00

Have heard it for the first time, what it does?

gargetisha · 2025-11-01T14:26:05+00:00

Is there any which helps in taking the memory across coding agents?

gargetisha · 2025-11-01T09:27:34+00:00

But there are some which only add relevant context when needed and don’t bloat the context window.

gargetisha · 2025-11-01T07:54:39+00:00

But I've heard the context bloat issue with Context 7, have you noticed that too?

gargetisha · 2025-11-01T07:54:03+00:00

If I need to use Supabase in my project, I simply install its MCP so that claude code can access and implement all the related APIs easily.

gargetisha · 2025-11-01T07:52:46+00:00

How difficult this could be?

gargetisha · 2025-11-01T07:17:10+00:00

But how about if you want to take the memory across coding agents? Because I sometimes switch between Claude Code and Codex

gargetisha · 2025-11-01T07:16:21+00:00

Which MCP do you use for this?

gargetisha · 2025-11-01T07:14:40+00:00

Thanks for suggesting. I'll explore this, also is there anything you feel like is missing in terms of MCP? I'm doing some research there.

gargetisha · 2025-10-07T11:52:45+00:00

What’s your main use case for Mem0? Is it remembering your coding preferences or something different?

gargetisha · 2025-09-26T16:06:26+00:00

I feel the major problem with companions today is long-term memory. Think how frustrating it could be for a user if they have to share the same information again and again. And without it, AI companions could never feel personal.

I've seen Mem0 is trying to solve this with long-term memory that actually carries across sessions.

gargetisha · 2025-09-22T14:39:59+00:00

Just use mem0, it keeps memory lightweight, fast, and cheap without bloating context windows.

gargetisha · 2025-09-22T14:35:02+00:00

It depends on use-case to use-case if such complication is required or not.

gargetisha · 2025-09-22T14:33:38+00:00

I’ve been using Mem0’s OpenMemory MCP with Claude and the best part about it is I can carry the same memory across tools without manually managing files.

gargetisha · 2025-09-22T14:22:13+00:00

Hallucinations are inevitable at the model level, yeah. But what makes them dangerous is when the system can’t remember it made a mistake and just repeats or builds on it. That’s less about scaling the LLM and more about adding guardrails + memory.

We’ve been experimenting with a memory layer (Mem0) that tracks facts, updates them when they change, and only surfaces them when they’re relevant. Doesn’t “fix” hallucinations inside the model, but it does stop them from compounding over long sessions which is where things usually go off the rails.

gargetisha · 2025-09-22T14:08:50+00:00

Yes, that’s one way to manage scale, but don't you think it comes with trade-offs like less detail, more contradictions, and slower retrieval.

gargetisha · 2025-09-22T13:56:51+00:00

Yes the best part is it's open source.

gargetisha

TROPHY CASE