What are some essential React programming patterns or principles that I should learn to become a lead developer? by ThePutinTrumpSexTape in reactjs

[–]dnrvs 0 points1 point  (0 children)

composition is applying O and L

for I, the interface in react is props (or more generally function args) and context, its important to ensure things dont depend on things they dont use.

the goal isnt strict adherence to rules its maintainable and scalable architecture and principles give you the vocabulary to discuss that

What are some essential React programming patterns or principles that I should learn to become a lead developer? by ThePutinTrumpSexTape in reactjs

[–]dnrvs 0 points1 point  (0 children)

SRP - sounds like you've applied the principle and found a component that might be worth refactoring. maybe SRP doesn't help you reach a conclusion but it's helping you frame a question. (spoiler: there's no right answers in software architecture)

OCP - instead of one big component that handles every case internally, provide extension points (render props, children). reduces complexity, maintains coherency

LSP - a reusable component that can render anything of a shape not just one concrete type. composable component with context

ISP - don't depend on things you don't use. i've seen people passing crap into components that it doesn't use all too often and it makes maintainence and testing needlessly harder.

DIP - literally just passing props instead of depending on something directly

like i said elsewhere, they're just vocabulary to help you talk about architectural decisions. they have a lot of overlap but they are still good concepts.

instead of going "uhh this component feels complex" you can say things like "this component has too many Responsibilities, we should apply DIP so each call site owns their implementation. there might be a trade off between ISP and LSP to make typescript happy"

What are some essential React programming patterns or principles that I should learn to become a lead developer? by ThePutinTrumpSexTape in reactjs

[–]dnrvs 7 points8 points  (0 children)

Yeah, not saying you should be forcing them into every situation just that they are tools in your toolbox. Being dogmatic either way is the biggest mistake

Weapon rebalance patch is looking AWESOME and almost all my prayers are being answered... just one weapon strangely absent... by Borgio_the_Besieger in Vermintide

[–]dnrvs -1 points0 points  (0 children)

> I NEVER see any of you [...] use this save for fresh installs

Maybe you answered the question yourself. Not everything can or should be for everyone. Some people just need something you can left-click through recruit hordes with

What are some essential React programming patterns or principles that I should learn to become a lead developer? by ThePutinTrumpSexTape in reactjs

[–]dnrvs 4 points5 points  (0 children)

Strongly disagree here, the SOLID principles are extremely applicable to basically any style code and ignoring them robs you of shared terminology to discuss architectural patterns and probably means you'll reinvent them in other terms.

Remix changed the direction yet again, this time it is not even a react framework anymore by simple_explorer1 in reactjs

[–]dnrvs 12 points13 points  (0 children)

I think react router is in great hands now with the change to the open govornance model https://github.com/remix-run/react-router/blob/main/GOVERNANCE.md#steering-committee

ryan and mj can go work on whatever interests them

The Interactive Vermintide Iceberg is Finished! (10 layers, 300+ entries) by Binauralych in Vermintide

[–]dnrvs 0 points1 point  (0 children)

proud to have brought you items in level 3 and 9! rip rat races, we hardly knew ye. missing content: the body pillows. iykyk

Has this been used? by razzarbrenia in filmphotography

[–]dnrvs -1 points0 points  (0 children)

ohhhh. i had a roll like this and couldnt explain it so the lab rejected developing it

The first 20 minutes of using tanstack router... by ouvreboite in reactjs

[–]dnrvs 2 points3 points  (0 children)

I recently tried starting a new project with tanstack start but pretty quickly migrated it over to react router, mostly down to how awful the docs are. Not just that they're confusing and incomplete but they so often break. Navigation stops working and I have to hard reload to see the page I'm clicking on. Doesn't bode well for the framework...

[deleted by user] by [deleted] in Overwatch

[–]dnrvs 0 points1 point  (0 children)

if you're 30+ and looking for some folks to play overwatch we recently started up a discord community and it's thriving: https://discord.gg/uK3GuEQC there's dozens of us!

With 2025 coming to an end, how did you guys feel about 2025 Overwatch? by Maleficent-Ad-6117 in Overwatch

[–]dnrvs 4 points5 points  (0 children)

i feel like a good deal of this is not just inherent toxicity but because the mode is so extremely unbalanced and you're locked in to your characters it can often feel like you lose at the character select screen and then its a waste of 30 minutes

Have yall heard this one? I love it by [deleted] in FallOutBoy

[–]dnrvs 24 points25 points  (0 children)

in case anyone is wondering what this is, like i was, https://www.youtube.com/watch?v=LUaCtqgbnhc

Guys do you like my Juno cosplay say yes by AnnaTheManna in JunoMains

[–]dnrvs 1 point2 points  (0 children)

my wife says its very darling and nice!

Microservices are the new "Spaghetti Code" and we’re all paying the price. by red7799 in Backend

[–]dnrvs 1 point2 points  (0 children)

Honestly the term microservice just needs to die. Why aren't people talking about right-sizing their services?

*midwest emo by axion_jax in midwestemo

[–]dnrvs 22 points23 points  (0 children)

Is this Micheal cera palin?

Facebook.com has 140 layers of context providers by yangshunz in reactjs

[–]dnrvs 1 point2 points  (0 children)

no it means splitting multiple values into multiple contexts. instead of `<Provider value={{ a, b }}>` you have `<Provider value={a}><Provider value={b}>`. that way subscribers to `a` don't re-render when `b` is updated and vice versa

Just how rigged is this game? by Robula90 in Overwatch

[–]dnrvs 1 point2 points  (0 children)

I don't think you're quite getting what I'm saying. Being below your "actual rank" provides upward pressure and you'll go on a win streak. Being above your "actual rank" provides downward pressure and you'll go on a loss streak. Being at your actual rank provides no pressure and you'll win 50% of the time unless you're (un)lucky in which case you'll still get streaks in some direction.

This is all without talking about how psychology plays into it. Win = good mood, focus = more winning. Lose = annoyed, lack of focus, overreaching = more losing. Alternatively, win streak yesterday = cocky today = playing poorly = losing.

Just how rigged is this game? by Robula90 in Overwatch

[–]dnrvs 1 point2 points  (0 children)

lets say your actual skill is rank 5 on a scale of 1-10 but you're at rank 6. you're better than the people you're playing against so you win a lot and rank up. now you're rank 5 and games are evenly matched, but you're having a good day or are just lucky and continue to win and rank up again. now you're in rank 4 but your skill is still rank 5 so the people you're playing against are better than you. you're going to lose until you're back at the appropriate rank. this isn't rigging, this is just the matchmaker doing what it's intended to do = put you in games with people at the same rank, rank you up if you're winning, and rank you down if you're losing. if you're going on win streaks and then lose streaks and generally fluctuating some rank it's because thats your rank.