There's another camp that don't care about the craft AND also don't care about the product. This camp, wielding power of AI, is making life worse for the other two camps.
I've been getting so many code reviews that are generated by AI, but the author does not even has the decency to self review the generated code before they send out pull requests. It feels like an insult sometimes. For example, unit tests that basically assert if `a = 1` after setting a to 1.
Every PR now has lots of unit tests, but they test the implementation details, not the spec. So now every change that breaks their implementation details causes false positive test failures. This creates a self enforcing negative loop. Every PR now comes with tons of unit test fixes.
People start responding to PR comments with something along the line of: I ask AI but it was not able to solve the problem, if you have a solution, LMK. Or another variant I see often is: I think this is wrong, but AI says this is fine, so I'll leave it as is.
I see craft lovers or product people using AI effectively. I use AI daily too. But the above camp is making my day to day job sometimes unbearable.
if someone really want to have single keystroke, there's always F<number> key that they can map to their frequently used movements, such as last edit, next function, special marker (such as `m`), etc.
I can see how that could work depends on the setup and the context. For example: People might use `. to jump to the last edit, or to a mark they set manually. Or simply `ciq` to edit inside the next quote without any manual cursor movements. I see people use plugin like harpoon to jump to their favorite location quickly. If you don't know about such setup, seeing people type <leader>1 to jump not just within a file, but across files, seems magical.
Something about implementing a workflow process that involves collecting inputs from multiple users is really hard. Epic's system basically collects inputs from schedulers, front desks, nurses, technicians, doctors, billings, etc. Each step of the process depends on previous step. If step X fails, but the result of the failure can only be recognized at step X+10, it will probably throw the workflow engine into chaos ...