Febin John James (@heyfebin) header
Febin John James (@heyfebin) profile picture

Building AIBodh

Bangalore
Joined January 2010
Photo by Febin John James (@heyfebin)Photo by Febin John James (@heyfebin)Photo by Febin John James (@heyfebin)Photo by Febin John James (@heyfebin)Photo by Febin John James (@heyfebin)Photo by Febin John James (@heyfebin)Photo by Febin John James (@heyfebin)Photo by Febin John James (@heyfebin)Photo by Febin John James (@heyfebin)Photo by Febin John James (@heyfebin)
Replying to @Ionkosm
generosity in usage limits
3
Replying to @thsottiaux
falls apart in clean coding practices, things like inline code that's difficult to understand and modify.
10
Replying to @henry_aileron
Need to add email, but you can use rss aibodh.com/feed.xml
1
1
27
Async Rust can be frustrating because the compiler errors feel disconnected from your intent, so you try to fix things without understanding why. Even working code can hang or run out of order at runtime, with no obvious place to begin debugging. This chapter guides you to build the state machine behind an async fn by hand, then uses that as a model to reason about common async bugs and compiler errors. aibodh.com/posts/async-rust-…
1
10
3,033
Async Rust can be frustrating because the compiler errors feel disconnected from your intent, so you try to fix things without understanding why. Even working code can hang or run out of order at runtime, with no obvious place to begin debugging. This chapter guides you to build the state machine behind an async fn by hand, then uses that as a model to reason about common async bugs and compiler errors. aibodh.com/posts/async-rust-…
1
1
293
Febin John James retweeted
At OpenAI, we're continuing to bet on Rust as the future of systems programming. I'm proud to announce that we're making a $600,000 commitment to the Rust Foundation, which combines our Platinum membership with additional support for maintainer efforts across the Rust ecosystem.
147
251
70
4,804
643,404
Great hands-on intro to async Rust by @heyfebin 🦀 It answers the question most tutorials skip: who actually runs async code in Rust? The answer is built from scratch : a oneshot channel, a waker, a block_on runner, using nothing but std. No Tokio yet. Just the raw primitives. Once every piece is understood, reaching for Tokio feels natural, nothing is magic anymore. Chapter 1 covers: → Why Rust ships no event loop (unlike Node) → What polling actually does → How Waker signals when to poll again → Building a oneshot channel from scratch 🔗 aibodh.com/posts/async-rust-… #Rust #RustLang #AsyncRust #Tokio #LearnRust
3
16
1
118
6,464
Bevy Game Engine Explained Visually aibodh.com/posts/bevy-game-e…
1
1
7
4,754
Replying to @claudeai @SpaceX
This is rate limits, not usage limits, the total weekly allowance hasn't changed, you just get faster access to the same quota. The "Higher usage limits" framing is misleading.
56
The Impatient Programmer's Guide to Bevy and Rust: Chapter 12 - Let There Be Networking By the end of this chapter, you'll learn to: - Understand how multiplayer games actually work under the hood, the four systems every online game needs (identity, persistence, real-time sync, and server authority). - See why SpacetimeDB is a fundamentally different approach: instead of stitching together a web server, a database, a WebSocket layer, and an auth system, you write one Rust module. - Set up SpacetimeDB locally, publish your first server module. - Implement the server side: a player table that stores who exists in your world, and reducers that automatically handle players joining, leaving, and coming back. - Connect your Bevy game to the server so that clicking Multiplayer opens a live connection screen showing your player name and who else is currently online. - Run two instances of your game side by side and watch them recognize each other as separate players on the same shared server. aibodh.com/posts/bevy-rust-g…
1
1
8
3,774
Febin John James retweeted
Replying to @airtable
@airtable is rewriting their database in Rust 🦀 #rust #rustlang #programming
4
6
2
92
3,009
Febin John James retweeted
“Rust slows me down.” So does thinking.
4
2
38
1,477
Febin John James retweeted
Writing Rust feels slow until you realize you’re not debugging in prod.
8
7
3
83
3,193
Febin John James retweeted
Replying to @robustus
Code itself will go away in favor of just making the binary directly. The next step after that is direct, real-time pixel generation by the neural net.
910
615
373
7,286
1,410,359
Febin John James retweeted
Being able to click the Grok button and instantly have a tweet explained in its full context is just wildly cool technology
471
599
119
22,740
2,254,114
Continuing my Bevy + Rust tutorial series. Chapter 7 - Let There Be Enemies Learn to build intelligent enemies that hunt and attack the player using A* pathfinding and AI behavior systems. By the end of this chapter, you'll learn: - Implement A* pathfinding for enemies to navigate around obstacles - Reuse player systems for enemies (movement, animation, combat) - Build AI behaviors aibodh.com/posts/bevy-rust-g…
9
1,671
Febin John James retweeted
Introducing Claude Opus 4.6. Our smartest model got an upgrade. Opus 4.6 plans more carefully, sustains agentic tasks for longer, operates reliably in massive codebases, and catches its own mistakes. It’s also our first Opus-class model with 1M token context in beta.
1,657
4,615
2,897
38,581
10,630,744
Replying to @sama
"something so clearly dishonest", "our most important principle for ads says that we won't do exactly this" You had ONE principle important enough to put in your company name. You see where the distrust comes from.
32
Febin John James retweeted
The older seasons of Star Trek were a positive view of the future
Hollywood convinced generations of a dystopian future because happiness was too boring for movies.  We need better storytellers to show how our future will be abundant.
4,532
5,154
415
74,394
30,973,221
Febin John James retweeted
Vibe coding is the creation of large quantities of complex AI-generated code. Executives push lay-offs claiming AI can handle the work. Managers pressure employees to meet quotas of how much of their code must be AI-generated... yet results are far from what was promised 1/
25
82
20
623
141,579