| github | https://github.com/am-kantox/ |
| blog | https://rocket-science.ru |
| stack overflow | https://stackoverflow.com/users/2035262/aleksei-matiushkin |
| forum | https://elixirforum.com/u/mudasobwa/summary |
| author of | metastatic, metacredo, ragex, md, finitomata, estructura, telemetria, etc |
In AI era, the languages/frameworks/libraries having different ways to accomplish the task (like ruby’s reduce/inject,) are a first-class threat to bugs and maintenance issues.
You language of choice has while and for loops?—You are doomed.
Iteratable arrays and/or lists with an access by index?—Doomed.
Greenthreads with mutable state?—Doomed.
if operator?—Doomed.
Etc.
AI-generated code is mostly vulnerable to conditional statements. uncertainties, and multiple paths to the target.
Rusty clippy fails when it sees 3.14. Here is the fix:
▸ Changed 3.14 → 2.72 in test to avoid clippy approx_constant (PI approximation)
That’s all one needs to know about how Rust ecosystem is designed and engineered.
Łukasz wrote a great article, ‘guiding not ruling’ the way of writing tests. I agreed with everything, short of his attitude to mocks. The further discussion revealed that we treat mocks in an absolutely different manner.
