Code Golf at Google
blog.zmxv.com
Code Golf at Google
1–10 of 38 posts
Re: Code Golf at Google
#2>http://go/codegolf
How does this work, some sort of TLD magic? (That shouldn't be possible, right?) Is it just routed within Google's internal network?
Re: Code Golf at Google
#3> http://go/codegolf How does this work, some sort of TLD magic? (That shouldn't be possible, right?) Is it just routed within Google's internal network?
I'd assume the same way localhost works on your computer.
Re: Code Golf at Google
#4> http://go/codegolf How does this work, some sort of TLD magic? (That shouldn't be possible, right?) Is it just routed within Google's internal network?
[deleted]
Re: Code Golf at Google
#5> http://go/codegolf How does this work, some sort of TLD magic? (That shouldn't be possible, right?) Is it just routed within Google's internal network?
It's probably resolved by the internal network DNS. You can do the same even with your home router.
Re: Code Golf at Google
#6> http://go/codegolf How does this work, some sort of TLD magic? (That shouldn't be possible, right?) Is it just routed within Google's internal network?
By default foo resolves to foo.mydomain.mytld (man resolv.conf, section domain), so as long as the machines are configured with a local domain, this will work.
Re: Code Golf at Google
#7i think the sad pattern I see in a lot of these code golf implementations is the solution score is based on Lines of Code, which we already agree is a POOR representation of either complexity or simplicity.
I think it would be far more interesting to measure number of instructions to complete the objective. Though I suspect the folks familiar with assembly would run circles, perhaps you could segment by solution language?
Re: Code Golf at Google
#8> http://go/codegolf How does this work, some sort of TLD magic? (That shouldn't be possible, right?) Is it just routed within Google's internal network?
It works the same as any other corporate network: either custom DNS resolution on the machine (i.e. /etc/hosts), DNS resolution in the internal network, or DNS resolution on the VPN. Or, more likely, a mix of the 3.
To get to go links, you've got to be connected to Google's network (either physically, or through VPN). It's essentially the same as accessing a computer on your LAN with its host name (in which case, the router can do the DNS lookup and resolution for the internal network).
Re: Code Golf at Google
#9i think the sad pattern I see in a lot of these code golf implementations is the solution score is based on Lines of Code, which we already agree is a POOR representation of either complexity or simplicity. I think it would be far more interesting to measure number of instructions to complete the objective. Though I suspect the folks familiar with assembly would run circles, perhaps you could segment by solution lang…
You are not describing code golf, though. "A sad pattern in chess is checkmate; the goal should be to eliminate the other player entirely."
I agree what you describe would be fun, too, but it isn't code golf.
Re: Code Golf at Google
#10> http://go/codegolf How does this work, some sort of TLD magic? (That shouldn't be possible, right?) Is it just routed within Google's internal network?
Search paths. The full address is go.corp.google.com (which is simply a URL shortener), IIRC; however, I think the resolvers are also configured to respond to a bare name in a lot of cases as an optimization. They talk a little bit about corp in their BeyondCorp paper[0], which is well worth a read, and I'm speaking to ancient memory so I might be wrong these days.
[0]: http://static.googleusercontent.com/media/research.google.co...