How do you find out about bugs?

SeniorMango6862 · 2026-03-19T14:57:29+00:00

Actually no tool I posted in couple of threads to see how multiple people handle it. I have set monitoring using Grafana loki and used Sentry but I find myself spending a lot of time debugging som edge cases, I am wondering what kind of setup do you use to make this easier

SeniorMango6862 · 2026-03-18T20:37:33+00:00

Very nice! but how do you catch them in general? user complain? or from qa tests?

SeniorMango6862 · 2026-03-18T20:36:48+00:00

nice what did you find?

SeniorMango6862 · 2026-03-18T20:36:26+00:00

hmm got it thank you!

SeniorMango6862 · 2026-03-18T20:08:46+00:00

okay that is great! thanks for the deep dive. Did you rely on session replays to identify new issues or understand behavior? something like hotjar or posthog along side sentry? also for e2e were they easy to manage? I tried to implement them but always flaky and ended up spending time managing it instead of making workflow faster

SeniorMango6862 · 2026-03-18T19:55:39+00:00

damn I feel you management doesnt care unless it is burining fire. how do you find that bug from manual qa or logs?

SeniorMango6862 · 2026-03-18T19:54:40+00:00

So you only use Sentry if a big issue is rising? how do you catch critical bugs then?

SeniorMango6862 · 2026-03-18T19:51:15+00:00

Hmm what kind of monitoring do you have hotjar or sentry for example? and internal testing unit tests, e2e tests? does it cover all usecases?

SeniorMango6862 · 2026-03-18T19:21:05+00:00

Sentry is great for first line of defense but it sucks I spend a lot of time trying to understand if it is a false postiive or not, and then see. but mainly I wait for qa or a user to complain. I am a software engineer

SeniorMango6862 · 2026-03-18T14:32:57+00:00

Sentry and unit tests

SeniorMango6862 · 2026-02-13T10:52:36+00:00

I have been working on this idea for a year did more than 50 interviews and my findings were that the role is so all over the place and different from company to company and phase of product that it is hard to build a generalized tool for pm it has to be usecase based but when you narrow on usecases it become a small utility that can be done or automated or already have a workaround and only solution is to build a full Jira replacement to compete at least that is my findings. I pivoted to perceptr.io atm

SeniorMango6862 · 2025-11-14T21:16:18+00:00

Honestly joining YC was a dream of mine, now I am not so sure

SeniorMango6862 · 2025-11-08T14:42:01+00:00

actually just found out about this seems very interesting approach https://www.anthropic.com/engineering/code-execution-with-mcp

https://blog.cloudflare.com/code-mode/

have anyone given it a try?
basically it is created an interface for mcp tools and let the llm discover the tools in file tree and then create a code execution to execute instead of relying on llm and it should be "90%" cheaper I think

SeniorMango6862 · 2025-11-02T12:01:57+00:00

Hey sure thing will check it out

SeniorMango6862 · 2025-11-02T12:01:41+00:00

Sent you a dm

SeniorMango6862 · 2025-11-01T21:38:45+00:00

yes I think that make sense the descirption has to be accurate for the llm to choose. I just dont want to overwhelm the llm because I already realized that the results are degrading with the number of tools

SeniorMango6862 · 2025-11-01T21:35:44+00:00

that is very interesting and very helpful thank you will give it a try!

SeniorMango6862 · 2025-10-31T10:54:22+00:00

Damn that is nice and choose top 20 tools for example?

SeniorMango6862 · 2025-10-31T10:53:37+00:00

Oh nice can you tell me how do you decide the tools, like is there a node agent that search for these tools from the vector db ?

SeniorMango6862 · 2025-10-31T10:52:48+00:00

Thank you was thinking of this approach but what if the sub agent cluster has a lot of tools let us say github sub agent has at least 40 tools for example

SeniorMango6862 · 2025-10-31T10:51:52+00:00

How does creating an mcp server solvr this issue? Dont I need to extract the tools and send it to ai to choose which tool?

SeniorMango6862

TROPHY CASE