You should have guardrails, that catches these critical paths.
Shipping is a muscle, and every engineer knows how to ship good production code, just that we end up spending too much time, on perfecting tiny details. Just have good engineering discipline. Feature-flags, beta releases.
A good question to ask is why aren't you shipping every week, regardless of how critical your feature is.
time to use claude code to understand DEKs paper, in plain English. As someone who did a bit of formal verification in grad school. I feel like, there are a long tail of problems that can be solved by human-model collab like this one. The problems may not mean much but hopefully it can stack up understanding of intelligence.
I actually spent some time on it, researching the best practices, and tried hard to make it a useful reference for the future, than just another marketing blog.
Feedback on any improvement of the technical limitation, and just the language would be appreciated .
Also would love to understand anything that people do thats different than whats covered in the blog.
I am sure you meant well, but it was your word-choice. Show some grace to the founders trying to build stuff. Its easy to nit-pick ideas and execution. You could have ask the same thing politely.
Focus on local, non-western LLMs, is not a unique differentiation, I am sure Peec can implement it tomorrow, if you guys want to.
Or were you only looking for differentiation so you can build it at Peec.
If two products are solving the same problem, eventually they will converge on the same feature-set. You should know that better.
https://docs.google.com/spreadsheets/d/1_ASxAG38uP3_vcVqVnhP...