← All episodes

AI Repo: codecrafters-io/build-your-own-x

2026-07-16

## Episode Summary In this episode, we cover: - **AI Repo: codecrafters-io/build-your-own-x** (GitHub Trending) - [Read more](https://github.com/codecrafters-io/build-your-own-x) - **AI Repo: apache/ossie** (GitHub Trending) - [Read more](https://github.com/apache/ossie) - **AI Repo: HKUDS/OpenHarness** (GitHub Trending) - [Read more](https://github.com/HKUDS/OpenHarness) - **AI Repo: thinking-machines-lab/tinker-cookbook** (GitHub Trending) - [Read more](https://github.com/thinking-machines-lab/tinker-cookbook) - **AI Repo: jrouwe/JoltPhysics** (GitHub Trending) - [Read more](https://github.com/jrouwe/JoltPhysics) --- *Sponsored by LimitLess AI*

Full transcript

Skyler: Hey everyone, welcome back to Git News A I, the show where we dig through the hottest trending repositories on GitHub so you don't have to. Quick shoutout to our sponsor LimitLess A I — more on them at the end of the episode. Today we've got a really interesting mix — we're talking about a legendary learning resource, a semantic data standardization project, an open agent harness, a post-training cookbook, and yes, even a physics engine that's making waves in the A I world. Let's get into it. Skyler: Alright, kicking things off with an absolute behemoth — codecrafters-io's build-your-own-x. If you've been anywhere near the GitHub trending page in the last few years, you've seen this one. Five hundred and twenty-six thousand stars. That's not a typo. This repository is essentially a curated collection of tutorials and guides for rebuilding popular technologies completely from scratch. We're talking build your own Git, build your own Docker, build your own database, your own web server — the list goes on and on. Skyler: Now why is this showing up on a A I focused podcast? Well, the recent activity that caught my eye was a pull request fixing an anchor link specifically in the A I model section. Which tells us that this repo now has a dedicated A I model building section, and people are actively maintaining it. That's exciting because the philosophy of building from scratch is honestly one of the best ways to deeply understand how these systems work under the hood. Skyler: If you're an M L engineer who's been slapping together Hugging Face pipelines without really understanding what's happening inside a transformer — no judgment, we've all been there — this repo is your ticket to actually grokking the fundamentals. The whole project is written in Markdown, so it's purely documentation and curated links to hands-on tutorials across tons of different languages. It's language agnostic, which is huge. Skyler: Seriously, whether you're a junior developer trying to level up or a senior engineer who wants to shore up your foundations, build-your-own-x belongs in your bookmarks. Check the show notes for the link. Skyler: Next up, let's talk about something a little more niche but honestly really important for the enterprise A I space — Apache Ossie. This one sits at just under nine hundred stars right now, so it's early days, but the concept is really compelling. Ossie is an industry-wide specification effort to standardize how semantic metadata gets exchanged across analytics, A I, and B I platforms. Skyler: Okay so let me break that down a little bit. Imagine you've got a data warehouse team, an A I team, and a business intelligence team all working in the same organization. They're all talking about the same data — customers, revenue, products — but they're each defining that data in slightly different ways in their own tools. That creates this massive headache where you have inconsistent definitions, duplicated logic, and nobody can agree on what the single source of truth actually is. Skyler: That's exactly the problem Ossie is trying to solve. It wants to be a vendor-neutral, standardized way to define and share semantic metadata so that everyone — your dbt models, your A I pipelines, your Tableau dashboards — they're all working from the same definitions. Recent activity includes fixes to their dbt converter and pytest setup, which tells me they're actively building out integrations with the modern data stack. Skyler: The fact that this is under the Apache umbrella gives it some serious institutional weight. This isn't just some weekend project. If you're a data engineer, an analytics engineer, or you're building A I systems that need to consume business data at scale, Ossie is absolutely worth keeping an eye on. It's written in Python, so the barrier to contributing is relatively low. Check the show notes for the link. Skyler: Moving right along — let's talk about OpenHarness from H K U D S. This one has nearly fifteen thousand stars and it's a really fascinating project. The full name is Open Agent Harness, and it comes bundled with a built-in personal agent called Ohmo. I love that name by the way — Ohmo. Skyler: So what exactly is an agent harness? Think of it like a testing and evaluation framework, but specifically designed for A I agents. If you've been building with L L M based agents — whether that's using LangChain, AutoGen, or rolling your own — you know that evaluating agent performance is genuinely hard. Like, how do you know if your agent is actually doing the right thing across a wide variety of tasks? How do you benchmark it? How do you stress test it? Skyler: That's where OpenHarness comes in. It provides a structured environment for running, testing, and evaluating agents consistently. And the inclusion of Ohmo as a built-in personal agent is interesting — it suggests this isn't just an abstract framework. There's a real working agent baked in that you can use as a reference implementation or even use directly. Skyler: It's written in Python, which makes total sense for the agent and L L M ecosystem. Now I do want to flag that there haven't been recent commits, so it might be in a bit of a quiet period. That said, fifteen thousand stars is nothing to sneeze at, and it's worth exploring if agent evaluation is part of your workflow. If you're building production A I agents and you're not thinking about harnesses and evaluation frameworks, you absolutely should be. Check the show notes for the link. Skyler: Okay, repository number four — thinking-machines-lab's tinker-cookbook. This one has around thirty-seven hundred stars and it's all about post-training with Tinker. Now post-training is one of those areas that has exploded in importance as L L Ms have matured. Pre-training is incredibly expensive and mostly done by the big labs, but post-training — fine-tuning, instruction tuning, reinforcement learning from human feedback, reasoning alignment — that's where a lot of the real innovation is happening at the community level. Skyler: The tinker-cookbook appears to be a collection of recipes — hence the cookbook name — for post-training workflows. And the recent activity is super telling. They just updated reasoning-effort presets to match a release mapping, and they're scaling the default max tokens based on reasoning effort level. That tells me this project is actively thinking about how to control and tune reasoning capabilities in models, which is very much at the cutting edge right now. Skyler: This kind of granular control over reasoning effort is something you see in frontier models, and the fact that an open-source cookbook is implementing similar concepts is genuinely exciting. If you're doing any kind of model fine-tuning or you want to experiment with post-training techniques without starting from absolute zero, this cookbook could save you a ton of time. Skyler: It's Python, it's actively maintained, and the focus on reasoning is super relevant given where the field is heading. M L engineers and researchers who are in the fine-tuning space — this one's definitely for you. Check the show notes for the link. Skyler: And our final repository today is a bit of a wildcard — jrouwe's Jolt Physics. Now hear me out before you skip ahead. Jolt is a multi-core friendly rigid body physics and collision detection library written in C++. It's been used in games like Horizon Forbidden West and Death Stranding 2. So why is it on a A I podcast with a seventy percent A I relevance score? Skyler: Here's the thing — physics simulation is becoming increasingly important in A I, specifically in the context of training robotics models and building simulation environments for reinforcement learning. If you want to train a robot to walk, pick up objects, or navigate a physical space, you need a physics engine. And not just any physics engine — you need one that's fast, accurate, and can run in parallel across multiple cores because you're often running thousands of simulation instances simultaneously. Skyler: Jolt Physics checks those boxes. It's multi-core friendly by design, it's highly performant, it's battle-tested in AAA games, and it has a really active community — nearly eleven thousand stars. The recent activity shows they're continuing to refine numerical precision with tolerance fixes and they're adding new projects to their showcase, including something called Lumina Engine. Skyler: If you're working in robotics simulation, if you're building synthetic data pipelines for physical A I, or if you're doing reinforcement learning in simulated environments, Jolt Physics is absolutely worth evaluating as your underlying physics layer. The C++ barrier might be a concern for Python-first M L folks, but there are bindings available. Check the show notes for the link. Skyler: And that's a wrap on today's repositories! Huge thank you to our sponsor LimitLess A I for making this show possible — seriously go check them out, they're doing some really cool stuff in the A I productivity space. If you found today's episode useful, please subscribe wherever you get your podcasts, leave us a review if you're feeling generous, and all the repository links we talked about today are waiting for you in the show notes. I'm Skyler, and I'll catch you in the next one — keep building cool stuff.
Ada Podcasts · Daily AI, silicon, and markets — brought to you by Ada, Ago Consulting, and Zen Semiconductor. · Advertise with us