http://humanstxt.org/
google.com/humans.txt
31–40 of 94 posts
Re: google.com/humans.txt
#32Why? Do you have so much spare time to waste on things like this?
Re: google.com/humans.txt
#33humans.txt: everyone: don't poke around /admin don't look in /cgi-bin don't put javascript into the form fields don't make your username look like valid SQL users: don't try to access IDs that you don't own always trust emails that appear to be from us don't look at /pricing#fine_print hackers and security researchers: please stay away lawyers: don't look too closely at /eula employees: don't look at other companies'…
google.txt: don't be evil.
Re: google.com/humans.txt
#34Would love to help them out, if I can get an interview...
The best meritocratic way (i.e. not dependent on your CV too much) to get invited to an interview with Google is to be top 1000 in Google Code Jam. Study algorithms a lot, practice on CodeForces and TopCoder. If you work hard on it, in some year you will be on top of Google Code Jam. Recommendations is good to have but it won't help you to be successful on the interview. Practice algorithms a lot, ... I mean literall…
Do you have any suggestions how to practice algorithms?
Re: google.com/humans.txt
#35Doesn't this implementation actually undermine the whole point of humans.txt? This is the equivalent of a robots.txt file consisting only of comments.
The whole point is to list who is behind the website. A LinkedIn list of people currently working for Google might suffice.
This is the best example of humans.txt: http://nest.com/humans.txt
Re: google.com/humans.txt
#36Why? Do you have so much spare time to waste on things like this?
Spare time wasted on what? Me reading the three sentences or someone else writing three sentences?
Re: google.com/humans.txt
#37http://www.gm.com/humans.txt I never would have guessed it.
Disclaimer: I work at GM. It's probably not as terrible as you imagine. Any opinions are my own.
Re: google.com/humans.txt
#38humans.txt: everyone: don't poke around /admin don't look in /cgi-bin don't put javascript into the form fields don't make your username look like valid SQL users: don't try to access IDs that you don't own always trust emails that appear to be from us don't look at /pricing#fine_print hackers and security researchers: please stay away lawyers: don't look too closely at /eula employees: don't look at other companies'…
google.txt: don't be evil.
Funny, that was deleted years ago, now returns:
"404: File not found."
Re: google.com/humans.txt
#39i was cofounder at a startup a long time ago, and wrote most of the backend code.
i put a humans.txt in there, and updated it every time we had a new employee.
then the CEO fired all the best engineers, and I decided to leave shortly after because sometimes in life you gotta let go.
the company is still (miraculously) around these days, although all of the original engineers are long gone.
the humans.txt is still accessible on their domain as it was on my last day, with all the names of the founding team for the first ~2 years inscribed in there - looks like their newer engineers never stumbled upon it.
sometimes when i get nostalgic i like to hit that URL and look at it
Re: google.com/humans.txt
#40old