CST370: wk 7

 This week we went over dynamic programming for collecting coins on a grid and Floyd’s algorithm for finding all-pairs shortest paths. The coin problem was pretty cool because it wasn’t just about getting the max coins, but also figuring out the exact path to take, and having to follow a weird tie-break rule where you pick left over top if they’re equal. Floyd’s algorithm made sense once I thought of it as letting more “stops” into the route one at a time and checking if that made a shorter path. I also got some practice handling -1 as infinity in the input/output. Overall, I feel like I’m getting more comfortable with DP grid problems and shortest path algorithms, and using Scanner in Java made the code way easier to read.

Comments

Post a Comment

Popular posts from this blog

CST 363 Wk7:

 I 100% prefer MongoDB, it's very intuitive compared to SQL statements, since it's more modern.   Some similarities are the CRUD operations, which makes going from SQL to MongoDB easy to handle. I do like how flexible the data is stored in MongoDB rather than SQL.
Read more

wk2: Trust the Process

 In the year 2012, Kobe Bryant was having a season filled with injuries and ups and downs, but confidently he said to "Trust the process" in order to achieve his goal of another NBA championship.  While he wasn't able to get this sixth championship, his saying still lives on.  Though I'm sure Kobe wasn't aware that trusting the process lies within our computers that allows them to perform whatever we tell them.   I've learned the interesting bits about how the OS manages processes through the fork() and exec() commands, which appear simple but allow the OS to perform multiple processes.  I later learned about how the OS manages permissions between the user and kernel, so the user can temporarily access higher permissions through the use of traps. Also fun to think about the potential of traps if one were to gain access, they can run malicious code.
Read more

CST334 - OS - WK1

 The first week of CST334 has been interesting, since I've always wondered how computers bridge the gap between hardware and software, and it seems like the OS is the glue that holds it all together.  I remember back in the lower division course of Computer Architecture, the professor spoke about how data is placed in memory and seeing where in the memory this information is being stored.  He was careful to point out that the memory address that was seen is not exactly the hardware memory address because of virtualization.  Then in the first week of this course we were exposed to virtualization to see how the OS manages the flow of information.  I find that all the computer things I've learned in the past through online tutorials like setting up linux machines, etc, are coming together, to understand why that command I copy and pasted to change file permissions are actually doing!
Read more