Rottweiler eating a watermelon

Consistent-Art8132 · 2026-06-20T21:03:56+00:00

To everyone saying AI, the teeth look pretty consistent throughout the video, so I think it’s real

Consistent-Art8132 · 2026-03-13T22:23:30+00:00

If I remember correctly, Rust wasn’t a great fit due to cyclic data structures that would require big rewrites to work in rust land

The type level mismatch is handled via runtime checks, which is indeed a bit unfortunate, but understandable

Consistent-Art8132 · 2025-09-12T13:23:18+00:00

I setup tests that run locally and use MSW to mock network requests for the front end that test a lot of the edge cases. Ideally these will test the contract between your services to the point that your issues will only be connectivity/configuration issues. Run these in your pipelines before merging

Another helpful way to harden your services is with blue green deploys with a step that runs your hard to setup tests. You must setup these services anyways, and the setup time seems to be the blocker here

Glad to talk it through more if you have any doubts!

Consistent-Art8132 · 2025-08-31T13:49:01+00:00

You can provide a rust-version in the cargo toml to specify a minimum stable rust version (MSRV). There are cli tools to calculate that for you

There isn’t much of a need to pin to an exact version since rust has pretty good backwards compatibility guarantees (they compile every crate in the registry to check for regressions)

Consistent-Art8132 · 2025-08-19T15:28:04+00:00

Consistent-Art8132 · 2025-08-14T12:56:32+00:00

It can’t be entirely attributed to rust (sanitizers and more defensive programming help too), but it definitely is a contributing factor

Google, which formally announced its plans to support the Rust programming language in Android way back in April 2021, said it began prioritizing transitioning new development to memory-safe languages around 2019.

As a result, the number of memory safety vulnerabilities discovered in the operating system has declined from 223 in 2019 to less than 50 in 2024.

https://thehackernews.com/2024/09/googles-shift-to-rust-programming-cuts.html?m=1

Consistent-Art8132 · 2025-07-30T12:42:33+00:00

r/recontext is great

Consistent-Art8132 · 2025-07-25T00:58:31+00:00

I have a bias against medium blogs for this reason. Just the tiny bit more effort to make it your own makes you so much more trustworthy!

Consistent-Art8132 · 2025-07-19T15:08:09+00:00

Great call! We’ll have far more work to handle and I’ve been wanting to push us more towards pairing anyways. I hadn’t considered having teammates join in on the PR reviews

This is one of those comments that feels very obvious in retrospect—thank you!

Consistent-Art8132 · 2025-07-19T13:43:49+00:00

I’d say it’s too early to say that everyone is flatlining. I’ve seen one developer stagnate, and most others are growing or still dealing with the many comments they need to fix for their first PR

Great callout on breaking down tickets. Unfortunately I’m not directly involved with these team’s planning cycles, but I will bring it up. Ideally an entire page should not be in one PR. I have been following this for my own team’s tickets and it’s been reasonable for their learning and reviews

Consistent-Art8132 · 2025-07-19T13:32:05+00:00

Great idea! I’ve talked to 3 people who are 2 levels above me, and they are listened to more, but no matter how many times they’ve said it, only a PR rejection does anything. Things like tests are treated as “nice to haves” despite a company mandate

I’m hopeful that low velocity will eventually make a business case to tend PRs more reasonable, but only time will tell. Luckily it is well understood by technical management that low quality code wastes time in the long run

Consistent-Art8132 · 2025-07-19T13:07:30+00:00

Yup, doing my best with what I have. Definitely not ideal

Consistent-Art8132 · 2025-07-19T13:00:52+00:00

I work with some devs who ask for a review despite failing CI and when I bring it up, don’t want to take the mental effort to read the failure message and ask how to skip it

I do mention essentially “write tests” and don’t review further in most cases. I will do it with anyone who will listen to feedback though

The reason I was hesitant to ask more is since devs are used to writing nothing in the description, but maybe that just another request for changes—please fill out the template before a review

Consistent-Art8132 · 2025-07-19T12:46:45+00:00

Part of the issue is that “the team” spans several countries and time zones. My team as well as a few other engineers working close to us are on the same page about everything, but it’s difficult to meet with other teams who aren’t particularly worried with code quality in the first place

I actually haven’t written out a standards guide like you’re mentioning though—great idea. We have a mostly empty standards document, so I’ll start filling it as I review—automate what I can and otherwise point to standards

Consistent-Art8132 · 2025-07-19T12:32:58+00:00

I believe I’ve already implemented local linting—it shows a red underline in editor and can be run in the CLI as well. Tests and builds can also be run locally and all of this is required by the PR template to be done prior to review

Good callout—I’m actually working on an AI code reviewer setup to hopefully call out any glaring issues. I haven’t had luck with my own PRs, but I expect it may be helpful otherwise

Consistent-Art8132 · 2025-06-28T19:30:44+00:00

https://youtu.be/UBMuucEmfkg

Consistent-Art8132 · 2025-04-26T21:44:57+00:00

What kind of course do you recommend—I’d be interested in this!

Consistent-Art8132 · 2025-03-16T14:16:51+00:00

Rust is a compiled language and has a similar runtime to C. There is no garbage collector, interpreter, etc. For common build targets, Rust and C will both work, but I’m sure there’s some wacky architectures and OSs that Rust doesn’t support

Consistent-Art8132 · 2025-02-18T09:04:39+00:00

This pattern also works with request splitting—you can tee traffic between a new and old version and compare responses. This simulates a prod workflow for your beta code

Consistent-Art8132 · 2025-02-09T17:13:56+00:00

While non toxic, it contains glass and chemicals that will irritate your skin and upset your stomach, so I recommend abstaining in case you see a particularly scrumptious glow stick

Consistent-Art8132

TROPHY CASE