Mingzhen Lin

𝗧𝗵𝗲 𝗯𝗲𝘀𝘁 𝗔𝗜 𝗰𝗼𝗱𝗶𝗻𝗴 𝗹𝗲𝘀𝘀𝗼𝗻 𝗰𝗼𝘀𝘁 𝗼𝘂𝗿 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 $𝟲𝟬𝟬 𝗮𝗻𝗱 𝗮 𝗺𝗮𝗿𝗿𝗶𝗮𝗴𝗲 𝗮𝗿𝗴𝘂𝗺𝗲𝗻𝘁. Our VP of Engineering, Xiaofan(James) Luan, was supposed to buy his wife a Dior bag for their anniversary.  Instead, he bought three Claude Code subscriptions and spent the holiday trying to cross-compile 2 million lines of C++. Every fix on one platform broke two others.  $600 later, the only output was "git reset --hard" — and a very cold dinner table.😂 "Make it compile on Windows" is a trap. The real goal was "compile everywhere without hacks" — no AI is going to figure that out for you at 2 am. What worked: constraints before code, review tests not code, bottom-up, one layer at a time. Same task, two days. Then he ran six parallel Claude sessions across three machines with git worktree. The bottleneck stopped being intelligence and started being how fast one person can alt-tab. AI solves exactly the problem you give it. Engineering is in knowing which one to give. His wife is still waiting for that bag. Full story: https://lnkd.in/gtsW_Wvk ——— Follow Milvus, created by Zilliz, for everything related to unstructured data

9

Most existing #lean4 datasets contain only correct proofs. Models learn error correction with RL, that's expensive. With UW Math AI lab we release a dataset of 260k erroneous Lean proofs with - compiler feedback - reasoning trace - corrected proof Improvements in Error Correction: - Goedel 8B: 2x - Kimina 8B: 3x Paper: https://lnkd.in/gaybt4bd

117

2 Comments

We (w/ Shansan Gong, Ruixiang ZHANG, Huangjie Zheng, Jiatao Gu, Navdeep Jaitly, Lingpeng Kong) released a family of 7B diffusion language models, DiffuCoder, that specializes on code generation, with a focus on understanding and improving masked diffusion models. A core analysis of DiffuCoder is the autoregressiveness (AR-ness) score, a novel metric that quantifies the causal patterns in decoding, revealing how diffusion models break from strict left-to-right generation for more flexible, non-linear code planning. Recent advances in autoregressive (AR) models dominate code generation, but diffusion-based LLMs (dLLMs) like DiffuCoder offer a promising alternative, especially for complex programming tasks. DiffuCoder explores how these models decode differently—showing less global AR-ness in code tasks compared to math—and how temperature affects both token selection and generation order, unlike traditional AR models. We also introduce coupled-GRPO, a post-training RL method with a coupled-sampling scheme, to reduce performance drops during accelerated decoding, boosting parallelism and efficiency. We use a self-improvement pipeline that leverages AR-ness analysis, coupled-GRPO optimization, and evaluation on benchmarks like AceCode-89k to refine decoding strategies. This approach enables DiffuCoder to navigate diverse code generation pathways and enhance performance with modest computational overhead. Looking ahead, we aim to further leverage Reinforcement Learning to steer code generation through these decoding patterns, with the discrete nature of AR-ness scores providing a foundation for search-based strategies—ideal for the sparse rewards of optimizing complex code structures. Check out our full paper and code for a deeper dive! Paper: https://lnkd.in/gVWU3BDJ Code: https://lnkd.in/gmXTZ_6n Models: https://lnkd.in/gTcKCDr9 #MachineLearning #AI #CodeGeneration #DiffusionModels #NLP

220

5 Comments

# Modul 5 : Data platform Analytics Engineering with Bruin (Local / DuckDB) I built a complete, production-style analytics pipeline locally using Bruin + DuckDB Key learnings & skills: • I designed a multi-layer data pipeline: ingestion → staging → reports • I Ingested raw NYC Taxi data (Parquet + CSV seed) into DuckDB • I built incremental models using time_interval • I defined dependencies correctly between assets • Implemented data quality checks (not null, unique, non-negative) • Debugged real-world issues: - YAML parsing errors - Missing refs - DuckDB file locks (solved via single-worker execution) • I Validated outputs using SQL: - row counts - date ranges - reconciliation between staging and reporting layers • I Queried and inspected tables via information_schema This hands-on work really highlighted the difference between writing SQL and engineering reliable data pipelines. here the link: https://lnkd.in/epRpYsjF What’s next – Part 5: Deploy to Cloud • Deploy the Bruin pipeline to a cloud data warehouse • Replace DuckDB with a cloud backend (e.g. BigQuery) • Configure cloud connections & environments • Run the same pipeline at scale • Prepare the pipeline for production usage • Understand cost, performance, and orchestration considerations #JustBeDataEngineer #AnalyticsEngineering #Bruin #DuckDB #DataPipelines #Zoomcamp_2026

3

1 Comment

👉 My Key Takeaways from Chip Huyen's Recent Interview on Lenny's Podcast Chip Huyen is the author of the widely recognized "AI Engineering: Building Applications with Foundation Models". Link to the podcast: https://lnkd.in/dxZ-tFWX 💡 Importance of post-training.  Pre-training gives you raw capabilities (next token prediction on massive data), but post-training is what makes the model actually usable. SFT on high-quality examples + RLHF. Fine-tuning should be your last resort, not first. Most problems can be solved with better prompts, better data, or RAG. 💡 Evals.  You can't improve what you can't measure. Need multiple types: unit tests (does this specific prompt work?), integration tests (does the whole pipeline work?), regression tests (did we break something?), and user feedback loops. The hardest part isn't writing evals; it's maintaining them as your product evolves. 💡AI products.  Reliability and UX matter more than models. Most AI product failures aren't about bad models: they're about reliability (API limits, latency spikes, poor monitoring) and UX (users don't understand how to use it, doesn't fit workflow). Building reliable platforms and talking to users constantly beats chasing SOTA models. Most insights come from watching users, not from benchmarks. 💡How to improve AI-powered apps.  What people think improves apps: staying current on AI news, chasing newest agentic framework, obsessing over vector database choice, constantly evaluating model benchmarks, fine-tuning models. What actually improves apps: talking to users, building reliable platforms, preparing better data, optimizing end-to-end workflows, writing better prompts. Better prompt engineering beats switching models 90% of the time. A well-crafted system prompt, clear instructions, good examples (few-shot), and proper output formatting can transform a mediocre experience into a great one. 💡 Advice for builders.  Start with user problem, not with cool AI technique. Use the simplest solution that works (often that's a good prompt, not a fine-tuned model). Build evals early. Focus on end-to-end experience. Don't fine-tune unless you've exhausted everything else. Don't treat AI as deterministic (it's not, you need to handle variability). Don't ignore data quality (garbage in, garbage out).

1

1 Comment

Just arXived: MUSTAFAR – Promoting Unstructured Sparsity for KV Cache Pruning in LLM Inference How do we shrink the memory-hogging key-value cache in large language models—without fine-tuning or accuracy degredation? Meet MUSTAFAR, our new end-to-end system that: 🔍 Prunes at the finest granularity with per-token magnitude-based unstructured sparsity: up to 70% pruning on both Key & Value caches with negligible quality drop. Notably, we can prune the Value cache (something structured methods can’t do) to very high sparsity! 📦 Compresses the resulting sparse cache into a bitmap-based format, packing the cache down to 45% of its original size. ⚡️ Accelerates decode-time attention via a custom sparse attention kernel, boosting tokens/sec throughput by up to 2.23× over dense inference. 🛠️ Integrates with orthogonal methods like token eviction and quantization for even richer compression. 👉 Check out the preprint & code: Paper: https://lnkd.in/eXeA99EZ Code & Kernel: https://lnkd.in/eZ9fyQP9 Huge thanks to my co-authors Helya Hosseini, Ramyad Hadidi and advisor Bahar Asgari for her guidance and insights 🚀

85

2 Comments