> I respectfully, but strongly, disagree. There's a reason most NBA players are over 2 meters tall, and one does not become taller with time, dedication nor focus.
Being tall isn't a skill. I suspect you could be skillful enough at basketball to overcome the hight disadvantage. However, I think most people who might become that skillful see the high disadvantage (plus the general difficulty of becoming a pro basketball player) and take a different path through life. It's also possible that the amount of time that would be needed to grow your skill past the height disadvantage is too long, so it's not feasible to do it to gain a position in the NBA.
It's a matter of the definition. The general factor of intelligence, which is measured through various somewhat lossy proxies like IQ tests, is exactly the degree to which someone exceeds expectation on all cognitive tasks (or vice versa).
The interesting finding is that this universal correlation is strong, real, and durable. Of course people in general have cognitive domains where they function better or worse than their g factor indicates, and that's before we get into the fact that intellectual task performance is strongly predicated on knowledge and practice, which is difficult to control for outside of tests designed (successfully, I must add) to do so.
Height is one physical attribute that helps, and professional players are mostly above average height for a reason. But also hand-eye coordination and fast-twitch muscles help even more. Many basketball players are very explosive athletes, because it's a sport with a relatively small play area and lots of quick movements are needed.
Track and swimming are where innate physical attributes have the most obvious benefits. Michael Phelphs had the perfect body for swimming. There is no amount of trainingg that 99.999% of the population could do to get close to what Usain Bolt ran. Most humans could not train to run under 4 minutes in a mile or under 2:30 in a marathon. They just don't have the right muscular and cardiovascular physiology.
Team sports are of course more complicated as other qualities come into play that aren't as directly physiological.
> Most humans could not train to run under 4 minutes in a mile or under 2:30 in a marathon.
Of course, but I don't think anyone was seriously suggesting that. The vast majority of humans can become pretty good at swimming though. And that was my interpretation of the original claim about cognitive tasks, mathematics, etc.
It seems to be pretty common even among native English speakers to use "writing assembler" and "writing assembly" interchangeably. If one were writing the tool that assembles to machine code, you'd say "writing an assembler".
Normally I'd agree (as a native english speaker with about twenty years of writing assembly under my belt), but the title tripped me up, too. I figured they forgot an "an" or an "s" at the end of "assembler" and i was surprised to find that no 6502 assembler was produced. It could be because I've written three different assemblers over the last two years, though, so it could be i was just projecting my own interests.
I actually prefer "writing assembly", and also think "writing assembler" is a bit confusing. But it feels like I'm several decades too late to complain about it ;)
True that. Having to carefully balance responsiveness and memory usage/OOM risk when setting up PHP-FPM pools definitely makes me grateful when deploying Go and Rust software in production environments.
I have to agree, despite using it a lot, async is the worst part of Rust.
If I had to do some of my projects over again, I'd probably just stick with synchronous Rust and thread pools.
The concept of async isn't that bad, but it's implementation in Rust feels rushed and incomplete.
For a language that puts so much emphasis on compile time checks to avoid runtime footguns, it's way too easy to clog the async runtime with blocking calls and not realize it.
No, ORMs abstract away the relational database and present it as if it were some kind of object database. Needing to map query results to structs is just incidental, and is completely missing the point of an ORM.
If copying query results to a list of structs is enough to qualify as an ORM, then the term is so generic as to be entirely useless.
This is clearly not what anyone means when they say they don't want an ORM.
An ORM library maps an entire relational database to a graph of objects, with the intention of abstracting away the relational database. Copying query results to structs doesn't actually do any of that.
Majority of ORMs really are nothing more than this.
But then it's nice to have something that generates optimised, database-specific SQL, can handle date/number conversion, supports many-many relationships, converting BLOB to binary streams etc.
Being tall isn't a skill. I suspect you could be skillful enough at basketball to overcome the hight disadvantage. However, I think most people who might become that skillful see the high disadvantage (plus the general difficulty of becoming a pro basketball player) and take a different path through life. It's also possible that the amount of time that would be needed to grow your skill past the height disadvantage is too long, so it's not feasible to do it to gain a position in the NBA.