CS373 Fall 2020: Jackson McClurg

Jackson McClurg
2 min readSep 27, 2020

Blog 5

  1. What did you do this past week? This past week I spent a lot of time on career fair and other related things. I also spent some time trying to learn the tools I’m going to need to work on our team project. The majority of my time in the next few days is going to be shifted from recruiting to my team and what I need to do in order to be in a spot where I can help and contribute to my team.
  2. What’s in your way? Last week I’ve been dealing with a housing issue and I’m not sure where I am going to be staying at in a few weeks. Right now I’m having a bit of an internet problem as well but I think I’ve got it managed to the point where I can do what I need to get done. I also don’t have much web development or scraping experience so I have a lot of learning to do for our team project.
  3. What will you do next week? Next week I am going to be working on this project and others, trying to make the most of the time that I have available. I’m also going to continue learning about the tools I’m using and work on developing those skills as well.
  4. What was your experience of types, object models, and iterators? (this question will vary, week to week) Types were pretty straightforward to me. In Python, all data is represented as an object or a relationship to an object, and iterators provide a useful way to allow different instances access an object without having to duplicate the object many times.
  5. What made you happy this week? This week I played Among Us with my friends and I had a really good time. If I get my work done next week and I’m in a good place I would like to play it again. It’s a really good time if you have enough people that you know that you can play with, and it’s free!
  6. What’s your pick-of-the-week or tip-of-the-week? My tip-of-the-week is to draft out what you want to work on before actually beginning to code. Get an idea in your head of what you want to do, and then write down on paper how you’re going to go about implementing it. This can save you from a lot of headaches and can help you realize ahead of time if your idea can actually work or not. Once you get it down on paper and are confident that it will work in code, then start working on your computer.

--

--

Jackson McClurg
0 Followers

Hi, I’m Jackson and this is my weekly blog for Professor Downing’s SWE class!