Michael Fitzke

Building AI to create a better world for pets @MarsGlobal

[Michael Fitzke @ButterKaffee]

@char_bone

[God’s Whisper @GodsWhisper777]

Bremen, Reinsberger Cemetery

[Michael Fitzke @ButterKaffee]

Hiking on Prince of Wales Island in Alaska. Took the photo of that fallen tree right before climbing over it.

[Michael Fitzke @ButterKaffee]

@rohanpaul_ai And those 50 cases are stored where?

[Nando de Freitas @NandoDF]

AI Models are valuable, but datasets and evals to train AI models are more valuable.

Datasets are valuable, but automated data pipelines that generate the datasets are more valuable.

*** Model < data < pipeline ***

At least until the models start building pipelines. Still far and unsafe.

[Michael Fitzke @ButterKaffee]

@giffmana Oh...I counted passes while there was a gorilla around

[Michael Fitzke @ButterKaffee]

@soumithchintala feels like the end of an era! Thank you for all the work you put into pyTorch Soumith! I still remember the bliss touching it for the first time coming from Theano. And thanks for letting Idly be our model for the blogpost we did back in the day :D

[Michael Fitzke @ButterKaffee]

@giffmana I still recommend https://t.co/4d5H7Z4xq9 sometimes for beginners

[gabogabigabu @gabogabigabu]

@syntacrobat &gt; Mom, can we have a type system?
&gt; No, we have a type system at home
The type system at home:
# (B, C, T)

[Michael Fitzke @ButterKaffee]

It's because ZIRP is over

[Boyang "Albert" Li at ICML 2026 @AlbertBoyangLi]

Given the recent drama at Meta FAIR, I was wondering if people would be interested in hearing my opinions on why industrial research is hard. My credential is that all three industrial research labs I worked at have shut their doors. That may or may not have made me an expert😅

[Michael Fitzke @ButterKaffee]

@julianibarz @ylecun What did you plan to use instead of convnets for vision in 2013?

[Braelyn ⛓️ @braelyn_ai]

why are all the most respectable software startups remote-first?

[Sebastian Raschka @rasbt]

DeepSeek finally released a new model and paper. And because this DeepSeek-OCR release is a bit different from what everyone expected, and DeepSeek releases are generally a big deal, I wanted to do a brief explainer of what it is all about.

In short, they explore how vision encoders can improve the efficiency of LLMs in processing and compressing textual information. And the takeaway is that rendering text as images and feeding that to the model results in more efficient compression than working with text directly.

My first intuition was that this sounds very inefficient and shouldn't work as well as using text tokenizers (or alternatives like Byte Latent Transformer) to prepare the input. It actually reminded me of the line of research I saw years ago, where researchers represented 3D molecules as 3D inputs or 2D images for ConvNets instead of using graph neural nets. This shouldn't work well and should be prone to overfitting.

In the case of DeepSeek-OCR, why even try such an approach? I imagine it started as a curiosity, but then it may have turned into an interesting idea for long-context scaling in LLMs and how to make it cheaper by using vision tokens and representations. (An image can say more than a thousand words, but who would have thought that an image of text can say 1000 words more efficiently!)

In any case, this DeepSeek-OCR approach turns out to be surprisingly efficient. In particular, they found that at a fixed  precision of 97% for long-context decoding (i.e., how well the model can compress information into a latent representation and reconstruct it), the OCR version needed 10 times fewer visual tokens than text tokens. In other words, the OCRed version can compress information 10x better than the text version.

How is it different compared to other VLLM architectures?
- They don't use a monolithic ViT as encoder, instead they fuse local and global vision features through a clever 16x convolutional compressor (this can handle high-resolution inputs efficiently in terms of memory and token counts).
- They are (to the best of my knowledge) those who use an MoE as a decoder.
I think it's an interesting, refreshing approach, and the twist here is that it works surprisingly well.
However, I don't think that visual representations of text will solve the limitations of LLMs. Also, while it is popular to dislike text tokenizers like BPE, image representations are messy as well (one has to deal with aspect ratios, resolutions, croppings, color intensity variations, brightness levels, etc.). Still, it’s an interesting idea. Also, if this approach is more efficient than regular black&white text, I am curious to see compression ratios when we add syntax color to code.

Regarding code, this may be an interesting alternative for storing contextual information, as spacing and subword tokenization remain challenges in traditional tokenizers. (Especially when working with code that uses many custom variable names that may not be represented in vocabularies and that have to be broken down into many individual subword tokens.)

Overall, it’s still such an esoteric concept to encode text in images that I am (still) surprised it could do well (and may it would only make sense for very long documents or special domains like OCR or code, not general language modeling).

(PS: Personally, I expected the DeepSeek team to follow up with a V4 model using the sparse attention mechanism they tried in V3.2 recently, but maybe that's still forthcoming. Now, after reading this paper, V4 is perhaps going to be a VLLM.)

[Michael Fitzke @ButterKaffee]

@dileeplearning Which species ?

[Michael Fitzke @ButterKaffee]

@dileeplearning Because you can train that end-to-end

[Anjney Midha @AnjneyMidha]

required reading for anyone who works with computers

[Paul Graham @paulg]

If you make your app 10% easier to use you'll get twice as many users.

[Pedro Domingos @pmddomingos]

Wow! It only takes 2 TB of simulation data to rediscover a few equations!

[Randall Balestriero @randall_balestr]

Should be "what we wish they represent" as this intuition breaks for high-dim. data https://t.co/zqQDtmZvnL + the encoded features are biased from the decoder/rec. loss https://t.co/d38rBsNZ4I. Use joint-embedding instead: https://t.co/geptacEc25 -&gt; recovers the data coordinates

[Michael Fitzke @ButterKaffee]

@DimitrisPapail "Create a tool to count how many r are in strawberrry"

[Dimitris Papailiopoulos @DimitrisPapail]

Every tool is "superhuman", in the specific use cases relative to it. Otherwise we would not use it.