Remember when computers worked?

Nah, me neither.

I think #rustlang should be marketed as a language for lazy programmers. There's a lot to learn and no shortcuts, but after the hard work is done you get to be super lazy!

Pass the wrong arguments into a function and get told how to fix it. Break the code while refactoring and ask the compiler to tell you what to do. Use other people's code via a single line in cargo.toml. Ask clippy if your code is weird and how to improve it. Don't think about race conditions. Let your mind drift

AI tech debt

https://www.kdnuggets.com/2022/07/hidden-technical-debts-every-ai-practitioner-aware.html

https://www.enterpriseai.news/2021/12/17/technical-debt-and-ai-what-it-is-and-how-to-fight-it/

https://towardsdatascience.com/technical-debt-in-machine-learning-8b0fae938657

25 years of GTA

https://www.bbc.com/news/uk-scotland-scotland-business-63742004

The timing in that video 🤣

https://www.twitter.com/ITNArchive/status/1597221270227013632

Someone shared https://liquid-rust.github.io/2022/11/14/introducing-flux/ and I am quite enthusiastic about this idea!

It reminds me of https://github.com/xldenis/creusot .

@vzaliva Hi Vadim 👋 great that ActivityPub works at least in one way 😂

Hi friends, if you're managing an #OpenSource or #FOSS project please tag every release you make. It's really helpful for inspecting source code and finding regressions.

#Nextest has its automated release flow be triggered by tag pushes, which means that creating and pushing tags (managed by cargo-release) is an essential part of the process. Feel free to adapt nextest's release flow to your liking!

https://github.com/nextest-rs/nextest/blob/main/.github/workflows/release.yml

https://github.com/nextest-rs/nextest/blob/main/internal-docs/releasing.md

Reminder that as per CoC, a honk rewrite in rust must be called husk and not hunk.

So pest now has a rule debugger! https://github.com/pest-parser/pest/discussions/739

Nice!