svstoyanovv

15 ms·

1.
by svstoyanovv 7mo ago
I think this requires discipline. The good thing is that we have coding agents, but again, you need a standard to tell the agent what to always look for, how to find it, and to describe your modules properly (even Claude Opus 4.6 makes mist
2.
by svstoyanovv 7mo ago
I understood the example, and it could be a minor hiccup there, but the essence is different: By having a structured context of the key session discoveries, decisions, rejected items (if there were past commits with decisions that had been
3.
by svstoyanovv 7mo ago
Yeah, you need to be aware of hallucinations for sure. Today, for example, I was doing my one linear, I've used all the curated knowledge to make some structure to it, see examples of deep research, brainstorm ideas around it, but I am
4.
by svstoyanovv 7mo ago
Why only small changes tho? I think it can also work with larger changes if you commit more regularly. And with agentic coding or even with autonomous agentic coding, you need to do it regularly and create these contextual checkpoints, no?
5.
by svstoyanovv 7mo ago
Suppose you spend months deeply researching a niche topic. You make your own discoveries, structure your own insights, and feed all of this tightly curated, highly specific context into an LLM. You essentially build a custom knowledge base
6.
At what level of deep context engineering does AI output become human-crafted?
1 points by svstoyanovv 7mo ago|0 comments
7.
by svstoyanovv 7mo ago
Have you tried, as Peter Steinberg suggested, "I ask for Specifications to be submitted, I can generate then the code based on that spec in a minute" - what we also find useful is exactly this, if a contributor wants to submit a P
8.
by svstoyanovv 7mo ago
Oh wow, this is insane. I was digging into Moltbook when it launched, and the creator said, "I had a dream about an architecture". Really interesting times we live in, indeed. The crypto bros started utilising the network to promo