iamchrisle
One-click process: Xtrax Stems 2 (https://audionamix.com/technology/xtrax-stems/)
Professional: ADX Trax Pro 3 (https://audionamix.com/technology/adx-trax-pro/)
Both products use a server which have a much larger pre-trained models. The professional one has added features such as handling sibilance, GUI to edit note following as a guide for the models, and an editor tool for extracting using harmonics.
(Note: I don't work for this company. I do pay for / use their products, and I also happen to know someone who works there.)
In general, yes we do practice it. They are guidelines, not rules tho.
Is Angular grossly over-engineered? Depends on how you look at it.
Any code's complexity reflects the complexity of its use case and Angular, for example, needs to fit A LOT of use cases at Google. So yea, sometimes, I think it can be a big hammer for a small nail. In other cases, all that abstraction helps. I guess that's the nature of how code eventually matures over time.
When you want to use it again, drag the saved rack into your project. The plugins settings will be restored.
Also, some Googlers are insanely good at finding out when they're about to get rid old swag.. I'm not one of them, unfortunately.
I do admit, the quantity of Mac power adapters laying around the office is a bit silly.
CitC clients takes seconds, many IDEs work (some better than others with dedicated/volunteers to support), internal GUI based versioning, code reviewing, testing, documenting, bug tracking tools also work at scale.
Looking for a job at Google? We’re hiring coders with 3xp3r13nc3 1n l337
Work is what you make of it.
Interview process: I interviewed at equally big companies like Comcast too. Google's interview process was just as slow as other big companies. Seems to be normal when you get to that size.
Management and structure: Your experience working there, like anywhere including a startup, will greatly depend on who your manager is. My manager is great and actively encourages me to step up my game.
Work/life balance: Google gives you a lot room to do the work that you're excited to do but that comes at a price: Self-regulation. If you're not good at it you WILL burn yourself out. But that's not any different than my last startup. I've seen it in startups too.
Personally, having a great time, learning a lot very fast, and happy. Of course, your millage may vary.
Pros: - It's good at dealing with older browsers - It's async (non blocking) - Simple to implement - No dependencies
Cons: - UI is simple but workflow is a little confusing at first - Not "plug-and-play". Still requires a little working knowledge about Google Analytics.
Technical details:
I don't know exactly how they do it but my guess is that they are I/O bound on the crawling side, then CPU bound on the parsing and processing side. I'm assuming they use different machines for those tasks.
On the crawling side, the index with 60-70 billion URLS was using 80 cc2.8xlarge machines with a backup on 200 c1.xlarge machines. (http://moz.com/blog/one-step-back-two-steps-forward)
(DISCLAIMER: I'm in the same industry. I am a developer with working for an indirect competitor. I know a few engineers and non-engineers who work at Moz.)
The .htaccess is used to 301 redirect www.bennet.org to bennet.org. Important for SEO so that Google only indexes one domain instead of the domain and the subdomain. Only indexing one domain gives it a better chance of ranking higher.
Also.. do you really think the traffic and 453k of bandwidth is really going to put any strain on performance?
Using A Microcontroller To Keep Your Plants Alive
5 Things You Might Not Know About IntelliJ
http://searchengineland.com/googles-matt-cutts-guest-bloggin...
Enumerated types can get in the way of fast and safe iteration
"because I see too many good products die because whoever built it never got it out to the right people."
- yes. Great ideas DESERVE to be found!
"difficult as a marketer discerning who is a gifted programmer and who isn't"
The street goes both ways. I would say that it's easy to fool a marketer into thinking you're a rockstar programmer.
"there is a long, long learning curve if you're going to do it well."
Well said. I still personally think it's more difficult -- maybe not conceptually, but it's terribly labor intensive and unpredictable.
If he's looking to attract specific types of developers he should consider create pages targeted to those developers. So those pages would get indexed for the specific developers who are searching for a jira/github/fogbugz tracking app.