Our years of background in crypto data informed the design of Trails Bottom up, from contract primitives (functions, events, constants, etc) to our Explorer (search, understand) to Trails (app layer)

We’ve been using this at Herd for the last year, and it has been always great 😌

shoot for 2-3x faster - get that right. Then you can go chasing 10x 100x

I interviewed close to two dozen people this week and something I heard a lot of is "I don't think about the code too much but I think a lot about system design and architecture" I don't think that's quite right, and here's why: before you ever get to system design you should think about program design system design is important! it matters a lot for scalability. but if you don't think about your type system and if you don't carefully design your seams and figure out how to make your code testable (you should probably use dependency injection btw) and if you don't think about where state lives and how it's managed and if you don't think about control flow and where abstractions should and should not exist your code is going to be an unmaintainable, poorly-factored mess of bad types and spaghetti code and even minor changes will turn into shotgun surgery and MASSIVE diffs I have seen it done I have even done it myself and it has never ended well "GPT-7 will fix it" does not help you when there's an incident at 3am that the agents can't debug and now you can't debug it either and now you have to unwind months of bad code I also have never heard "I don't look at the code, just at the system design" said by someone who is actually good at system design program design and system design are more closely coupled than people think this was a very strong (negative) predictor of how someone would do on the system design part of the interview make of this what you will

What are all the positions affected by apyx and the STRC depeg? 50 tokens and vaults are intertwined in apxUSD across pendle, morpho, termmax, infinifi, neutrl, royco, beefy, and more (cross chain too on base and bsc). I break down the apxUSD balance sheet graph here:

Herd is a great tool to understand protocol risk and potential liquidity windfalls. We analysed apxUSD through Herd and Pendle has an exposure of $140M, Morpho $25M At a smaller scale Curve, Royco and Aeordrome also have exposure.

how to be good at your job - realize this one thing is actually made up of two separate things - realize instead of solving the direct problem you can solve a broader problem - instead of implementing thing, implement other thing that makes it easier to implement thing

One of my favorite things about @EffectTS_ is that I’ve spent the last year building an Effect-native frontend framework, and I still could not explain to you what a monad is. Best I can do is “you can flat map it”.

my goal is to keep kit so busy that "Later" never happens

a hundred or so tokens covered by doubleclick now 👀 pretty cool to watch the agent start to scale and run into other tokens while building the graph. am also learning that the operations of these tokens are even more wild and complex that I could have imagined 🤣 threads soon

using AI for coding is a deeply technical engineering craft most people don't approach it as so, and don't get the results we associate with high craft but the ones who do have been sprinting ahead more tokens wont save you, more thinking skill llm intuition will have been saying this for almost 9 months now

Why does tsgo use so much memory? Because it literally never frees memory allocated for types! And multi-threading overhead makes it likely to duplicate typechecking state on multiple threads I wrote about this in more detail here: zackoverflow.dev/writing/why… Basically: - nearly every type is allocated and then never freed (including transient types which are created and destroyed very quickly) - each thread gets its own type-checking state (types, symbols, etc.) - but they don't share data - so it's very easy for one thread to end up recomputing and allocating memory for types/symbols/etc. that another thread already did The end result is a very high peak memory usage!

the real moat is understanding your customers' problems better than everyone else. AI can help with this, sure, but it still takes a lot of care and judgement - it hasn't been accelerated the way coding has.

1/ Lots of people have asked me what I think about Claude’s new workflows. My take: they’re excellent. I’m already using them. I’m so energized to see the thesis behind Smithers getting validated.

Herd provides a level of transparency that is simply unheard of and cannot be replaced by a simple Proof of Reserve. Great stuff. More assets to come ;)))

your daily reminder to stop suffering through manual exploration on etherscan and use the herd MCP instead 🦬