sounds like your company sucks. I'm sorry, must be lonely
sounds like your company sucks. I'm sorry, must be lonely
suboptimal viewing [of the ads]
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
libgen seems to be one of their sources
this, and also nothing is 100% new - knowledge in similar areas will always help
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?
and how you could test it easily! it's incredible how much it helps for cleaner architectures
I still appreciate not having to open a website.. there's way too much context switching on the web
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
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!
who should we be worried about?
depends what you mean by application code.. I'd say if your business logic is exclusively used by a ui feature the best is to keep them together. but you probably want to abstract away things like data access. I found working with a nx monorepo helps reasoning about how to structure your code.
just get a synology?
what is not going to Oktoberfest gonna do?
or people used to work alone never having to go back to their code (e. g. bad consultancy jobs)