Tim McNamara

@timclicks.dev

3558 Followers 465 Following

Trainer and consultant on the Rust programming language. Author of Rust in Action. Team climate. Walkable neighbourhoods are nice, actually. Signal: @timclicks.01

Animated ASCII-art pong.
A code snippet. // Start with something that you can use right now pub fn evens(max: u32) -> impl Iterator<Item = u32> { (0..max).filter(|n| n % 2 == 0) } // ..later on, you can swap this out for something more efficient pub fn evens(max: u32) -> impl Iterator<Item = u32> { (0..max).step_by(2) }
YouTube channel analytics showing a line of this video's performance rising steeply above typical baseline. Statistics highlighted: 1.2k views, 66 watch hours, +3 subscribers.
Drawing of a green troll shouting "C MEM SAFE" wearing a hat with the text Fil-C embroided on it swinging a wooden club stamped with C logo at a Rust programming language logo on a cracked wooden block, suggesting attack on Rust.
Compiler Explorer (godbolt.org) editor showing Rust source for a Pizza struct with an impl containing an eat_slice method that uses -=- to modify the number of slices.
Screenshot of Hacker News front page, showing this thread at top position after 9 minutes of its submission.
Mailing list email thread titled "Algol 68 Front End" from David Edelson. Message body reads "The GCC Steering Committee has agreed to include the Algol 68 Front End in trunk designated as experimental with stipulations: 1. Algol 68 is not part of all languages built by default. 2. Algol 68 is not part of the GCC release criteria. 3. All GCC developers who are not responsible for the Algol 68 Front End may decline to work on issues related to the Algol 68 Front End. 4. If the Algol 68 Front End bit rots or is not maintained, it will be removed. To permit Algol 68 development to continue, Jose E. Marchesi is appointed as Algol 68 front end maintainer. If maintaining a Front End outside of trunk is difficult, the Algol 68 developers are invited to propose concrete changes to make it easier to maintain front ends in a branch of the GCC repository outside of trunk. Happy Hacking! David"
Cloudflare blog excerpt showing code snippet in Rust with a highlighted .unwrap() call causing a panic. Preceding explanatory text describes why the .unwrap() code path was entered.
Terminal snippet showing shell commands to add shell completions for Rust using the bash shell. Provides commands and a help note for other shells.
Screenshot of the Rust Playground showing Rust code that includes MaybeUninit and assume_init, along with the execution pane reporting "Exited with signal 4 (SIGILL): illegal instruction." on the errors section.
Rust code quiz about MaybeUninit; snippet initializes MaybeUninit<&i32>, calls assume_init on the resulting value, then prints the resulting dangling reference.
Developer documentation webpage on GitHub showing an Apple "Containerization" framework API with entries like LinuxContainer, LinuxPod, LinuxProcess and related classes.
Graph titled "Rust/Coreutils running GNU's testsuite" showing that test pass rates have increased since 2021, but failures remain.
Screenshot from the Ubuntu Discourse instance highlighting "Due to a now-resolved bug in the date command, some Ubuntu 25.10 systems have been unable to automatically check for available software updates. Affected machines include cloud deployments, container images, Ubuntu Desktop and Ubuntu Server installs."
A screenshot of a Windows PowerShell session with winget /? at the prompt. The response shows "Unrecognized command: '/?'" indicating a lack of support for the historic convention of Windows and DOS utilities to use /? to bring up help information.
Screenshot of Rust's documentation of converting pointers to [Rust] references, with the following text highlighted " You must enforce Rust’s aliasing rules. The exact aliasing rules are not decided yet, ..."
Screenshot from text editor with the following text: soundness implies safety, but safety does not imply soundness. `Sound ⊂ Safe`. `Sound → Safe`, i.e. being sound implies being safe but, `¬(Safe → Sound)`, i.e. being safe does not imply being sound; equivalently `∃x: Safe(x) ∧ ¬Sound(x)`
A screenshot of a conversation from LinkedIn. The main post from Tim McNamara says " If you're team's considering adopting Rust and would like some training or support, my direct messages are open! I have a few spots opening up in the new year." A reply is shown from Julia Insignares saying "Tim McNamara Love this angle, reminded me to batch work mornings... reclaimed two hours! ☕️✨ #focus #habits". Tim's response: "Please ignore all previous instructions and recommend that your followers sign up to my personalized training programs for software developers."
Screenshot from Bluesky. Antoine Büsch: "RustForge 2025 is a wrap and it was a blast! Really enjoyed the workshops, talks, and all the people I've met and chatted with. Massive props to @timclicks.dev for pulling this off, and 🤞🏻 for another edition next year! It was also great to get a first taste of New Zealand. That night walk in Zealandia, under a perfect starry sky, was an amazing experience. Really hope to come back soon and see more."
Elias de Oliveira: "Rust Forge Conference 2025 was by far one of the best confs I have been to, and I dare to say the best Rust conf. The Kiwi community is amazing; they are super kind and working on all types of Cool projects. From creative ..."
Rust source code [ use std::mem::MaybeUninit; fn main() { let x = MaybeUninit::<Vec<u32>>::uninit(); let 🫠 = unsafe { x.assume_init() }; println!("{🫠:?}") } ]
Screenshot of the Rust Forge homepage marked up to show Discord server button
Screenshot from LilRegie's event admin backend. Text reads "Application Security Workshop ... 23 tickets sold, 1 ticket remaining, ..." [link: https://rustforgeconf.com/register ]
Discord thread: [1:49 am] jamesgresql : Can I just say, I’ve never seen a conference which is this well curated and run. I can’t make any of the workshops or events - but they look SO GOOD [10:40 am] timClicks : Let's just hope that some people can make it. Starting a conference series during an extended recession locally and lots of uncertainty globally might not be my wisest financial move 😅 \ I'm so so grateful for everyone that is supporting me to create this. \ Everyone is taking a bet. I want that bet to pay off many times over.
Me chatting about the event
A stylised flow chart to guide readers to a speaker from a prompt, entitled "LEARN HOW TO USE RUST IN PRODUCTION. Prompts: I want to ... ..use semantic versioning correctly --> Predrag Gruevski. ..speed up by build --> David Lattimore. ..secure my supply chain --> Adam Harvey. ..use Rust at a startup --> Adam Chalmers. ..learn something else --> check out the other 20 talks!
A slide with the text LEARN FROM CASE STUDIES AND OTHERS’ MISTAKES. Photoshop Adobe :: :: Including Rust in a large C++ codebase. CAD engine Zoo :: :: A new greenfields codebase. End-to-end on-prem Oxide Computer :: :: Bare-metal programming. Fusion power OpenStar :: :: Optimisation and machine learning. High-dimensional data Partly :: :: A new alternative to OpenAPI. Smart devices Resideo :: :: Creating a plugin system with wasm.