Devs Debate Why They Avoid Tinker for Post-Training: Cost and Code Ownership

A discussion on X explored why practitioners avoid Thinking Machines' Tinker for post-training: developers cited high costs and the desire to own their post-training code, while defenders argued Tinker still allows full code ownership.

2026-09-22 ~ 2026-09-22 · 3 related posts

• Tinker aims to handle posttraining ML infra for everyone — what's holding users back? — PatrickToulme · 2026-09-22
• Why devs skip Tinker for posttraining: cost and owning your own code — silver__tsuki · 2026-09-22
• cHHillee defends Tinker: you can own your post-training codebase, only trainer and sampler are abstracted — cHHillee · 2026-09-22