iamchrisle

There is probably something out there, but I know you can do this in Ableton Live by dragging an audio file onto a MIDI track and it will extract the notes into MIDI for you.

Non-open source products that also separate vocals from music if you need something more "professional".

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.)

Googler here.

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.

I think the saying is "Quality, speed, cost. Pick two?"

Workaround: Make your plugin with settings as you want, then group it so it's inside an instrument rack. Then drag the rack into the browser and into a folder of your choosing.

When you want to use it again, drag the saved rack into your project. The plugins settings will be restored.

No. Keywords do not appear in Google Analytics since search switched to HTTPS. The query strings are dropped going from HTTPS to HTTP. Keywords will show up as "(not provided)"(Disclaimer: I work at Google but I'm not on the search team. I do use Google Analytics.)

Googler here. The free shirts are usually not for employees. They're usually old promotional stuff that are left overs from events held for businesses.

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.

Kinda. Depends on who you ask. :)

There are dedicated and volunteer teams that work on the internal tools and a strong testing and accountability culture. Everything is built from source.

The major build tools are insanely powerful, pragmatic, and maintained by dedicated teams. Volunteers also add features as needed.

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.

This is still how it's done today.

FWIW, Safari (webkit) is mostly working. IE is, unsurprisingly, a train wreck.

I worked at tech startups and small companies since 1998 until I joined Google this year.

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.

Google Tag Manager is great!

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.

Moz is an analytics startup for marketers. It essentially crawls the internet to create a graph of links and reports that in their user interface. They also calculate a score based on the authority of links similar but not the same as Google's Pagerank. They also do social tracking.

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.)

Just a quick note: Moz's domain authority and page authority score is what is used the most in the industry. It relies on their farm crawling the web and seeing who's linking to who. Their business is NOT heavily dependent on Google. Rankings is one of many features.

The .htaccess file is important for SEO. For the context of the blog (seogadget.com), it's worth noting that SEO is more important than performance.

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?

Careful about guest posts. Google has said there's a difference between guest posts and posts that you've paid for (paid linking). See this video from Google:

http://searchengineland.com/googles-matt-cutts-guest-bloggin...

A couple statements to highlight:

"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.

thanks.

I'll let him blog in detail about it but one suggestion I made was that a single page website could be harder to get visibility on just simply in terms of Google search. At least in terms of the people he believe to be his direct competition.

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.

Perhaps I'll nuance: Conceptually, marketing is not hard. But it's very hard work.

Oh yes. Now i recall. Thanks for the clarification.

Because it has to load a virtual frame buffer (Xvfb), the chrome browser, a Selenium server, and then your testing framework. All that adds up to crap performance. There's a lot of pieces that could be simplified with a smaller set of requirements. But like @diminoten said: it's worth it if you have no other choice.

Nice. I would add that Selenium performance isn't super awesome but if you only need to use it for a specific set of integration tests it's OK. You can use something like PhantomJS to speed through the rest your tests that don't specifically need exact browser implementations.

Thanks for the comment. What's Blink? I don't think I've heard of it. I would love to learn more.

I have a 1/2 written post about this exactly. I took it out because it would have made this post too long. But TLDR: I found a few edge cases where using a real browser was easier to use than a headless toolkit. Definitely will be my next post.

This demo had some of the best pacing and flow in the demo scene. Such a classic! It's great to see it open sourced.

TL;DR: Not dead.

Also, he replied to me when we asked him on Twitter:

https://twitter.com/wycats/status/292391457313132544

then clarified: https://twitter.com/wycats/status/292391589643423746

I would agree with this.

Google changes all the time. I would ALWAYS place more emphasis on a great brand name, and great product. At the end of the day, your brand should outlast Google's algorithm changes. You don't want to be on the losing side of an algorithm change.