Pull-request makes sense in Github, because the typical work-flow for open-source on Github is to fork the repo you want to contribute to. Hence, the maintainer has to pull the code from you.
Merge-request makes more sense in Gitlab because they're main use-case is as a self-hosted internal tool where developers most-likely are pushing all of their feature branches to a central repository and asking for the branch to be merged into the mainline branch.
There is no such thing as "reverse" natural selection. It's just that intelligence and being career driven are not a favorable trait for natural selection. It's working just fine.
Any runner? Sprinting is as good as anything for developing explosive leg strength. Of course, the best sprinters work lifting into their training as well.
> Sprinting is as good as anything for developing explosive leg strength.
Considering that "leg strength" is conventionally measured via seated leg press for a maximal, single repetition, I would be extremely surprised if an Olympic sprinter could achieve the same sort of leg strength that an Olympic weightlifter (of similar weight) could attain.
That depends completely on how you define "strong". I think legs that can carry a 50 pound pack to the top of a mountain are "stronger" than a guy who can lift twice as much as me, but can't even run a 5K.
Because last I checked, the english language was flexible, with multiple definitions for most words. I looked a few up for "strength". I did not find any dictionary that solely defined it as the ability to move heavy objects.
Words have consensus meanings, and when you try to redefine them unilaterally you make it harder to communicate. Strength in this context is defined as the ability to exert physical force (as in Newton's Second Law, force = mass x acceleration).
Do you disagree that it's useful to distinguish between strength and endurance?
codingdave asserted, "I think legs that can carry a 50 pound pack to the top of a mountain are "stronger" than a guy who can lift twice as much as me, but can't even run a 5K."
The former is an example of great endurance (without necessarily having great strength), and the latter is an example of great strength without endurance. You can have one without the other, so they're different, and it's plainly incorrect to say that a person with high endurance/low strength is "stronger" than a person with high strength/low endurance.
I took it to mean that the thing being described by the word endurance is objectively different than the thing being described by the word strength when not being used in the endurance sense. In a way saying that the measurement of a muscle's ability to repeated do the same amount of work before failure is a objectively different than the measurement of a muscle's ability to output a maximum amount of work for a single rep. Or another way, the stat that lets you lift a 1kg weight 200 times is objectively different from the stat that lets you lift a 200kg weight once. Related, but different.
As to if the word strength is objectively different from the word endurance, simply consider that one starts with a 's' and the other with an 'e'.
I'm not entirely convinced 'strong legs' are the causative factor in healthier brains. It is possible the researchers measured an artifact of people that do running cardio.
Particularly damning is that the research participants were all female. Anyone who's set foot in a gym knows that women do cardio disproportionately, and that the cardio they do increases thigh musculature...
I have to disagree. Sure women do more cardio, but the cardio increasing thigh musculature? Not a chance. Squatting increases thigh musculature. Doing the elliptical for an hour a day does not. Running slowly or at a medium speed does not. Nor do either lead to any gain in strength anywhere.
Have you seen the thighs and calves of people who bike? Of course lifting will cause more hypertrophy, but arguing that cardio doesn't lead to some gains in musculature is just wrong.
Huh? Running certainly increases the strength of your leg muscles. The only possible exception to this would be if you were jogging very very slowly. But if you go from not running at all to running faster than, say, 6mph, your legs will certainly get stronger.
The best company I ever worked for did a two hour pair programming session on a simple rails app (since they were a rails shop) with every candidate that got passed the "chat over coffee" stage. You'd get to see the kind of code the candidates write and how they work through problems, how they work with another developer, and get a really good overall sense of how they would work as part of the team.
I like pair programming sessions a lot because both the candidate and the employer are investing an equal amount of time. While the intention behind take-home projects is good, the result is often that the candidate invests several hours into a project just to be quickly passed over by the employer.
Alternatively, I used Rdio first and tried out Spotify when they released the Playstation4 integration and my reaction was "Oh, ok, it's basically Rdio but with a lousy interface. I'll keep using Rdio then".
I love the Pomodoro Technique, and use the Tomighty app specificaly for it's simplicity and that it's native so I don't need to keep a pinned browser tab open just for it - love simple things like this that just sit in my system-tray.
I pair it up with Toggl, a time tracking service online to keep reports of what I'm working on, and I find it a huge boon to my productivity and ability to justify the time I spend working on things.
Merge-request makes more sense in Gitlab because they're main use-case is as a self-hosted internal tool where developers most-likely are pushing all of their feature branches to a central repository and asking for the branch to be merged into the mainline branch.