Vivek Kalyan
vivekkalyan.com
Vivek Kalyan
@vivekkalyan.com
Applied AI. Building cartograph.app. Previously: Head of AI @ handshakes.ai 🇸🇬

I write (sparsely) at: vivekkalyan.com
Inspired by my experience consulting for companies and the rise of inference time compute for LLMs (as well as the acceptance of users waiting while the LLM *thinks*), I suggest many teams working on RAG should rethink if you can improve your accuracy by relaxing latency.
January 20, 2025 at 6:44 AM
This really resonates with me. I spent 6 years building the AI products at my previous company and felt first hand the consequences of decisions (both good and bad). I've much more opinions on how to do certain things because of it.
January 11, 2025 at 2:26 PM
Try using a local UI (I'm using msty.app), and call Claude via API. Fits my bursty nature of usage, and monthly cost is much cheaper generally. You do lose their system prompt + Artifacts but I don't miss it much.
Msty - Using AI Models made Simple and Easy
AI beyond just plain chat. Private, Offline, Split chats, Branching, Concurrent chats, Web Search, RAG, Prompts Library, Vapor Mode, and more. Perfect LM Studio, Jan AI, and Perplexity alternative. Us...
msty.app
January 11, 2025 at 6:47 AM
They are the victims of their own media success, they raised at ridiculous valuation and they need to show that they disrupting the software engineering market beyond something like copilot/cursor.
December 12, 2024 at 11:32 AM
Do you have the link to the public repo? Java is highly requested, we just have been focusing on validating the usefulness of the current docs before spending time adding new languages.
December 8, 2024 at 5:05 PM
Cartograph solves this by automatically creating and updating both written documentation and visual representations that stay synchronized with code changes.

We are very early, but there's much more to ship. We would love to get some feedback on our product.
December 8, 2024 at 3:01 PM
In complex systems, we spend most of our time understanding code - but most AI tools are focused on helping you write more code. Engineering teams struggle with outdated documentation and inconsistent system diagrams. This slows down development and makes it difficult to understand complex systems.
December 8, 2024 at 3:01 PM
Congrats on the move! And your first 🦋 post.
December 4, 2024 at 10:00 AM
Yeah, hot mess is the right description of it 😂. Would be interested to see if there is a nicer solution.
December 4, 2024 at 12:56 AM
Yeah, I've been writing rust for a few months now for parsing codebase into a graph (cartograph.app). But, it's also a conscious decision to force myself to write "idiomatic Rust", i.e. more functional.
Cartograph | AI knowledge base for your code
cartograph.app
December 3, 2024 at 1:00 AM
Do you have sources for the budget claims? I have not seen any numbers comparing models so would be interested to know.
November 29, 2024 at 10:15 AM
Yeah, your feed is the training data for your brain. Curate it for what you want to see more of
November 26, 2024 at 6:37 PM
How does using an assert statement work in practice? Are you using something like pytest as your benchmark runner?
November 26, 2024 at 5:35 PM
Very disappointed your bio doesn't say learning machine.
November 26, 2024 at 5:28 PM
Good guidelines. One thing I want to add is if you are benchmarking your system's real world performance - you probably want to keep a version of the benchmark without the easy examples removed. Especially if you need to report to non-technical management how your system is performing.
November 26, 2024 at 2:56 AM
The most on-pulse demo would be on the bluesky firehose data.
November 25, 2024 at 5:02 PM
Models will follow the order of the schema you specify! So just putting the COT field first works well in practice. Structured outputs also ensure that the model response can be parsed as json. Use Pydantic/Zod here.
November 25, 2024 at 4:55 PM