Allwell

"Teaching is a humbling and deeply educational experience, and I cannot recommend it enough!" --Jon Gjengset. Thank you, Jon, for giving your time, expertise, and energy to write a masterclass on Idiomatic Rust. I've always admired your knack for teaching and hope to do the same. I just finished studying Rust for Rustaceans by @jonhoo. After studying the Rust Book, like @davidtolnay said in the preface, I noticed a knowledge gap between concepts explored in TRPL (The Rust Programming Language) Book (a.k.a., the Rust Book) and terminology in the std library and Rust Reference. I wanted to close that gap, to truly understand, because I've come to LOVE Rust. I wanted to leave no stone unturned. I found the best 2nd book after the Rust Book (goes without saying, I highly recommend). As advised, in Chapter 13, Jon, I'll learn by teaching too. In the coming days, I'll share blog posts and hopefully hold live sessions where I debunk the myth that "Rust is too hard." Chipping at topics bit by bit. It used to be that if you wanted to learn the inner workings of computer programming that'd tell you to learn C. Today, I'd tell you to learn Rust. Rust teaches you to appreciate the power you wield when you write, build and run a computer program. Yes, it is complex, but "complex is better than complicated." It might take some getting used to, yes, but with time and focus anyone can master the language and that's what I hope to do. PS. Thank you @OReillyMedia for access to a plethora of golden technical resources. Thank you @timoreilly. That's two Rust books in 3 months! Grateful.

I never thought I’d be writing this tweet. I was laid off. For most people that’s a scary moment. For me, it’s a countdown. I’m on a visa. No job means out of status. Out of status means leaving. Leaving means saying goodbye to years of my life, the friends I’ve made, the work I’ve poured myself into, the future I came here to build. And right now, with everything happening around immigration, that goodbye feels closer than ever. I have a CS PhD and have spent years working on AI, ML, deep learning, and computer vision. I’m open to full-time roles, internships, PhD positions, or postdocs. I’ve never asked the internet for help before. I’m asking now. If you can share this, tag a lab or team, or just know someone who’s hiring, please do. A retweet could genuinely change my life. abdollahzakeri.github.io #USCISPause #LiftTheHold #DigitalBlackOutIran‌

@rezoundous Definitely nerfed. I think it's the 2nd of April discount erasure thing

Is it just me, or has Codex usage limits been nerfed?

I don't know who needs to hear this. But no matter what language you are working on. You should definitely learn rust once in your lifetime. It teaches alot tbh. Learning rust makes you a better developer in your language.

@FOjebiyi Amazing work. Well done. And good use of AI.

Hi guys, I built an open-source alternative to @pewbeam_ai in one week. github.com/openbezal/rhema Started coding during a Sunday church service. By the following Sunday, we were using it live during our church service. Wild. Here's what Rhema does: it listens to your pastor's sermon in real-time, detects Bible verse references as they're mentioned, and displays them on screen instantly. No manual clicking, no dedicated slide operator needed. The tech stack: - Tauri 2.0 with a Rust backend handling all the heavy lifting: audio capture, transcription pipeline, verse detection logic, and system tray integration - Local AI embeddings using Qwen3-0.6B so everything runs on-device with zero cloud dependency. Your sermons never leave your machine - Real-time audio transcription paired with semantic search against a full Bible verse database The Rust backend was a deliberate choice. We needed low latency audio processing and efficient memory usage for running an embedding model locally, and Rust delivers on both. Is it perfect? Probably not. But the core functionality works and we're already using it in a real church environment This is where you come in. Rhema is fully open source and we need contributors to help take it to the next level. Whether it's improving the verse detection accuracy, adding multi-language support, building a better overlay UI, adding support for more Bible translations, or optimizing the transcription pipeline, there's real work to be done and real impact to be made. If you're a Rust developer, a frontend engineer, an ML enthusiast, or just someone who loves building tools for the church, come build with us. Star the repo. Fork it. Open a PR. Let's make this the go-to open-source solution for live Bible verse display in churches worldwide. github.com/openbezal/rhema

Judging by my tl there is a growing gap in understanding of AI capability. The first issue I think is around recency and tier of use. I think a lot of people tried the free tier of ChatGPT somewhere last year and allowed it to inform their views on AI a little too much. This is a group of reactions laughing at various quirks of the models, hallucinations, etc. Yes I also saw the viral videos of OpenAI's Advanced Voice mode fumbling simple queries like "should I drive or walk to the carwash". The thing is that these free and old/deprecated models don't reflect the capability in the latest round of state of the art agentic models of this year, especially OpenAI Codex and Claude Code. But that brings me to the second issue. Even if people paid $200/month to use the state of the art models, a lot of the capabilities are relatively "peaky" in highly technical areas. Typical queries around search, writing, advice, etc. are *not* the domain that has made the most noticeable and dramatic strides in capability. Partly, this is due to the technical details of reinforcement learning and its use of verifiable rewards. But partly, it's also because these use cases are not sufficiently prioritized by the companies in their hillclimbing because they don't lead to as much $$$ value. The goldmines are elsewhere, and the focus comes along. So that brings me to the second group of people, who *both* 1) pay for and use the state of the art frontier agentic models (OpenAI Codex / Claude Code) and 2) do so professionally in technical domains like programming, math and research. This group of people is subject to the highest amount of "AI Psychosis" because the recent improvements in these domains as of this year have been nothing short of staggering. When you hand a computer terminal to one of these models, you can now watch them melt programming problems that you'd normally expect to take days/weeks of work. It's this second group of people that assigns a much greater gravity to the capabilities, their slope, and various cyber-related repercussions. TLDR the people in these two groups are speaking past each other. It really is simultaneously the case that OpenAI's free and I think slightly orphaned (?) "Advanced Voice Mode" will fumble the dumbest questions in your Instagram's reels and *at the same time*, OpenAI's highest-tier and paid Codex model will go off for 1 hour to coherently restructure an entire code base, or find and exploit vulnerabilities in computer systems. This part really works and has made dramatic strides because 2 properties: 1) these domains offer explicit reward functions that are verifiable meaning they are easily amenable to reinforcement learning training (e.g. unit tests passed yes or no, in contrast to writing, which is much harder to explicitly judge), but also 2) they are a lot more valuable in b2b settings, meaning that the biggest fraction of the team is focused on improving them. So here we are.

Hot take: Rust might be the best language for vibe-coding. The compiler provides strong feedback and guardrails. And AI thrives on guardrails.

The job board now comes with roadmaps. Because finding the job is only half the journey. 🦀 6 Rust career tracks now live. 🔴 Rust Backend Engineer 🤖 Rust AI Engineer ⚙️ Rust Systems Engineer ⛓️ Rust Web3 Engineer 📟 Rust Embedded Engineer ☁️ Rust Cloud Engineer Each track breaks down into focused modules with curated resources, books, repos, videos, and real projects to build. 👉 Explore it live: rustjobs-one.vercel.app #RustLang #UIDesign #LearningPaths #TechJobs #OpenToCollaborate #SideProject #ProductDesign #RustProgramming #Rust #Programming

A lot is happening in the world. @AnthropicAI finally officially mention Mythos. youtu.be/INGOC6-LLv0?si…

Two cool rules I like in Rust: 1. The Orphan Rule 2. Lifetime Ellision Rules. Did you know the Orphan Rule has exceptions? These exceptions operate for blanket implementations, fundamental types, and covered implementations. These exceptions make up Rust Coherence.

@instablog9ja When I hear such things from women what I say to them is, "keep up this energy when you turn 35."

“Anything shared with a man is not princess treatment, even if he pays all the bills and provides a house and vacations” — lady

@Ajiboye11Tony @Blue_Footy Just because someone is excellent at what he does doesn't mean you should snag at him. Instead you should support him.

@Blue_Footy With this write up, it's understandable if people accuse you of being on the payroll of the club because this write up is totally unnecessary for an 'average' fan to write. and the 'job' should be done by PR consultant hired by the ownership.

✍️ Strasbourg's project excites me a lot. Even more than Chelsea’s project. It's easier to develop players at a mid-table club than at a top club. The talent in that team is crazy. They talk about Chelsea taking their players, but they are not a club that can keep players away from big teams. If Chelsea don't take them, other big teams will. Once they produce a good talent, bigger clubs will circle. How many years was Simakan when they sold him to RB Leipzig before BlueCo takeover? I think the main thing is for them to keep getting top replacements. They are like Brighton, they bring in top potentials but not big enough to keep them long-term. To do that, they will need to pay big wages which is impossible for a club of their size yet. In terms of talent, they're impressive. Yassine, Mourabet, Doue, Nanasi etc. I mean, 70-80% of that squad are international players. It's not something they are used to. And the succession plan has been well planned. Panichelli is replacing Emegha and Oyedeji looks like he will replace Barco pretty much. And they will bring in more players to improve the squad again. I think they are set to become competitive long term, they have a structure to support it. They are getting enough financial support from BlueCo. They are not being fed with crumbs. The only thing they can complain about is their culture being trampled on by BlueCo, but a dying club don't care about all that. Bordeaux will want to be a sister club now just to stabilise again. I keep telling their fans, they are here because their club wasn't doing great financially and was running out of time. No foreign owner will care more about culture than making profit. But at least, on the pitch, they are doing well, better than most teams in a multi-club model in Ligue 1. They will only get better from here. I think they should look at the brighter side. They have a solid project going on there. I love watching them play football.

rust errors: tehee ~~ you made a mistake here 👉👈 small fix 😋 C++ errors:

@_HerDAO @IronClawAI @HERDAOIndia @HerDao_Mexico @HERDAONigeria @herdaoghana @herdaovzla @herdaobali @HERDAO_Kenya @Ewhachain @womenindefi_org Rust is a beautiful PL. I'm happy to be involved.

Tomorrow. We open Rust education scholarships 🦀 Most people don’t fail Rust because it’s hard They fail because they never get the right environment Limited cohort. Beginner → builder pipeline. Real systems training. Not everyone will get in. Details tomorrow!

@rustaceans_rs This one is now gonna battle Diesel ORM.

Toasty, an async ORM for Rust from the Tokio team, is now officially released on crates.io Version 0.3.0 – supports SQL databases like PostgreSQL, MySQL, SQLite, and NoSQL with DynamoDB. #rust #rustlang #programming

@penberg Nice. Will try this with Codex CLI.

I just shipped Swarm 0.1 for herding your agents, not terminals. Coding agents exhibit high latency because they make mistakes and get off track. However, running them in parallel can improve your development throughput by allowing you to tackle multiple problems at once. However, managing a bunch of parallel coding agents is a pain. Every agent needs a copy of the source code, a git branch, and multiple terminals. Before long, you're drowning in tabs with no idea what's running where. I built Swarm to fix that. It's a manager for all your repos, workspaces, and agent sessions, available as a native Linux desktop app powered by Ghostty. Here's how it works. You add a repository (your source code), create workspaces (git worktrees per task), and then open as many terminal sessions as you need in each workspace to run coding agents, development servers, and more. One workspace per feature. One agent per workspace. No more chaos. Works with any coding agent. 🔗 github.com/penberg/swarm

"AI makes everyone a developer" is true the same way "cameras makes everyone a photographer"

Lord Jesus is Alive! Glory to the Lord Jesus forevermore. Happy Easter! ✨️

Finally!

😂😭