And also files issues for blockers

I’ve absolutely caught things and made improvements just from skimming them occasionally - they are particularly useful when you get a PR that makes you scratch your head

But I’m definitely not taking full advantage of all the feedback coming in yet

I have to imagine parsing signal from noise there is a massive challenge when it’s other agents that are using your MCP and not just your own

thanks for all your work!

i've settled on all of this context attached to issues in a project management system and referenced from commits

it works just fine - its not like your agent cannot read your issue tracker

my wife and i have two non-overlapping sets haha you can imagine how that plays out

don't let the title fool you - the first half of the book is just elixir

over the past 8 years this is the book i've used to ramp back up on elixir and it works like a charm every time - i've never finished it

for me, a mark of a good programming book in this tutorial-project style is that I have started it half a dozen times and never finished it because at some point before the end I've been equipped w/ the tools to go off and do my own thing

> Why not? Who says that? Who proved that system understanding is not just more complex pattern matching?

I'm not in the camp of "system understanding is just more complex pattern matching"

but I am absolutely in the camp of "there are many tasks where pattern matching is just as effective as actual understanding"

but i also wonder to what extent this needs to be its own thing or if this is just something that it looks like we need but really people just need to shovel more stuff into their data warehouse / data lake that you never had reason to before, because now that's all fodder for agentic search

the only time i reach for official MCP is when they offer features that are not available via API - and this annoys me to no end (looking at you Figma, Hex)

The way I think of it, the main characteristic of agentic search is just that the agent can execute many types of adhoc queries

It’s not about a file system

As I understood it early RAG systems were all about performing that search for the agent - that’s what makes that approach “non agentic”

But when I have a database that has both embeddings and full text and you can query against both of those things and I let the agent execute whatever types of queries it wants - that’s “agentic search” in my book

"Assign agents the biggest piece justifiable. I can summarize a product outcome or a feature in two lines. That’s what goes on the ticket. Let the agents figure out subtasks when the work is ready for review, not before. Once you break an initiative into technical issues upfront, the outcome gets lost and the focus shifts to minutiae."

This is not about the ticket being well defined, this is about the agent having the larger context of what you are trying to do

e.g. spend time creating a skill about how to query production logs