Another quote from The Manager's Path book that I wanted to share:

There are some projects, usually described by words like infrastructure, platform, or system, that require architecture or significant advanced planning. When faced with this kind of project, which includes many unknowns and relatively hard deadlines, you will find it doesn’t fit so well into the standard agile process.

I really do think that Agile fans are sometimes just a bit too eager to see it everywhere.

In my years at Google and AWS, we had outages and failures, but very very few of them were due to anything as simple as a software bug. Botched deployments, throttling misconfigurations, cert problems (OMG cert problems), DNS hiccups, an intern doing a load test with a Python noscript, malfunctioning canaries, there are lots of branches in that trail of tears. But usually not just a bug. I can’t remember when precisely I became infected, but I can testify: Once you are, you’re never going to be comfortable in the presence of untested code.

https://www.tbray.org/ongoing/When/202x/2021/05/15/Testing-in-2021

Origin: https://twitter.com/jschauma/status/1409608031508303875?s=19

Here is my Monday pick of a programming language😁: Flix

- Developed in Aarhus University
- Syntax similar to Scala
- Functional First
- Design inspired by Haskell, Rust, Scala
- Has Higher Kinded Types
- Checks purity and impurity at type level
- Has a special contract (constraint) language

Actually at the first glance I would say I like it a lot. I really think that Haskell over-engineered with their IO monad, and Scala has no built-in purity checks. So here we go. Might actually give it a try.

Microsoft seems quite serious about their love for Linux lately. Recently they released a first version of their own Linux Distribution https://github.com/microsoft/CBL-Mariner

Just found this podcast from Jane Street (the famous finance company that uses OCaml). They talk about a variety of topics from OS to UI to compilers.

Mainly they discuss how their teams work on these topics. Seems like a hell of an insight into FP at scale.

Finally brought up again a personal blog website after fiddling with CSS for a couple of days😅.

So here you go - a blog post on absence of lifetimes in our daily Rust code https://www.ivkov.tech/absence-of-lifetimes/

SQLX is planning to drop async-std runtime support and only use tokio.

And it is very indicative of the state of async runtimes in Rust. A lot of people on Reddit are saying that tokio won.

I think this is quite sad. Rust async working group should have standardized interfaces for runtimes long ago. Then there would be no split in the ecosystem and consequently less popular projects dying out.

As if the async working group heard me - they have just published a vision for async in Rust for the coming years!😁

They mainly discuss:
1. Support for async fns in traits
2. Common interface for runtimes
3. Easier syntax for async iterators

https://blog.rust-lang.org/inside-rust/2022/02/03/async-in-2022.html

React like cross platform UI framework in Rust - https://dioxuslabs.com/

It's finally happening 😁. Rust is getting better for UI construction!

Amazon recently posted about their contribution to Rust and there they mentioned that Rust was started as a research project in Mozilla in 2010.

And that was a huge historical inaccuracy there!

But hopefully soon it was corrected by Graydon Hoare (the actual creator of Rust) himself:

A minor nit: Rust didn't start "as a research project at Mozilla in 2010".

It started as a personal project (on my own laptop, on my own time) in 2006.

It was a small but real 17kloc native compiler for linux, mac and windows by the time Mozilla began sponsoring it in 2009-10.

https://twitter.com/graydon_pub/status/1492634815748739077?t=pWPVYsyF5QKlhN6LyzFFNw&s=19

Original: https://twitter.com/e_salvaggio/status/1494322969127964679?t=foIKToFvHKhvyNAqInMQEw&s=19

Ruthless Java 👀

Rust tip of the day:

If you ever find a lot of repetitive straight forward clippy suggestions try running cargo clippy --fix.

And depending on the complexity of the changes you might need to add
__CARGO_FIX_YOLO=1 cargo clippy --fix as clippy by default is allowed to fix only a small category of lints, others are considered more experimental.

For more info on this check out https://github.com/rust-lang/rustfix/issues/200

Another new lang from Google - https://github.com/carbon-language/carbon-lang

It is quite strange to include inheritance in a modern language. Though they want it to be "a direct successor to C++", so I guess their ideas are rather rooted in C++ design and style of thinking.

# Serde Tips

A nice /r/rust thread with tips about using serde_json, some of which are not so obvious. I only got two things to add:

- Don't forget to read through serde.rs, it covers most of the day-to-day knowledge. It's surprising how many serde users don't know about it.

- Consider using lib.rs/nanoserde if you only need some basic features and care about the size of your project's dependencies.

As we call it in Russian - being a "senior помидор"

Generic associated types in Rust are going to be stabilized soon - https://twitter.com/AliceICecile/status/1565110186456539136?t=MkhLkmKqKXK08esNrXxGOw&s=19

This is a big change for the Rust type system