TStarini sunilinai-content-utilties.hashnode.dev·1d ago · 4 min readWhat Your Documents Mean, Not Just What They SayOn this page A Tiny Experiment Why Keywords Fail Meaning Without Matching Words The Hidden Layer A Simple Mental Model Try It Yourself The Aha Moment The Hidden Signal In the previous artic00
TStarini sunilinai-content-utilties.hashnode.dev·May 30 · 5 min readWhat Your Documents Whisper When Nobody's LookingMost people think important information is easy to spot. Look at enough documents and you will find the important topics because they appear again and again. More mentions = more importance. Right? No00
TStarini sunilinai-content-utilties.hashnode.dev·May 18 · 4 min readWhy Most RAG Pipelines Destroy Document StructureMost developers building RAG systems make the same mistake. They split documents by token count, call it "chunking," and move on.The result: a retrieval system that finds the right words in the wrong 00
TStarini sunilinai-content-utilties.hashnode.dev·May 8 · 4 min readWhy Document Parsing Is Harder Than It LooksMost document parsers flatten everything into plain text. But real-world documents are messy: inconsistent headings broken bullet lists repeated sections tables missing structure I wanted to se00
TStarini sunilinai-content-utilties.hashnode.dev·Apr 27 · 7 min readFrom One Shot to a Pipeline: Evolving DOCX → JSON (V1 → V2)Why change what works? A common first version of “turn this Word file into JSON” is simple: read the text, send all of it to the LLM once, parse JSON back. It ships fast and works on small docs. In pr00
