23 Followers
119 Following
193 Posts
I'm a computational scientist, Rust, C++ and Python developer, FLOSS enthusiast, and privacy advocate

Some people before #LLMs

"But writing #documentation is so time-consuming. We have no time for that!"

"We won't adopt #Rust as our service is not performance-critical."

----------------

The same people after LLMs:

"We need some more docs over here... and please update that SKILL.md. Otherwise, how should our LLM navigate our codebase and know what to do?"

"#RustLang is awesome! LLMs make way fewer errors now with strict types!"

Just insane!

#Society #People #AI #ArtificialIntelligence

Is your company currently hiring for a role that includes using Rust?

Reply with a link to the opening and any relevant context.

If you're not, we'd appreciate a repost for visibility

#rust #rustlang #programming

@marekfort GNU #Emacs would never.
Kleiner Tipp für alle, die bei der Halbierungsinitiative JA stimmen wollen: Deine Stimme zählt doppelt, wenn Du auf dem Abstimmungszettel direkt hinschreibst, welche Sendung der SRG Du blöd findest.

Hi rustaceans. I'm hitting a wall with this life time error where I think lifetimes should not play a role.

Why is the lifetime of a trait's associated type even in question when defining a generic axum handler? The type parameter is not the type of an argument, it's not contained in a future and it's not the type of a return value. I'm drawing a complete blank and your insight or boosts are much appreciated!

https://users.rust-lang.org/t/trait-bounds-of-type-also-applied-to-generic-type-parameters/138566?u=tjunge

#rustlang

Trait bounds of type also applied to generic type parameters?

I'm hitting a wall with a weird-to-me compiler error. When creating a generic axum handler function, it requires that the type parameters be Send + Sync + 'static, even in examples where they are simple associated types that never need to be sent between threads. I found a minimum reproducible example where the type parameter isn't even ever used: use std::sync::Arc; use axum::{Router, extract::State, response::IntoResponse, routing::get}; trait Greeter: Send + Sync { type GreetType; ...

The Rust Programming Language Forum
@samiamsam @geerlingguy There's always an XKCD, but sometimes there's a Calvin and Hobbes too

RE: https://fosstodon.org/@rustnl/116119445480765544

Warning: the end of this talk might be unreachable!

#rustlang #rust

Is your company currently hiring for a role that includes using Rust?

Reply with a link to the opening and any relevant context.

If you're not, we'd appreciate a repost for visibility

#rust #rustlang #programming

It’s time I crank up the search for new work to 11, because wow I really need it.

Bottom line: you bring me aboard your web publishing or software team because there are many fires vying for your attention and I figure out which ones to put out first.

My CV: https://jaredwhite.com/cv/
My biz site: https://www.whitefusion.studio

I'm design-focused: smooth fast UX & providing delightful experiences. Deep frontend, full-stack, and open source expertise.

Boosts greatly appreciated!
#FediHire #GetFediHired

Jared White - CV

Full-stack Developer • Educator • Open Source Maintainer

Jared White
Repeat after me: Separating username and password fields on separate (fucking responsive) page WILL NOT INCREASE A FUCKING SECURITY IN ANY WAY! IT WILL JUST MAKE THE PASSWORD MANAGERS TO WORK WORSE AND THUS IT WILL FUCKING DECREASE THE SECURITY!!!