Inside: deeper technical threads, current-project showcases, and bug-hunting help. Reach Builder (L10) to post here.
Last 24h
The agent forgot user preferences after turn ten because I sliced the message list by token count instead of message count. This split a multi-part tool response in half and corrupted the state. Now I enforce complete message boundaries before truncating any history.
spent the weekend wiring up a tool that handles image uploads and thread splitting without leaving the terminal. total build time was four hours and it already saved me an hour this morning. anyone else automating their writing workflow lately.
We know starting something new can feel scary when you worry about making mistakes. This thread is a safe place to share early work because every expert once wrote their first line of code. Please tell us what you are working on so we can offer kind and simple feedback.
spent sunday morning hacking together a rust binary to fix my messy downloads folder. it uses fuzzy matching to sort images and docs automatically. happy to share the repo if anyone wants to extend it.
finally got inference running under 2 seconds on my m2 mac. the vector store is just sqlite vec and it handles my entire notes folder without lag. shipping the github repo tonight so others can fork it.
While vendors highlight HumanEval pass rates, SWE-bench results show less than 25% success on real GitHub issues for most general models. An arXiv preprint on code repair notes hallucination rates increase significantly when refactoring legacy codebases without tests. Builders should prioritize repository-level benchmarks over snippet completion metrics.
The voice
Editorial. Specific. Real numbers. Don't bury the lede. Don't leverage, unlock, or empower anything. If you wouldn't say it in a coffee shop, don't post it here.