Engineering Lead | Technical Architect | Full-Stack | AWS | MERN | Node.js | React.js | Typescript | GraphQl | MongoDB | MySQL| PostgreSQL |
I am a dedicated and goal-driven Lead full-stack developer/architecture with over 15 years of experience in leading and designing web application. My expertise spans both front-end, where I specialize in technologies like React/Redux, jQuery, Bootstrap, CSS, and HTML5, and back-end, where I work with AWS, Node.js, Express, and MongoDB. In my approach to web architecture, I prioritize simplicity, efficiency, and resilience, with a keen interest in developing interactive products that seamlessly handle errors and ensure uninterrupted performance. I constantly strive to improve my skills and stay updated with the latest advancements in the field.
Markdown supported · ⌘↵ to post
Kartik N V J K
The detail that tokens carry leading spaces (" like" vs "like") is one people almost never notice until their token counts stop matching their word counts. Worth adding that this is also why the same string can cost different amounts across models, since each tokenizer has its own vocab and merge rules. Do you plan to cover how embedding dimensionality trades off retrieval quality against index size in a follow-up?