5 ms·
One humorous side-effect of having all that code viewable (and searchable!) by everyone was that the codebase will contain whatever typo, error, or mistake you
by yongjik 11y ago
One humorous side-effect of having all that code viewable (and searchable!) by everyone was that the codebase will contain whatever typo, error, or mistake you can think of (and convert into a regular expression).
I remember seeing an internal page with dozens of links for humorous searches like "interger", "funciton", or "([A-Z][a-z]+){7,} lang:java"...
- wetmore 11y ago> "([A-Z][a-z]+){7,} lang:java Yeah this one was my favorite of the code search examples, there are some really good ones in there.
- cag_ii 11y agoCan you explain this? It looks to me like a regexp that searches Java source for words 7+ characters that start with a capital letter?
- yongjik 11y agoIt searches for CamelCase identifiers that are made of seven or more "terms", where each term is a capital letter followed by one or more lowercase letters. E.g., ProjectPotatoLoginPageBuilderFactoryObserver. (Disclaimer: I just made it up. Not an actual Google project name.) "lang: java" is not a part of regexp; just a Google code search extension that searches for Java.
- robryk 11y agoThis searches for camelcase identifiers with at least 7 words.
- nandhp 11y agoAnd then you killed off the public version and you keep that fun (and useful) toy to yourself. (But as great as Google Code Search was, my grudge is because of Reader.)
- bubersson 11y agoI encourage everyone to search in their codebase for "1204", "521" and "265" :)