fusio @ fusio @lemmy.world

Posts

1

Comments

30

Joined

2 yr. ago

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

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.

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?

I see the revoke button but it does nothing. I'm in Switzerland. Is it a bug?

libgen seems to be one of their sources

we have them in CH.. I'm not a fan

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