Transcript
Hello everyone welcome to another day of the Jim.
June 20 A couple hours late um June 22,022.
I the last thing that's been on my mind has been recording these episodes this week, last couple days, I've just I've been so buried in code and.
You know there's, I don't know if you've ever coded before or done web development but there is this.
It's kind of balancing of two worlds, I would say one of them is maintaining a very high level abstraction of trying to figure out um kind of where things are located in this virtual space. It seems to require a lot of working memory. Okay, this happened, I did this here and that here in this year. Okay. And I'm trying to imagine the structure at this level. If I have this structure here then this could work over here and that could integrate with this. Um I found that writing down, writing it down sometimes helps, but regardless just this idea of. Contemplating something at a very high abstract level and and frankly trying to abstract things up to higher and higher levels. Going into different level programming. You have, there's object oriented programming where you're trying to come up with different types of classes, which is kind of like nouns, and then you have methods or functions which are kind of like verbs and you have all sorts of things like this. So 1 1 aspect is being thinking at a very high level, I would say. Then there's another aspect which is almost the complete opposite. And this is the one that I think plagues me a lot of times. It's the little details, ah the little details like missing a semicolon or, trying to check this one today was trying to say, oh it's not working. The code is fine. Why is the site not working? Oh, it's not working because. The code. I didn't upload the code to the website, I was just using it on my computer. So the code was only on the computer, but it wasn't working on the website, that's why, because I didn't upload it. Okay. And I can't tell you how many times I've come across certain details like that. I think it's one of the things that pushed me away from coding when I was in school where I was just like, oh my gosh, how many hours do I have to spend in the basement of this engineering lab at the University of Illinois? I think of Sun Microsystems computer trying to find that semicolon. Oh, now it's a lot easier with some of the the software to develop, but it was not. Uh but so anyways it's just this balance of I think thinking at a very high abstract level and also thinking a very low detailed level, which may be why a lot of people don't go into it. But you know, I wonder if there are parallels in other fields. I mean, does this happen in in the medical industry, Does this happen in accounting? Does this happen in a carpentry? Does this happen in so many different fields? In teaching and education and in health care and landscaping and all sorts of fields? Is there that level of very high level abstraction and going down into the nitty gritty details a lot? I don't know. I would assume so, but I wonder if it's as extreme the computer is if you make one little mistake, it doesn't work a lot of times you miss that semicolon and parentheses and the whole thing fails. Um but at the same time if we can't abstract it, put the thing in place, it can struggle as well. I don't know. So I wonder if.
Things that seem so incredibly specific to a field actually are quite translatable. So if if you're in an industry that's not computer programming and you've experienced such high level abstraction and need for intense focus on details. I'd love to hear about it because I think that pattern probably shows up a lot more than I or others may think it does and I am running out of voice because I'm tired. Another thing about coding is like realizing, don't breathe too much and I'm thinking so so quickly and everything like that. Anyways.
Okay, well I will talk to you tomorrow. Bye.
No comments yet