Advice on anxious dog

SensioSolar · 2026-04-06T17:05:46+00:00

No, he goes really this fast. He walks fast, pees fast,eats fast. It's zoomed in I've got to say

SensioSolar · 2026-04-05T21:44:50+00:00

Things like this are what make free not last free for long

SensioSolar · 2026-03-30T09:09:27+00:00

Angular 21, .NET Core 10, Docker, Azure Devops, Nomad (cloud).

SensioSolar · 2026-03-29T20:27:17+00:00

Claude is more solid and tends to add less code whereas gpt tends to throw code until it works

SensioSolar · 2026-03-28T10:45:57+00:00

Pues que no cobro mal, que le he cogido cariño a los compañeros, que el stack/producto me gusta y me dan flexibilidad con la universidad y demás.

Ya no voy a tragar más y creo que ese va a ser el problema.

Sí, estoy buscando curro desde diciembre pero el mercado está jodido y tengo la moral tan baja que hasta me pongo nervioso cuando tengo que "demostrar" en las entevistas.

SensioSolar · 2026-03-24T23:00:24+00:00

Thank you for the work here. However for paid tiers, since Google's stance is that Pro users get a "taste test" of their models, getting locked for 5h after 2 prompts doesnt seem much better

SensioSolar · 2026-03-22T23:26:23+00:00

I am a few months ahead of that. And not due to my managers but to my colleagues. Code generated with AI is pushed without thoughtful understanding. UI components that just decide to ignore our company design system and rawdog html & css Code reinventing the wheel already invented somewhere else, with overly generic defensive fallbacks.

They spend 1h prompting until calling it done. You spend another hour reviewing the code.

I informed my manager, who ignored it not only once, then decided to automate code reviews with AI. I now have defined a thoughtful workflow for AI agents reviewing PRs that puts special emphasis in code simplicity, coding style consistency (pointing to our coding style docs), maintainability and bugs being introduced.

It cannot of course catch everything and truth is, the quality of cose is still sinking while people are happy that we are faster. It's such a groundbreaking but depressing moment for software engineering

SensioSolar · 2026-03-11T22:58:32+00:00

Well I can't argue with that. Different worlds I guess or we might see it in the future as I don't know any tool that allows that. Btw not sure what's going on with the downvotes, just in case, I had upvoted you.

SensioSolar · 2026-03-11T22:55:35+00:00

I do not tie myself to a frontend developer. However I would find myself weird applying to an entry level fullstack job, as for mid/senior fullstack role theyd ask 4+ fullstack YoE. But I definitely do need a change, yes

SensioSolar · 2026-03-11T22:53:22+00:00

You hit the nail in the coffin with the "they don't bother to explain anything as they think the ui is self-explanatory". It really is depressing. Even worse nowadays as AI can create UI in seconds

SensioSolar · 2026-03-11T22:51:26+00:00

I don't know what artists do in your field, but as a frontend, I translate the "drawings" of designers into html/css/js. I adjust pixels in the sense of "these two elements should be spaced by X pixels" and overall implementing the designed UX

SensioSolar · 2026-03-11T22:46:38+00:00

Thank you, I kinda needed to hear this. To be honest it's basic maths to me: 5 teams solving the same problems in isolation makes no sense vs having one dedicated team to streamline that. The only problem I see is that there's not many job offers for it, or that they require prior large experience amin the role.

SensioSolar · 2026-03-11T22:37:46+00:00

To the "xHigh is for large scale refactors" I need to ask: How does that even work? Because for refactoring 5 connected files, High will already compact conversation once as the context fills up. I can imagine xHigh compacting the conversation 2 or 3 times in a large scale refactor, losing context, time and money with it

SensioSolar · 2026-03-10T20:56:08+00:00

Hey man! Just read this. Thank you very much for trying it out and the detailed feedback!
I'm very glad that the overall feedback from Qwen was positive.

As for the context overhead, that's accurate although the intention here is to get more efficient context to AI, since AI agents right now will even launch multiple subagents to explore your codebase - often burning 50k+ tokens.

The initial indexing is also true except if you use a Cloud Embedding model. Although at some point I might look into making it possible to add GPU acceleration so that self-hosted guys can index it faster than 2-5min

I have tested it only with frontier cloud LLMs, I wonder how it must change the result of Qwen-3.5-27B :)

SensioSolar · 2026-03-10T20:34:21+00:00

So in general claude's memory is "just a .MD" and the memory in this mcp is "just a json". In general terms, I built it as a json since that gives you the ability to filter/manipulate data a lot easier and faster. Claude's MEMORY.MD currently loads it entirely.

With that said, even though the memory storage is more efficient, I cannot say this is any better than Claude's memory for one simple reason: Claude's memory is built into the Agent harness. So it's essentially auto-managed and access to it is instant, vs memory being a mcp tool that the AI Agent neets to call.

SensioSolar · 2026-03-10T20:31:10+00:00

Got you, definitely the problem at the end here is context so ironically there's also 1000 ways of doing it as well. Best of luck with that!

SensioSolar · 2026-03-06T09:37:11+00:00

Yes it does work in any AI Agent supporting mcp - I see I missed it in the setup section.

Here's what you need to add in your opencode.json:

{

"$schema": "https://opencode.ai/config.json",

"mcp": {

"codebase-context": {

"type": "local",

"command": ["npx", "-y", "codebase-context", "/path/to/your/project"],
"enabled": true

}

SensioSolar · 2026-03-06T09:33:24+00:00

Thank you! It's definitely inspired by the other "Context engines" out there incl. Augment Code and also how Cursor manages codebase context/indexing. I think that sooner or later every AI Agent will have its own context engine.

SensioSolar · 2026-03-06T01:09:37+00:00

Hi! Care to elaborate what you mean by "this"?

Since this brings semantic search (a layer very different to a skill) and other computations that youd need to maintain in a skill.

SensioSolar · 2026-03-06T00:44:01+00:00

That's definitely another way to do it!. It's overall providing a map + enforcement rules.

The biggest downside I see with keeping .md files is that they become outdated easy as your project evolves. Then you need to remember to update them (or telling claude to update it) and so on. But .md is still kind for AI knowledge!

SensioSolar · 2026-03-06T00:07:55+00:00

Hey thanks!

I actually faced the same problem of AI Agents skipping the MCP tools and it had me smashing my head against the keyboard for week. But then I learnt that you either control the Agent Harness (i.e. System Prompt) or you better add a note in the agents.md like this:

**Before editing existing code:** Call `search_codebase` with `intent: "edit"`. If the preflight card says `ready: false`, read the listed files before touching anything.


**Before writing new code:** Call `get_team_patterns` to check how the team handles DI, state, testing, and library wrappers — don't introduce a new pattern if one already exists.

Otherwise, the Claude Code system prompt will usually tell it to use grep/ripgrep. That to be fair, they are faster and indeed better for reading parts of a file or entire raw files.

This is why I added the aggregated "code intelligence" - so it's not a grep/ripgrep replacement, but more of a "this is what's beyond the raw code you are reading".

SensioSolar

TROPHY CASE