I've never worked in the valley, and I usually don't have much to do with the web or mobile. I don't have a degree, and the subject has literally never once come up in an interview. In 17 years, I've never encountered anyone who cares. Also, the vast majority of job descriptions read something like "Degree in CS OR equivalent experience" and therefore explicitly do not require degrees.
It will vary from company to company and culture to culture... I have a friend at a large aerospace company who was basically told he had 3 years to get his degree or he was out... He's now a mid-level project manager and does 2-3 the workload of his closest peers, but H.R. policy was that he shouldn't have been allowed into his current position without it.
Try playing with an online solar system simulator some time. After thousands of orbits, a tiny gravitational nudge can have a huge effect on a system. Also read about the concept of orbital resonances.
Professionals do in fact date coworkers. It happens all the time - it's a matter of culture. Spend some time at Microsoft, for example. "Microsoft Married" is in the corporate slang lexicon on the intranet.
Of course, what he's managing to imply is that women should not date men at their offices. Because it victimizes the men, who are forced to retaliate when the relationship ends, and then they look bad in the press.
Could you be more paternalistic? We're talking about a woman who was a partner at one of the best VC firms in the world. Pointing our her unprofessional behavior implies nothing more than that _she_ should have known better. If you really want to be a white knight, stop treating women at the top of the industry like interns.
I've had to use Safari lately because Hulu simply won't work in Chrome. I've also found that some sites that are unusably slow in Chrome scroll like a dream in Safari. It's too bad, because I prefer Chrome's UI. YMMV.
It's not a matter of truth, just convention. "Software Engineer" is a title used in many organizations - not a subtype of engineer. It means programmer. Trying to apply arbitrary qualifications after the fact to make it more "engineer-like" is misguided. Some of us are called Architect even though we don't design buildings or use CAD software to design our products.
Some comments here suggest the possibility of making manual changes to the Rust code. After cross compiling, how does one make changes to the Rust code, then go back and make changes to the Python code, and cross compile again without losing the customized Rust code?
IMO there is an enormous difference. I've always defined hatred in terms like "motivated to kill, for real." Less serious is anger. Far less serious is mischief, which is where I feel most trolling sits.
Put another way, if a person is being irritating (in text, at that), and you find yourself feeling terrorized, there's a massive failure of communication occurring.
I have to agree with you. It's never registered as a problem for me. I think of it like an ordinary kitchen knife. Yeah there's an off chance I might cut myself, but 99% of the time I'm just going to enjoy a steak.
Seems there's nothing specific in the article about which which changes to DX are supposed to enable CGI quality, or how. Is it more polys/sec for smoother models and more geometry? Maybe a more efficient shared memory architecture for GI (I'm speculating. Maybe dreaming)? We're always being promised cinema quality in games, and while we're really not all that far off from it already, we're still quite a bit behind in lighting/rendering.
And not just rendering. Animation is the biggest issue. You don't get Hollywood quality animation out of nothing. DX12 is going to provide some new features but calling it "as good as CGI" (i.e. movie-quality CGI) is just dreaming.
As a whole, I think the article finally provides a fair amount of specificness, but I was initially struck by how much space is devoted up front to "he-said she-said". It reminded me of celebrity gossip, sportscasting, and punditry.