News for hackers. Stuff that matters.
Re:Guide for Technical Development by drinchev on Tuesday May 12, 2015 @10:02AM (#9531793)
These examples on their own discredit the post so much that it's a shame it has "google.com" as a domain of origin.
Re:Guide for Technical Development by TheBeardKing on Tuesday May 12, 2015 @10:28AM (#9531971)
I don't know, I don't view Google as having the same level of perfection as, say, Apple. I know when I use Google products, almost infinitely in beta, there's going to be some things lacking and unpolished. Helpful yet unfinished, you take what you get.
Re:Guide for Technical Development by fecak on Tuesday May 12, 2015 @10:35AM (#9532009)
Perfection is one thing. But this is a page on their website trying to help them recruit for engineers? Shouldn't that have a bit of a higher standard?
Re:Guide for Technical Development by gonzo41 on Tuesday May 12, 2015 @10:49AM (#9532138)
all of these comments about non trivial matters are bike shedding. even this comment, its only increasing entropy, your missing the forest for the trees.
Re:Guide for Technical Development by itsybitsycoder on Tuesday May 12, 2015 @12:08PM (#9532737)
@rockdiesel, it's definitely "for" the trees, where "for" means "because of". You can't see the forest (big picture) because you're paying too much attention to the individual trees (details).
Re:Guide for Technical Development by pc86 on Tuesday May 12, 2015 @02:47PM (#9533969)
If the "reply" link is unavailable you can click on the time to be able to reply directly.
Re:Guide for Technical Development by rockdiesel on Tuesday May 12, 2015 @02:49PM (#9533989)
That makes sense. Thank you for your explanation.
Re:Guide for Technical Development by sukilot on Tuesday May 12, 2015 @04:29PM (#9534633)
Trivial, not non trivial.
Re:Guide for Technical Development by rockdiesel on Tuesday May 12, 2015 @12:02PM (#9532698)
Off-topic, but I always thought it was "can't see the forest through the trees" not "forest for the trees".

Meaning someone can't see passed what is in front of them (trees/treeline) to see the bigger picture (forest).

Re:Guide for Technical Development by fecak on Tuesday May 12, 2015 @02:24PM (#9533794)
If you look at the page now, it's been changed. JavaScript is now one word, university is no longer in caps, the "learn AI" bullet now has been formatted properly, and they've now properly capitalized GitHub. Looks like Google is listening to the suggestions made above (in parent post).
Re:Guide for Technical Development by jsudhams on Tuesday May 12, 2015 @12:51PM (#9533053)
Why is so much importance to written language? Why not practice casual writing like casual speaking. I think many of these expectations put lot of pressure on the people who wants to communicate in writing but that language to be written is not mother tongue or might not even gone to high school.
Re:Guide for Technical Development by hueving on Tuesday May 12, 2015 @01:15PM (#9533264)
The expectations are higher when it comes from a major company like Google, especially when it's speaking from a position of authority on a topic like what to do with your life.
Re:Guide for Technical Development by phillipwills on Tuesday May 12, 2015 @07:59PM (#9535839)
With casual speaking, you place emphasis and pauses, naturally... With writing, nobody can read your body language... hear your pauses... notice your _emphasis_... unless you s.p.e.l.l. it out...
Re:Guide for Technical Development by sukilot on Tuesday May 12, 2015 @04:33PM (#9534653)
Casual sepaking is heard once. Published writing is read many times, and is easy to point edit, so it it worth investing a bit more in correctness.