

this, and also nothing is 100% new - knowledge in similar areas will always help
I already have to live with my choices in real life, let me play the damn game (╯°□°)╯︵ ┻━┻)
or people used to work alone never having to go back to their code (e. g. bad consultancy jobs)
it really struggles with mid sized monorepo (think react libraries managed via NX)
I love intellij. The gut Integration and diff utilities alone are worth using it. However, it is so. Fucking. Slow!
depends on the company/team culture. are other people gonna have to fix or extend code you wrote? are you the sole engineer working on entire modules? do you hate feedback?
what data? just curios because there are so many ways to do PRs properly… like for everything, if it’s done badly better not do it. does not mean it is inherently bad
sounds like your company sucks. I’m sorry, must be lonely
and how you could test it easily! it’s incredible how much it helps for cleaner architectures
what’s a trainer?
I still appreciate not having to open a website… there’s way too much context switching on the web
who should we be worried about?
yeah, fair point. it really only works with standard boilerplate code which is simple enough to not have any issue I guess… in my case working with a NX monorepo, that would be any code created using the generators
That’s why PR should be small. It’s much better to have multiple PRs than a single big one.
Totally fair to have gigantic PR full of boilerplate code, but generally you can split the boilerplate and your feature in 2 PRs, where only the feature will get a proper review.
All of this obviously depends on the criticality of the system :p