Try: https://www.google.com/killer-robots.txt Discussion: https://news.ycombinator.com/item?id=7988924 and https://news.ycombinator.com/item?id=7979909
haha awesome :]
google.com/humans.txt
51–60 of 94 posts
Re: google.com/humans.txt
#52Doesn'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
We list out our product team: https://esharesinc.com/humans.txt
It's the first pull request new product people submit: adding themselves to humans.txt – works really well.
Re: google.com/humans.txt
#53https://www.facebook.com/humans.txt
i knew Zuck was a robot!
Re: google.com/humans.txt
#54http://booking.com/humans.txt
(Disclaimer: I work at Booking; opinions my own)
Re: google.com/humans.txt
#55i 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 acc…
Is it really that easy to miss an errant text file in the site directory? I'm so meticulous when it comes to code that you couldn't possibly get that past me.
Re: google.com/humans.txt
#56Earlier quoted context omitted.
Try twtxt.txt
To help others before they try it, it's a 404
Thanks and sorry, just thought it might fit, twtxt being ...
Decentralised, minimalist microblogging service for hackers. http://twtxt.readthedocs.org/en/stable/
Re: google.com/humans.txt
#57Earlier quoted context omitted.
have someone that works or has worked there vouch for you. I've had a google recruiter contact me on that alone.
It's probably the easiest way to get an interview for most companies.
But the question is, are you going to pass the interview? Getting an interview is the easy part - I've gotten two Google interviews so far just from recruiters and a friend recommending me.
Re: google.com/humans.txt
#58Would love to help them out, if I can get an interview...
To be very honest: don't waste your time It is certainly a common desire of a lot of people to work there. And it certainly can be achieved if you have the technical skills But the advantages of a position are overrated, and the disadvantages, underrated. Certainly, not everywhere you can work on Google sized problems, but other place have interesting problems as well, and you'll feel your work to be more valued
Speaking as a former Google engineer? I know a few disillusioned Google engineers :) Just understand from the outside looking in the company is still very much tantalizing. Most companies worth working for these days have a similarly stringent interview process so I can't see what the disadvantage would be of upping your technical skills.
Re: google.com/humans.txt
#59http://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.
Not bad! Don't let the marketing team find it.
Re: google.com/humans.txt
#60Earlier quoted context omitted.
To be very honest: don't waste your time It is certainly a common desire of a lot of people to work there. And it certainly can be achieved if you have the technical skills But the advantages of a position are overrated, and the disadvantages, underrated. Certainly, not everywhere you can work on Google sized problems, but other place have interesting problems as well, and you'll feel your work to be more valued
Speaking as a former Google engineer? I know a few disillusioned Google engineers :) Just understand from the outside looking in the company is still very much tantalizing. Most companies worth working for these days have a similarly stringent interview process so I can't see what the disadvantage would be of upping your technical skills.
> Speaking as a former Google engineer? I know a few disillusioned Google engineers :)
Not former nor current. Me too!
And yes, the Google interview process made me aware of some (important) blanks in my knowledge
At the same time they ignore the "incidental" talents and knowledge of people in their process (a lot of times, technical knowledge).
I also compare what they're doing with what people that got turned down are doing