Monday, Monday, day, open wide dev fans, get ready to stuff your face with JavaScript CSS,

Node modules, barbecue tips, get workflows, break dancing, soft skills, web development,

the hastiest, the crazyest, the tastiest, web development treats, coming in hot, here

is Wes Barakuda, Boss and Scott El Torro Lugo, Tolinsky.

Welcome to syntax in this episode, episode number 668, we're going to be talking about

proxying, intercepting and debugging traffic. And this could be any traffic on your network

really is what it comes down to. My name is Scott Tolinsky, I'm a developer from Denver,

with me as always, is Wes Boss. Wes, what's going on my name?

Yeah, I am excited to talk about this because you came to me with a really cool story.

I'm not going to spoil it because we'll go over it in just a second, but I too have tried to

intercept traffic that comes from hardware, software, applications, desktop apps,

being able to intercept requests and peer into what data is being sent.

So what we're going to do today is go through why you might want to do it, both as a developer,

as well as a hacker, not like a nefarious hacker, but someone who likes to poke at this mind.

Yeah, curious mind, exactly, gray areas, as well as different applications you can use to

sort of peer into it. Because if you've ever had a piece of software or hardware,

and you hear people, oh, they're sending your traffic to x, y, and z, you literally can check.

And we'll go through that and how to do that today.

Yeah. And speaking of debugging, this podcast is brought to you by century at century.io.

Use the coupon code, tasty treat, sign up today and you'll get two months for free.

So yeah, let's talk all about all of the stuff. Do you want me to start with my story or do you

want to start with the web proxies thing? No, start with your story because they think that

...