CS 373 Fall 2019: Travis Langston
Week of 10/28–11/3
- What did you do this past week?
This past week I went up to Dallas for an onsite interview on Monday and Tuesday, which ended up going pretty well. I should be hearing back from them this week, so hopefully I’ll be able to wrap up this internship search shortly. I also finished my compilers project on Tuesday and then spent the rest of the week grading exams and projects for OOP and getting caught up in Chemistry since I have an exam next week. Lastly, I registered for the spring semester on Thursday and for the first time was able to get into all of the classes I wanted.
2. What’s in your way?
Right now I’m just behind in a couple classes because of interviews and all of the projects that were due in the past few weeks. I just need to spend some time catching up this weekend and then hopefully the rest of the semester will be better since I won’t have as many due dates clustered together over a short time period.
3. What will you do next week?
Next week I will mostly focus on preparing for my chem exam and on finishing up phase 3 for this class. We still have a couple leftover issues from phase 2 that we need to fix so I’ll probably end up spending quite a bit of time on that. Other than that, I just need to work on getting started on the next compilers project since the next two are supposed to be the most difficult. In addition, I need to work on figuring out my idea for my second virtualization project so I can get started working on it soon.
4. What was your experience of SQL?
I enjoyed the lectures and exercises on SQL. So far it seems pretty easy although I definitely need to spend some more time practicing it before the next exam. Hackerrank and Leetcode both have some additional SQL practice problems so I’ll probably spend some time working through those in the future.
5. What’s your pick-of-the-week or tip-of-the-week?
My pick of the week is the tool Mozilla rr: https://rr-project.org/. I find it really helpful for debugging code since it allows you to record the execution of a program, including the values of the registers at each step and any signals the program receives, and replay it in GDB so you can then step forwards and backwards through it’s execution. This makes reproducing errors a lot easier and greatly speeds up the debugging process.

