filtra.io

31 Mar

CUDA, CUDA, CUDA... What if there was a different, open way to write highly-efficient GPU kernels? This is the big swing that Tracel AI is taking. And, guess what... Rust is key to their approach. Check out our podcast with Tracel CEO Nathaniel Simard (linked below):

filtra.io/rust/intervi...

1 Apr

Rust's error messages are still unrivaled.

filtra.iofiltra.io | Breaking The AI Infra Monopoly With Rust- Tracel AIA filtra.io interview featuring Tracel AI.

26 Mar

What are things that software engineers think are really important that just aren't when you zoom out?

25 Mar

Is there such a thing as artisanal software? If so, what does it looks like? Examples? Artisanal: products made by hand or using traditional, non-mechanized methods by a skilled craftsperson, typically in small batches

24 Mar

If LLMs are good at translating from one programming language to another (I think they are), then we should be seeing less programming language-specific requirements in software engineering job postings. For those in the job hunt, does this match what you're seeing?

24 Mar

Seems like we need to figure out continual learning for the next step of AI... The fact that SOTA is models built in Python is a big barrier to getting this done since Python is not highly cross-platform. Does anyone know of a language that might be good for this...? 🦀😉

I've been really impressed with Agent Skills as a way to extend the functionality of coding agents. So, I had a thought... A community led and maintained skill for writing Rust. 🧵

I also think something like this could further Rust adoption if it proved highly effective. I should also note that I have been searching and seen some smaller, fragmented attempts at this.

One last thought on this. Over time, I think you could make this even better by making specific skills or maybe sub-skills for specific Rust use cases like safety critical.

I've been really impressed with Agent Skills as a way to extend the functionality of coding agents. So, I had a thought... A community led and maintained skill for writing Rust. 🧵

There is so much tribal knowledge about writing Rust that I think could be brought together to dramatically improve agents. One of the big advantages of Rust is that it is a language that DOES tend to have a canonical way to do things. A skill could extend that advantage.

I'm very intrigued by OpenCode for one reason: Ability to switch models quickly without relearning the whole tool. For those that are using it, has they delivered on this value prop? Or, are you still reworking your workflow when swapping models?

Rust is exploding in the defense space. Is that just because of expanding defense budgets? What other factors are at play here?

Are you guys writing specs for your agents to code from? How are you doing it? - I assume it's markdown - Is it multiple files? If so, what is each file for? - Is there a standard name you always give the file? Or a naming convention? - Where do the files live?

If you are primarily editing files with a CLI-based agent (Claude Code, Codex, etc.), how are you reviewing the files? In an editor or just right in the terminal with vim or something else lightweight?

Why do people like Zig over Rust? Is it more of a reaction to a certain culture that exists around Rust than to the technology itself?

Most commentary about the usefulness of coding agents seems to center around web, mobile, etc... Are the agents similarly effective in real world domains? (embedded, robotics, aerospace, etc.) If not, why not? Please repost for reach and @ mention those who might have insight!

You might want to unfollow us... Our content has always been very Rust focused. We love Rust. Beyond the language, we love the Rust community. And, our highest purpose has always been to help those in the community find ways to support their families through rewarding work. 🧵

Above all, this change in focus comes from an understanding that some in our community are incredibly anxious in this moment. If this is you, know that I feel a ton of empathy for you. But, we all have to keep stumbling forward with whatever information we have.

So, let's wade through the uncertainty together! We hope you'll stay for this, but if this isn't what you signed up for, no hard feelings : ) - Drew

What is clear is that the ground is moving beneath our feet. Anything we say about Rust in particular is less helpful to our community than what light we might be able to shed on the path forward by asking good questions about the future.

So, we will continue to post about Rust, and our focus will continue to be on you- this amazing group of Rustaceans that have rallied around filtra. But, we will also focus our attention on asking questions about your (and our) future in the age of AI.

We think it is very clear that AI is shifting the landscape for our community in a way that eclipses any conversations about Rust.

To be clear, we don't know whether AI will increase or decrease demand for software engineers. We don't know whether we should all be getting even better at writing code or becoming product generalists. We, like you, have virtually no answers.

23 Feb

AI Code Review Is A New, Discrete Skill We have to learn to discern when we have to understand a snippet of AI generated code deeply and when we don't. - Bit of UI code that behaves how it should? -> Skim - Password salt and hash-> CHECK IT Agree?

21 Feb

Elon said Rust is pretty great. Rust people on X:

20 Feb

I always thought the Rust haters were grizzled C/C++ vets who couldn't be bothered changing because they had expelled memory leaks out of their very being many years ago. Now I'm starting to see that a lot of them are just as zealous as the RIIR crowd.

20 Feb

Help me write questions for our next podcast interview! What questions or thoughts do you have about the intersection of AI and Rust?

Why is Rust such a big deal for robotics? Carter Schultz of @ampsortation.bsky.social explained this to me in a very clear way when we talked. Check out the interview linked in the comments!

filtra.io/rust/intervi...

filtra.iofiltra.io | How Rust Could Change RoboticsA filtra.io Rust interview.

January '26 Rust Jobs Report just dropped! Highlights: - Privacy company Proton cracks top 10 hirers - IOT/Robotics/Automotive finally takes its rightful place as largest Rust hiring industry Check out the full report linked in the comments!

filtra.io/rust/jobs-re...

filtra.iofiltra.io | Rust Jobs Report - January 2026The January 2026 Rust Jobs Report

17 Feb

Ignore every AI headline. Many of us are breathlessly following every development. It's keeping us from the daily blocking and tackling that actually moves the needle in our lives. Learn the state of the art for a couple of concentrated days every quarter. That's all you need.

13 Feb

If you write code in 2026, it seems there are two ways forward for your career: 1. Learn how to build a whole product (learn about design and business). 2. Learn even more about the deep tech details. Which way are you going?

Are you Rustmaxxing?

Been working on learning how to wield the term "mog." So, let's give this a shot... Fair to say Rust mogs C?

STOP SPAMMING YOUR RESUME TO RANDOM JOBS! Instead, think like the hirer. Q: What is a hirer's greatest fear? A: Hiring a poor fit, or worse, someone dishonest. To get hired, think about providing off-resume evidence of capability and character. Here are some ideas: 🧵

Bonus points if you can get one of these done: - Contribute meaningfully to an open source project the company maintains or cares about - Volunteer on advisory boards or similar in your chosen industry

The goal is that when you do actually apply to a job you know who's on the other side of the web form, and you know that they're looking for your resume in the stack.

1. Before anything else, work your network. Who already knows and trusts you? Nepotism exists because of familial love, but also because family members are a known entity. Use this instead of complaining. Contact: - Family - Friends - Former coworkers and clients - Etc

2. Use social media to expand your network for free. - DON'T spam connection requests or DMs - Post content relevant to your interests - Engage thoughtfully with others - DM and get to know everyone that follows you.

filtra.io reposted

Chris Benson

@chrisbenson.bsky.social

practicalai.fmPractical AI | Deep learning in Rust with Burn 🔥It seems like everyone is interested in Rust these days. Even the most popular Python linter, Ruff, isn’t written in Python! It’s written in Rust. But what is the state of training or inferencing d...

@rustcodepro.bsky.social and @filtra.bsky.social -> you might be interested in the interview we did with Nathaniel Simard, creator of Burn, on @practicalai.bsky.social practicalai.fm/242

If you DON'T code for several hours every day, you probably like coding with AI. I'm looking at you C-Suite types and podcasters. (Also me to be fair) If you DO code a lot, you probably don't like using AI. That seems to be the way this debate is breaking.

I think this makes sense. People that code a lot tend to mostly be in one stack and project where they know the syntax and architecture extremely well and can just flow through solving problems. For the rest of us, having a helper is awesome. Seem true to you?

The whole git adopting Rust thing seemed to bring out an ugly side of conversations about the Rust community. No idea why. But, some unsolicited thoughts: 🧵

The fact that people who find other technical communities not inclusive find the Rust community inclusive is a good thing. More brains building the ecosystem advances software correctness.

At the same time, to the extent that the community ever becomes a tool for advancing a particular worldview other than "software correctness good", we do actually shrink the overall community and detract from software correctness.

The whole git adopting Rust thing seemed to bring out an ugly side of conversations about the Rust community. No idea why. But, some unsolicited thoughts: 🧵

Rust is a programming language apparently aimed at increasing software correctness. To the extent that the Rust community should have a collective worldview at all, that worldview should be very focused on advancing software correctness.