You have to choose either dumbbells or barbells to get wiped from existence. Which one are you keeping and why?
You have to choose either dumbbells or barbells to get wiped from existence. Which one are you keeping and why?
You have to choose either dumbbells or barbells to get wiped from existence. Which one are you keeping and why?
you can do every barbell excercise with dumbbells. The reverse is not true
try dumbbell squatting even a light weight like 300 lb moron
Try Bulgarian split squats with 150s.
couldn't do it tbh. but if i could, i could use either a barbell or a dumbbell
I'll save you the math but with lunges it would take a 160 lb male 147 lbs of added weight to approximate a 300 lb squat. With two 50s and a vest I think that's doable. Not even going to bother with BSS.
i don't do squats
Dumbbell.
Name 3
>you can do every barbell excercise with dumbbells. The reverse is not true
>Name 3
What dumbbell exercise can you not do with a barbell?
A barbell is just a really big dumbbell.
Lateral raises
Lu raises
Hammer curls
Skullcrushers
But not that I have a barbell I would miss it terribly
You can do skullcrushers with a barbell thoughbeit
No
Deadlifts, Snatches, Cleans, Squats, Jerks, and Push Press would all be done with baby weight.
What is the point of making a thread like this?
This image triggers me. You wouldn't have an "app service" and API gateway (assuming they mean AWS) at the same level for calls. The frontends should be different but if the mobile is calling an api gateway then the browser would be calling it to - no one maintains two different apis.
How would you picture it then?
Mobile app and browser both go to the same api gateway that then go to individual services.
Yeah but how would you picture it without it looking moronic?
Like this for an architecture diagram. Alternatively you remove the single api gateway and have one for each service.
Yes, good, I didn't cosider adding the end user. Thank you
>remove the single api gateway and have one for each service.
Lol do you even graphQL homosexual?
Yeah, I have actually. It's pretty good and makes things a bit simpler for the frontend. It saves costs on the backend depending on how often individual services are being invoked and other things. It's very much a pro/con individual scenario, I think.
That's fine, you can have server side rendering as long as it doesn't contain your core business logic separate from the mobile app. It's hard for a lot of old businesses to move off their jpas but the jpa can simply call the same api as the mobile app. You never want to have the same business logic implemented separately. See my shitty 2 minute diagram
>no one maintains two different apis
You would be surprised of the moronic shit I've seen implemented by "top engineers" in one of the biggest American corps
Not everything requires SPA (single page web app), maybe they are using seever side rendering, a tried and true simple method. But no, you have to over complicate shit with megabytes of JavaScript don’t you?! Learn to fricking architecture
>You have to choose either dumbbells or barbells to get wiped from existence.
I choose Black folk
keeping dumbbells need muh isolations sorry powershitters
>Implying you can't do variations with barbells that target specific muscles more.
>skull crushers or french press
>barbell curls
>upright rows
>barbell front raise
>plate lateral or rear raises
you have been deboonked
>you have to choose
no I don't.
Something about breakfast and well-melanated individuals
Keep barbells.
>why
Home gym adjustable dumbbells suck and are expensive.
Kettlebells.
I feel like John Wick when I use them.
Bumbbells
Barbell for squats, for everything else I do weighted calisthenics anyways.