muddi [he/him]

There are automations. You can even add git hooks iirc. Mostly I find the lint and other code quality integrations nice to have in the IDE, since the inline results allow me to navigate directly to the code

Diffing is a lot easier too

Nitpicking can be automated by a linter, then reviews can actually sit back and review more important things like high-level design and scalability

as if peer reviews could actually spot bugs that tests can’t catch

There can’t be bugs if there are no tests to catch them! Ofc you can also automate test coverage standards. But PRs are sometimes the only way to catch bugs, even and especially with senior devs in my experience bc they are lazy and will skip writing tests, or write useless or bare minimum tests just to check off code standards and merge on ahead

I think of it in terms of levels building on top of each other, or circles enveloping each other; also how I evaluate interviewees and new hires:

1. Finishes the task, but needs handholding
2. Finishes the task, figuring it out from docs, guides, and internet
3. Finishes the task, proactively trying to make sure it doesn’t return again as a bug or failing QA
4. Finishes the task, designing things in a way so that devs don’t need to put in extra effort in the future

In short, learning how to do something right, but also alternative strategies, how to pick the best option, and finally make sure you always end up with the right choice, or automatically do so, by design.

It’s at core a matter of experience, but taking on new opportunities and reading up helps to accelerate that.

“suffer”

There is a lockdown mode or something in the power menu that should disable biometrics until the next unlock with pin/passcode

Not defending the companies, just something to be aware of if you see a cop coming towards you in the distance

marvel fans 2 seconds after Martin Scorsese says something

I wonder if it’s all those variables named with single letter and abbreviations, so annoying to code review