I dont understand why so many people have the need to emphasize the code vs product battle. There is no battle. Coding/developing/software engineering is a skill, that just like any other skill has certain requirements and best practices that have to be followed in order to make a quality, maintainable and adaptable application that can stand the test of time from the software perspective. Product, features, marketin…
The Claude Code Leak
51–60 of 203 posts
Re: The Claude Code Leak
#52" The real value in the AI ecosystem isn’t the model or the harness — it’s the integration of both working seamlessly together. " Wut? The value in the ecosystem is the model. Harnesses are simple. Great models work nearly identically in every harness
I tried to build my own harness once. The amount of work that is required is incredible. From how external memory is managed per session to the techniques to save on the context window, for example, you do not want the llm to read in whole files, instead you give it the capability to read chunks from offsets, but then what should stay in context and what should be pruned.
After that you have to start designing the think - plan - generate - evaluation pipeline. A learning moment for me here was to split up when the llm is evaluating the work, because same lllm who did the work should not evaluate itself, it introduces a bias. Then you realize you need subagents too and statt wondering how their context will be handled (maybe return a summarized version to the main llm?).
And then you have to start thinking about integration with mcp servers and how the llm should invoke things like tools, prompts and resources from each mcp. I learned llms, especially the smaller ones tend to hiccup and return malformed json format.
At some point I started wondering about just throwing everything and just look at PydanticAi or Langchain or Langgraph or Microsoft Autogen to operate everything between the llm and mcps. Its quite difficult to make something like this work well, especially for long horizontal tasks.
Re: The Claude Code Leak
#53Earlier quoted context omitted.
Hey there, author of the post here! I actually wrote this piece myself on my phone while I was out for a walk this morning. It was initially meant to be a quick note more than a full blog post —- whereas Coding As A Creative Expression took me a couple of days to write. I made a commitment to write more this year and put my thoughts out quicker than I used to, so that’s likely the primary reason it’s not as deep of a…
> wrote this piece myself on my phone while I was out for a walk If you have a strategy for jotting down (or dictating) notes while walking about, I would be curious how you manage that. I spend plenty of time walking outside, and tend to get (at the time) ideas that I'd like to explore further, most of which have evaporated from my mind by the time I get back home. Or even before I can get my phone out to jot down t…
Some are just born with it.
Re: The Claude Code Leak
#54I wonder what happened to the person that wrote "Coding as Creative Expression" ( https://build.ms/2022/5/21/coding-as-creative-expression/ )? I'm not (just) being glib. That earlier article displays some introspection and thoughtful consideration of an old debate. The writing style is clearly personal, human. Today's post is not so much. It has LLM fingerprints on it. It's longer, there are more words. But it doesn'…
Have you noticed that comments like "this post seems written with AI" are now appearing on all posts, even those written without AI? We're starting to become wary due to the abuse of AI and proliferation of sloppy content, but also because we often have trouble distinguishing authentic from sloppy content. Another feature of this AI era that I hate.
Re: The Claude Code Leak
#55Seems wrong. Devs will whine, moan and nitpick about even free software but they can understand failure modes, navigate around bugs and file issues on GitHub. The quality bar is 10-100x amongst non-techno-savvy folks and enterprise users that are paying for your software. They’re far more “picky”.
Re: The Claude Code Leak
#56I wonder what happened to the person that wrote "Coding as Creative Expression" ( https://build.ms/2022/5/21/coding-as-creative-expression/ )? I'm not (just) being glib. That earlier article displays some introspection and thoughtful consideration of an old debate. The writing style is clearly personal, human. Today's post is not so much. It has LLM fingerprints on it. It's longer, there are more words. But it doesn'…
What changed is you, the reader. In 2026 we treat the smallest signs as evidence of LLM writing. Too long? LLM. Too short? LLM. Too grammatically correct? Must be LLM.
Re: The Claude Code Leak
#57Earlier quoted context omitted.
Have you noticed that comments like "this post seems written with AI" are now appearing on all posts, even those written without AI? We're starting to become wary due to the abuse of AI and proliferation of sloppy content, but also because we often have trouble distinguishing authentic from sloppy content. Another feature of this AI era that I hate.
Agreed. Its so tedious that the top comment section on every HN post the last six months is "this seems be written by LLM" with a bunch of back and forth on whether it is or not.
Re: The Claude Code Leak
#58" The real value in the AI ecosystem isn’t the model or the harness — it’s the integration of both working seamlessly together. " Wut? The value in the ecosystem is the model. Harnesses are simple. Great models work nearly identically in every harness
I wouldn’t say harnesses is simple. They do a lot of things that we aren’t thinking of. I learned that a good harnesses is as valuable as the model. But obviously the model is what carries the whole thing. I tried to build my own harness once. The amount of work that is required is incredible. From how external memory is managed per session to the techniques to save on the context window, for example, you do not want…
Re: The Claude Code Leak
#59Re: The Claude Code Leak
#60Earlier quoted context omitted.
What changed is you, the reader. In 2026 we treat the smallest signs as evidence of LLM writing. Too long? LLM. Too short? LLM. Too grammatically correct? Must be LLM.
For me it was the "it's not x"/"it's y" stuff and some other structures Claude is very fond of using all the time. Perhaps humans are starting to write like LLMs!
But who knows!