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.

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.