Mr. Ånand

13K posts

Mr. Ånand banner
Mr. Ånand

Mr. Ånand

@Astrodevil_

🥑DevRel | Dev Ambassador → @MiniMax_AI 🧑‍💻Helping DevTools ➝ @Studio1HQ 📤Newsletter ➝ @DailyAI_Insight ⚔️Soon ➝ https://t.co/IVHPpCodNR⚡DM ➝ for Collabs

Jezero Crater, Mars 🇮🇳 Katılım Haziran 2019
597 Takip Edilen2K Takipçiler
Sabitlenmiş Tweet
Mr. Ånand
Mr. Ånand@Astrodevil_·
Nebius just launched Data Lab inside @nebiustf! And I think this is the missing piece in most LLM improvement workflows. Fine-tuning itself is not the hard part anymore. The hard part is the loop: → find useful production logs → isolate failure cases → clean and reshape the data → create a training dataset → run post-training → deploy the improved model → repeat without rebuilding everything That’s exactly what Data Lab is trying to fix. It turns inference logs and existing datasets into reusable training data inside Token Factory. So instead of treating model improvement like a one-time cleanup project, you can run it like a loop: Logs → curated dataset → post-training → better model → redeploy → repeat. I also tested this in my own workflow for: → Dataset preparation → Teacher-student distillation → Data Lab batch inference → LoRA fine-tuning → Serverless adapter deployment → Model comparison with a Gradio app The interesting part is that the workflow stays connected. You are not jumping between random scripts, notebooks, storage exports, training tools, and deployment infra. Data Lab makes the model improvement cycle much faster for production apps.
Mr. Ånand tweet media
English
1
1
0
117
Mr. Ånand
Mr. Ånand@Astrodevil_·
@romanchernin So Nebius is ready to help in that process with open models and Data lab like products?
English
0
0
0
566
Roman Chernin
Roman Chernin@romanchernin·
My [optimistic] thinking: Anthropic’s insane revenue growth and the huge number of tokens it generates show what will happen next with open-source / alternative model tokens. Start with frontier models → grow usage → collect data → tune cheaper models -> get margins.
English
17
27
342
66.1K
Mr. Ånand retweetledi
zR
zR@zRdianjiao·
🚀 GLM-5.1-HighSpeed is live: 400 tokens/s — a new speed ceiling for flagship-tier LLM APIs. Not a smaller model traded for speed. A flagship from @Zai_org that's also the fastest. 📖 Full technical deep-dive 👇 tilert.ai/blog/speed-as-…
GIF
English
43
70
859
57.3K
Sick
Sick@sickdotdev·
My company’s claude account got exhausted. Now my legendary manager is asking if we can build our own LLM like Claude to reduce costs😭
English
932
1.1K
23.3K
875.1K
Mr. Ånand
Mr. Ånand@Astrodevil_·
I just got acquired by @Kalshi for $300K/yr job for next 5 years 🙌
English
1
1
9
580
Rishika Gupta
Rishika Gupta@rishikagupta__·
TIL, Satya Nadella is an engineer from MIT🤯 Manipal Institute of Technology
English
10
1
173
12.7K
Mr. Ånand
Mr. Ånand@Astrodevil_·
Nebius just launched Data Lab inside @nebiustf! And I think this is the missing piece in most LLM improvement workflows. Fine-tuning itself is not the hard part anymore. The hard part is the loop: → find useful production logs → isolate failure cases → clean and reshape the data → create a training dataset → run post-training → deploy the improved model → repeat without rebuilding everything That’s exactly what Data Lab is trying to fix. It turns inference logs and existing datasets into reusable training data inside Token Factory. So instead of treating model improvement like a one-time cleanup project, you can run it like a loop: Logs → curated dataset → post-training → better model → redeploy → repeat. I also tested this in my own workflow for: → Dataset preparation → Teacher-student distillation → Data Lab batch inference → LoRA fine-tuning → Serverless adapter deployment → Model comparison with a Gradio app The interesting part is that the workflow stays connected. You are not jumping between random scripts, notebooks, storage exports, training tools, and deployment infra. Data Lab makes the model improvement cycle much faster for production apps.
Mr. Ånand tweet media
English
1
1
0
117
Mr. Ånand
Mr. Ånand@Astrodevil_·
Most AI teams aren't bottlenecked by training anymore. They're bottlenecked by iteration speed. Production logs contain the best signal for improving your next model → real prompts, real failures, real edge cases. But turning logs into training data still means: → Manual exports → Script-based cleaning → Fragmented workflows → Stale insights by deployment @nebiustf Data Lab closes that gap. Explore inference logs and datasets in one workspace. Filter to what matters. Create reusable datasets. Move directly into post-training. No rebuilding the pipeline each time. S3-connected workflows mean your data stays where it lives. No extra copies, no security review delays. The value isn't one feature. It's the full loop from production insights to better models.
Mr. Ånand tweet media
English
1
1
1
69
Mr. Ånand
Mr. Ånand@Astrodevil_·
Built a quick demo comparing a normal model vs fine-tuned model for insurance claim chatbots. Used @nebiustf Data Lab to close the loop: → Uploaded dataset via Data Lab → Filtered for claim-specific interactions → Created a reusable dataset → Fine-tuned and redeployed The difference in response quality is noticeable. LLM improvement loop for production apps should be easy. Data Lab lets you import inference logs and chat completions from your deployed app LLM as well. This is what the iteration loop looks like in practice 👇
English
2
0
2
111
Mr. Ånand retweetledi
Mr. Ånand
Mr. Ånand@Astrodevil_·
Ever tried building activity logs for your SaaS? Looks dead simple. Log events. Store them. Query them. Ship it. Then you actually start building. First, you need schemas for every event type. Comments, edits, reactions, agent actions. Then user attribution that works across sessions and devices. Oh and agent attribution that tells AI actions apart from humans. Then there's debouncing. Because nobody wants 200 separate log entries when someone rewrites one paragraph. You batch keystrokes into something meaningful. Real-time subscriptions without constantly polling your database. Filtering by org, document, feature, user, agent, time. Immutability so records can't be tampered with. Permission scoping so users only see their allowed stuff. REST API for backend access. Compliance formatting because auditors won't accept "trust me bro." 10 weeks later, you're still building it. What caught my attention about @veltjs? AI agents and humans log the same way. Agent rewrites something? Same record structure as a human edit. Same schema. Same attribution format. This matters more than you'd think. Enterprises won't let AI agents touch production without proof of what happened. Who did what. When. Why. Immutable records that survive an audit. No audit trail? You're running agents blind. Something breaks, and you've got no way to prove what the agent did or didn't do. Velt auto-captures events from their features. Custom events? One function call via createActivity(). setActivityDebounceTime() batches your keystrokes into clean records. getAllActivities() pulls org-wide or document-specific logs. You can enable immutable mode for tamper-proof audit trails that compliance teams trust. The hard part isn't the logging. It's everything underneath: real-time sync, permission layers, compliance formats, agent tracking, and storage that auditors trust. That infrastructure? That's the part that eats quarters. Full docs 👇 docs.velt.dev/async-collabor…
English
0
1
3
116
Mr. Ånand retweetledi
Mr. Ånand
Mr. Ånand@Astrodevil_·
Ever tried running a coding agent locally without shipping your code to third-party APIs? We just did it with @opencode + @Jozu_AI Rapid Inference Containers. Used a 4-bit quantized GGUF of Qwen3.5-9B. The speed difference? Ridiculous. Jozu RIC can serve the model in 42.8 seconds. @nvidia NIM took 239.2 seconds for the same task. That's 5.6x faster 🔥 Here's how it works 👇
Mr. Ånand tweet media
English
2
1
2
336