You're listening to coding blocks episode 132.

subscribe to us and leave us a review on iTunes Spotify,

Stichur and more using your favorite podcast app and stop trying to mess me up. I see you guys talking

and mimicking me and mocking me as I do this. It's not what it work. You didn't trick me up. I don't know what that outworks was about. We'll just keep going though so you can visit us

that you could be less on. We can find shown this discussion in the table a lot more and if

keep that questions rans can be sent to comments at

couldn't boss dot net. So if you speak in a language other than English or any

known language demand then nobody else can try and act like they're speaking like

you so follow us on Twitter at nobody else can try and act like they're speaking like you.

So follow us on Twitter at coding blocks

or head to W.coding.net

and find all our social links there

at the top of the page with that.

I'm Alan Underwood. I'm Joe Zact and I'm Michael

Outlaw. This episode is sponsored by the University of California Irvine

Division of Continuing Education one of the top 50 nationally ranked universities UCI offers

over 80 certificates and specialized programs designed for working professionals. And Data Dog, a cloud scale monitoring and analytics platform that unifies metrics, traces, and logs so you can identify and resolve performance issues quickly.

All right, and hey, today we're talking about some Google engineering practices and we're going to tell you

what that's about in a minute here. But first we got a little bit of news and as we do got to say huge thank you for

everyone that let us review got a couple names to shout out here from iTunes

thank you J. Barger, podcast devour. I dig it. And, uh,

Darachi, thank you so much. And from Stitcher, we have Diamond C.

...