HN user

fabmilo

79 karma

I am interested in helping software development teams and individuals turn plain-language specifications into production-ready code using AI. My expertise bridges the gap between intent and implementation, accelerating software development.

Posts3
Comments74
View on HN

Location: San Francisco, CA, USA Remote: Yes Willing to relocate: No

Technologies: Python, Go, TypeScript, PyTorch

Linkedin: http://www.linkedin.com/in/fabmilo

Hi, I’m Fabrizio Milo, a senior AI/ML engineer, large-scale systems architect, and former technical co-founder. I’ve spent my career building production AI, ML infrastructure, and high-scale backend systems across startups and growth-stage companies.

Most recently, I’ve been building AI platforms for LLM training and fine-tuning, RAG databases, local and remote LLM inference, semantic retrieval, and agentic orchestration for business intelligence and code generation. I’ve also contributed to open source ML projects including GPT-Neo, TensorFlow and published research on synthetic data from LLMs.

Previously, I was VP of Technology at ZELIG, where I led the virtual try-on AI research roadmap and managed a cross-functional team building ML/3D systems for fashion retail. Before that, I was Head of Machine Learning Engineering at Recurrency, where I hired and led a 6-person ML/platform team and shipped demand forecasting, dynamic pricing, and recommendation systems on AWS/Snowflake/SageMaker. I also co-founded Passio, where I built the technical foundation for an on-device Nutrition-AI SDK with real-time computer vision inference.

Earlier in my career, I built scalable systems at TheRealReal and Scopely, optimized CUDA kernels at NVIDIA, and worked on real-time market-data and high-performance systems. I’m strongest where AI research, production engineering, and startup execution meet: taking ambiguous technical/product goals and turning them into shipped systems, teams, and infrastructure.

I can architect and build anything you need given enough compute and time.

Why I Write (1946) 3 months ago

Writing it thinking. We developed our brain together with our hands. It feels slow but is actually faster for the end goal.

I am fascinated by this example of using AI to improve AI. I won a small prize using this technique on helion kernels at a pytorch hackathon in SF.

The next step are: - give the agent the whole deep learning literature research and do tree search over the various ideas that have been proposed in the past. - have some distributed notepad that any of these agents can read and improve upon.

Very impressive work from Waymo. The driving with a tornado in the horizon example kind of struck my imagination, many people actually panic in such scenarios. I wonder though the compute requirements to run these simulations and producing so many data points.

because of the principle: you only understand what you can create. You think you know something until you have to re-create it from scratch.

Claude Sonnet 4.5 10 months ago

Yeah I totally agree, we need time to completion of each step and the number of steps, sizes of prompts, number of tools, ... and better visualization of each run and break down based on the difficulty of the task

The AI coding trap 10 months ago

one axis that is missing from the discussion is how fast they are improving. We need ~35 years to get a senior software engineer (from birth to education to experience). These things are not even 3.5 years old. I am very interested in this space, if you are too dm me on X:@fabmilo I am in SF.

I like zotero, I started vibe coding some integration for my workflow, the project is a bit clunky to build and iterate the development specially with gemini & claude. But I think that is the direction to take instead of reinvent from scratch something

I read the paper and the results don't really convince me that is the case. But the problem still remains of being able to use information from different part of the model without squishing it to a single value with the softmax.

We have to move past tokenization for the next leap in capabilities. All this work done on tokens, specially in the RL optimization contest, is just local optimization alchemy.

DeepSeek-R1 2 years ago

was genuinely excited when I read this but the github repo does not have any code.

Thanks to make this open source! Doesn't seem to have any AI enabled search feature does it? Honestly I think you gave up too early, there are solid foundations in the app but definitely needs some more polishing for practical use. I managed to build it on my mac. npm install, npm run tauri build. What is your workflow to add features / debug?

from my understanding that is what they do, see the paper: > We use a pre-trained GPT-2 (Radford et al., 2019) as the base model for all experiments. I agree the feedback is necessary, and the mechanism simple and cheap, but I don't think is optimal.