Skip to content
View skat00sh's full-sized avatar
💭
hmm...mehh!
💭
hmm...mehh!

Organizations

@fossasia

Block or report skat00sh

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
skat00sh/README.md

Devendra Vyas

Applied ML engineer. I work with images and multimodal data — computer vision, VLMs, and the messy business of teaching machines to make sense of what they see (and read, and hear).

Munich · vyas.dev · makesnosense.io · LinkedIn


Six years turning research into things that actually run. The constant across all of it: pixels, and everything you can bolt onto them. Classic computer vision, then edge deployment on Jetson / TensorRT, then MLOps that survives production, and lately LLM / RAG / VLM / agentic systems — same throughline, I just kept finding new modalities to feed the models. One peer-reviewed paper I'm genuinely happy about (HiPEAC 2025, on active inference), tech-lead experience on an EU edge-AI project, and a standing suspicion of anything a vendor describes as "just."

I like problems where the data is rich and slightly unruly — images, video, text-and-vision together. The interesting failures live there: a model that's fluent in one modality and clueless the moment you cross into another. Most of applied ML is really about those seams, and I've spent my career happily poking at them.

What I actually do

  • Vision & multimodal — from classic CV pipelines to VLMs: detection, recognition, retrieval, and getting language and images to actually agree on what they're looking at.
  • From lab to the real world — models compressed and quantized until they fit a robot's power budget, then deployed where latency has consequences. The gap between a benchmark and a deployment is where the real work hides.
  • Systems over demos — the interesting part of an ML system is never the model. It's the seam where it meets a messy world and has to pretend it's coping.
  • Explaining hard things — interactive explainers at makesnosense.io: positional encodings you can poke, Kalman filters that stop being scary. Teaching is just debugging your own understanding in public.

🤖 Ask the README

terminal typing animation

A chatbot with no model, no server, and no ambition. Click a question.

> what do you actually work on?
Images and multimodal data, mostly. Computer vision pipelines, VLMs, and the negotiation where language and pixels have to agree on what they're looking at. If it has a camera or a modality mismatch, I'm interested.
> give me a hot take
Most "AI problems" are data problems wearing a model's clothes. The model is rarely the bottleneck; the seam between the model and the real world is.
> are you available for work?
Yes. Hard applied-ML problems with rich visual or multimodal data — Staff / forward-deployed / research-adjacent. Bonus points if there's real hardware involved. Links are at the top.
> convince me in one line
I've spent six years shipping ML that had to survive contact with reality, and I can explain why it worked — which is rarer than it should be.
> is this a real chatbot?
No. It's <details> tags and low cunning. GitHub won't run a model in here. You clicked anyway, though — so it worked.

Anti-hype · first-principles · allergic to the word revolutionary

Pinned Loading

  1. mcmrirecon mcmrirecon Public

    Forked from tum-ri/mcmrirecon

    A project developed as a part of Praktikum Machine Learning in Medical Imaging by our team (TUMRI) at the Technical University of Munich

    Python

  2. linkedin-job-saver linkedin-job-saver Public

    Chrome extension to automate Job Application using n8n

    JavaScript