36 | Jeff Byer – Chrome Dev Tools, Shopify, CCPA and Tech Talk

Today Jeff Byer (@globaljeff) talks about his experiment with workspaces in Chrome Dev Tools, the Shopify universe, upcoming project launches, real-world project issues, and tech talk.
Show Links
Chrome Dev Tools – Workspaces https://www.hongkiat.com/blog/google-chrome-workspace/CCPA – https://oag.ca.gov/privacy/ccpaFact Sheet, pdf
Transcript
Jeff Byer    00:06    Welcome to digital rage, the podcast about all things internet and the people that make it great. My name is Jeff Byer and I know last episode I have promised you guests but uh, that didn’t happen. You know, people are busy, things are happening and uh, you know, just didn’t get around to it. I did have an interview scheduled, we had our <inaudible> in our call  
Jeff Byer    00:30    and there was a misunderstanding. This a, I believe a the person involved was expecting some sort of a uh, you know, get to know ya. Uh, cause I sales call and I was expecting it to be an interview. So a little bit of a miscommunication. But um, anyway, I do have a ton of things to talk about. So this will be an episode full of stuff. I like to say stuff because some of it is crap set of, some of it’s not. So let’s get right into it. First thing is I was playing around and in Chrome and, and the dev tools and just futzing around and came across the workspaces in dev tools and thought, okay, this is interesting. Why would, why would they have a, you know, invite somebody to put their file structure inside of Chrome dev tools if it doesn’t actually make any live, live edits as you go.  
Jeff Byer    01:41    Because as most developers know, whenever you get to a live website and you go into dev tools, you can modify all of the code you want and change the display of, of that website. You know, change the content, anything you want, run experiments, even if it’s not your site but only you can see it. And as soon as you close dev tools or refresh the page, all those edits are gone. And it goes back to the way it is on the live server. And I do use that sometimes to one. If I’m trying to get a screenshot and I want to modify things for the actual screenshot, I’ll go in, remove modules, remove ads and stuff like that. But on my own sites, I use it just to play around and see, you know, if there’s something visually or content wise that I want to accomplish, how fast it would be to make that adjustment and just kind of play around in dev tools before I open up, uh, you know, my editor editing environment and go ahead and go through with the change.  
Jeff Byer    02:45    It also helps me to, to create estimates on what it’s going to take to accomplish certain things requested by my client. So I get into this and I’ve read a couple of articles and I go through the Google tutorial on how to use Chrome tools and the whole time, uh, I’m going through these tutorials and obviously it says, okay, you know, it’s, you’ll be able to save the changes if you use it in, in your local environment and you add your local pho folder for that environment. So I was like, okay, that’s fine, but it, uh, it’s very limited and uh, I didn’t see any way if you are going to use a SAS or any type of, of pre compiler that it just didn’t have a way to really integrate those unless you had another third party script going. So the whole time I’m going through this tutorials, like who the hell would use this?  
Jeff Byer    03:47    It’s just basic. If you had a basic site with no preprocessing prop, pre-processing, no minification and uh, just static something, I don’t even know what, um, that’s what you’d use. So I went down a rabbit hole on that and found myself completely disappointed. So moving on. Um, so today I added an