colescodes

7 ms·

1. 1.▲
   by colescodes 2mo ago

   The Dagestan kebab shop guy left a trail though. Commits, has a PR thread, maybe a ticket. There's something to dig into, and an agent is decent at excavating it. Ask the agent why X and not Y about its own code and you get a fresh ans
2. 2.▲
   by colescodes 2mo ago

   The bewildered feeling is doing real work, I think. Reading my own code I'm checking it against a design I already have in my head. Reading someone else's I have to rebuild the design first, and that's where most of the bugs
3. 3.▲
   Reviewing code you didn't write(coles.codes)

   16 points by colescodes 2mo ago|6 comments
4. 4.▲
   by colescodes 2mo ago

   Author here. This came out of the last couple of weeks at work, where review has crowded out writing code because teammates and agents both produce it faster than anyone reads it. The short version: review the approach before the lines, and
5. 5.▲
   by colescodes 3mo ago

   I'd try Qwen 3.6 35B-A3B or 27B with a temperature of around 0.6. You'd need to offload some of it to RAM though. I've had okay luck with Gemma 4 12B with a temperature of 1.0 but it will miss things a lot :(
6. 6.▲
   Local Models in Mid-2026(coles.codes)

   3 points by colescodes 3mo ago|3 comments
7. 7.▲
   Understanding KV Cache: The Hidden Memory Cost of Serving LLMs(melchi.me)

   3 points by colescodes 4mo ago|0 comments