@getpy Absolutely. I do want to see how to illustrate that better for people from other communities, although now I think about it, it might become pure comparison rabbit hole as well. Hmmmm!
Tomorrow I'll focus on my actual and personal experiences as I build many applications with @DSPyOSS, also going to be my first presentation on a TUI :)
https://t.co/CJU7XGDhwH
@MaximeRivest Yup. Human level context engineering is missing out. It’s why I stopped having MCPs by default, and barely have rules/skills if any. I also have never ran out of usage for CC. And I love it that it’s a loose cannon because I already control where it can go wild.
@jamesacowling I’m always confused by this. If there r too many lines changed, ask for split. Just better standards, better checks, already filter a lot. Comm on issues, PRs. Good software takes time to review and build. Why keep on trying to make it “fast”? Just communicate on trade-offs.
@lateinteraction I find that, because conversation/chat is many people’s first major interaction with NLP, it’s hard to imagine beyond its application when that’s just one of the many possible ways to frame tasks.
@tech_optimist is my inspiration to write more, and after reading this piece on writing, it's making me think more about how to formulate my ideas into more concrete outlines better. I know my content will be scattered, but hopefully I can have another piece after NYE :D
This year, I've gotten a ton positive feedback on my writing from people in all walks of life: engineers, academics, CEOs, VCs and even non-technical folks. So I put some thought into why that is, and externalized my thinking into this blog post 👇🏽
1/3
https://t.co/xi1pzvenp9
@CodeByNZ If you use nvim, actually you probably don’t even need to be a regular user, just a bit setup, I reco https://t.co/oR0XqW64zV
It’s light weight (just a file), I can run some rest and grow endpoints before Postman even starts up :D