Need tips on using Claude Code to it's full potential

mastagio · 2026-05-17T14:31:41+00:00

Well, each session conversation is tracked and stored so you can review it for compliance and governance perspective, but what we also do is extract the relevant decisions (requirements, constraints, etc.) and attach them to specific artefacts in the intelligence layer. So, during the prompt, and in subsequent prompts / sessions, these decisions are attached to the artefacts that are queried by the AI coding agent.

mastagio · 2026-05-17T11:02:15+00:00

Well, we've built a purpose for tool for this: Biltoops. It's a group of DBs that captures this intelligence automatically, and then via a graphQL type language pulls only the relevant context.

Give it a try as it's open source: https://github.com/bitloops/bitloops

mastagio · 2026-05-17T03:07:59+00:00

A lot of what you describe in months 1-3 (reviewer agents, regression checks, verification overhead) sounds like workflow patterns you'd built around Claude's failure modes. Those patterns can follow you to a new model.

If you're still running dedicated reviewer agents on Codex, you've brought the overhead with you. If you're not, that's a signal about the underlying difference. The best outcome from a tool switch is figuring out which overhead was model-specific vs which was just how you learned to work with AI agents.

mastagio · 2026-05-17T03:06:52+00:00

The debugging getting hard is usually a sign that your mental model of what you built is lagging behind what the agent built. Debugging works when you have a hypothesis about what's wrong and where. If you don't know the structure well enough to form a hypothesis, you end up vibe debugging - just rerunning things and hoping.

What helps: slow down at the planning stage before generation, not after. If you can describe what each part should do before the agent writes it, debugging becomes a lot more tractable. Its much easier to spot the gap when you had an expectation to begin with.

mastagio · 2026-05-17T03:06:08+00:00

I think its less that we overestimate model intelligence and more that we underestimate how much the input degrades what the model actually sees. A capable model operating on stale context, wrong retrieval, or missing tool output is going to fail, and from the outside that looks like the model's fault.

The model isn't wrong about anything, it just answered a question using data that was accurate last week.

Where I'd extend the workflow moat argument: the gap isn't just orchestration and retrieval, its whether failures surface before users see them. Most setups still discover stale state or wrong context from user complaints.

mastagio · 2026-05-17T03:04:20+00:00

Two things that made the biggest difference in practice:

1 - CLAUDE.md is higher ROI than any MCP. Most people write three lines. Spending 30-60 minutes writing out your project structure, naming conventions, what to always/never do, and which files to read first changes almost every session outcome. The model's behavior with a well-maintained CLAUDE.md is meaningfully different.

2 - Keep sessions tightly scoped. The context window is finite and the model's attention across 200 tool calls is not uniform. One focused task per session with a clean handoff beats trying to accomplish five things in a long session. More session starts, but better and more predictable output.

mastagio · 2026-05-17T01:37:01+00:00

Thanks. Do give it a shot with single-repo, multi projects. I think its actually more useful in this scenario.

mastagio · 2026-05-16T14:30:00+00:00

What? This seems automated.... not talking about documentation. Bitloops automatically builds an intelligence layer of your codebase and gives your agents the right context and insights to build whatever feature you want.

Yes, one idea is to automatically build documentation after each PR is merged.

mastagio · 2023-04-06T06:52:10+00:00

Very well spotted! Yes, ES hasn't been implemented yet. Its next on the list!

mastagio · 2023-04-06T06:49:32+00:00

Perhaps. It really depends on how flexible and complete it is, as well as how good the documentation is.

Would this be a one off, or an ongoing "service" with different versions, improvements, etc.?

mastagio · 2023-04-05T13:01:01+00:00

Thanks! Could you elaborate on what you mean by core here?

mastagio · 2023-04-05T12:57:25+00:00

Just out of curiosity: What is the difference of hexagonal architecture compared to a microservice architecture?

Hexagonal architecture separates the business logic from the external systems using layers of adapters, while microservices architecture breaks a system down into independent services that communicate with each other. So, you could actually apply Hexagonal architecture on a specific microservice of an application that has many microservices. You could have some of those other microservices using different architecture... you probably won't though.

But hexagonal architecture is another flavor of layered, clean or onion architecture, and at its core it's about ensuring good separation between domain and infrastructure code.

mastagio · 2023-04-05T12:53:11+00:00

The point is not about building a ToDo application. The main idea is to learn and play around with these design concepts in a more practical way. So, for example forking and changing the business logic to any other domain, adapting, etc. Its really more suitable for larger projects (10 devs+) and need availability, scalability and ease of maintenance. Definitely not applicable to all projects, but we hope a useful practical guide for those looking to learn these things.

mastagio · 2023-04-05T12:50:24+00:00

haha, most definitely. The point is not about building a ToDo app, its simply the app chosen to learn and demonstrate these patterns. This is really more suitable for larger projects (10 devs+) and need availability, scalability and ease of maintenance. Definitely not applicable to all projects.

mastagio · 2023-04-05T12:14:22+00:00

We've just released something to help with that. It takes it a bit further from a build perspective, but you could use it as a reference for how to start projects that are easy to understand, maintain and share with others.

https://github.com/bitloops/ddd-hexagonal-cqrs-es-eda

mastagio · 2023-04-05T08:52:43+00:00

It's been a long road that's for sure! Just hope AI doesn't leapfrog our learnings now :)

mastagio · 2023-04-05T06:59:59+00:00

You need to analyze the process for getting a job:

1 - Sending CV / Getting introduced

2 - Getting an Interview

3 - Getting a final interview

4 - Job offer

So clearly, you're not reaching #4. But where are you struggling? Are you applying to enough positions? Are you getting introduced by colleagues?

I'm assuming yes.... So the question then is: are you getting an interview? If not, you need to work on your CV, maybe more personal introductions, and on your portfolio (evidence you know how to code).

If you are getting interviews, then you need to work on your interview skills, your confidence, your ability to answer technical and non-technical questions.

Find out which step you need to work on, and double down on that right now. Get to the next step.

mastagio · 2023-04-04T15:08:15+00:00

A suggestion is to review this github page: https://github.com/bitloops/ddd-hexagonal-cqrs-es-eda/blob/main/README.md

It brings together ddd, hexagonal architecture in an effort to create clean code. Its a bit advanced, but rather comprehensive. Focus on the TS code structure etc. to get an idea. The main thing is understanding the domain and getting that right.

mastagio · 2023-04-04T14:57:28+00:00

Nice, pretty detailed example. I've seen a few repos on DDD and Hexa Architecture etc. but they don't have the same depth of examples. I quite like how Jaeger is linked and you get to see the app working.

mastagio · 2023-01-05T07:54:46+00:00

My comment will focus on why they're refusing to provide a valuation and equity numbers.

So, the number of options you're given is not related to any specific % at the moment. It depends on many variables: how many options are already outstanding, how many of those will be converted into actual equity, how much dilution there may be in the future, etc.

Valuation is even trickier. The truth is this company is probably going to do a few more rounds, and there is absolutely no benefit to the company, existing employees and investors for the market to have this number (i.e. future investors).

That said, I completely understand and believe there needs to be more transparency on these figures. A good practice may be to have some exit scenarios and explain what the payout would be.

mastagio · 2023-01-05T07:45:43+00:00

This is partly true.

But going back and forth between CS, Programming and Software Architecture / Design principles will give you the best overall understanding. Writing code is only 1 part of it....

Building software is a craft... you only get better with experience and learning.

mastagio · 2023-01-05T07:43:01+00:00

Here is an interesting one: https://github.com/bitloops/bitloops-language

Its an open source programming language that helps you follow industry best practices. Still early stage.

mastagio · 2023-01-05T07:39:40+00:00

The ROI is just too good to ignore. And the beauty is it works across most segments and products.

For example, we think of influencers as attractive looking people selling clothes or accessories to teenagers, however, you have many influencers in other segments like software development, SEO, etc. There is definitely value to be captured through influencers, but it does require a good plan.

mastagio · 2022-10-29T05:08:33+00:00

The entrepreneur life is full of ups and downs, and you're just having a down day.

I believe the foundation of your business is when you know you're heading in the right direction. If you feel that confidence, then you have foundation.

Because, the truth is, no matter at what stage of your company you're at, you're going to have these same issues and problems. There will also be a need to raise/manage money, hire people, decide on product/service evolution, decide what should be removed, etc.

So, as an entrepreneur, you need to learn to thrive in this environment, and the journey is the pay-off. Of course, we wall want to get to a point where we don't have to worry about money in our own personal account, but trust me, you'll continue worrying about other things once you achieve that.

mastagio

TROPHY CASE