CST 370 - Week 5 - Quick Sort and finding a pattern

Reading about quick sort and median of three partitioning really reminded me of the fake coin puzzles we solved. And in some sense they are very similar -- efficiency is about dividing and conquering. Breaking something down into smaller pieces. Rather than doing exhaustive comparisons you split a large problem into smaller halves. These smaller steps allow for less cognitive load and a quicker solution overall.

Median of three partitioning does the same. We look at the first, middle and last. And working with sub arrays allow us to sort much faster.

It seems like a lot of this class, and finding efficiency is about finding a pattern to break something down smaller than as presented. It's an interesting concept I hope to bring elsewhere.

Comments

Post a Comment

Popular posts from this blog

CST 363 - Week 3 - SEE-QWILL or ES-SKEW-EL

Should it be pronounced SEE-QWILL or ES-SKEW-EL ... who knows? Maybe it's like GIF. Potato Tomato. 1. An SQL view is a virtual table whose contents are defined by a stored query. I think of it as a saved SELECT statement that I can interact with as if it were a real table. It's similar to a table because it has rows and columns, and can be queried SELECT to simplify retrieving complex data. However, it's different because a view doesn't store its own data—it just displaying data from the underlying tables. Which sort of makes sense since views don't have their own primary keys. 2. It's hard to compare SQL to a language like Java. Java has a lot more flexibility in data structures. Also Java works synchronously (well unless you count multi-threading) so it's processing data one at a time versus SQL which is fundamentally different under the hood. That said SQL is a lot more "clear" and I think the nature of queries is a lot more determinant than so...
Read more

CST 338 - Week 4 - Legally Distinct Learning Journal

I worked with Branden from my team. With this assignment (and with most assignments) I always try to work directly off the prompt, filling out each defined method from the UML diagram of the assignment. Once I feel good about implementation, I use the unit test as a guide to help debug and get each function fully ironed out. Afterwards I go back in, format and clean up variable names and add single line comments for clarity. Through this process I am working through the logic in my code 2-3 times which leads to a cleaner output. Branden mentioned his strategy was, “For Project 1, I took it one step at a time. I started with the Monster class and followed the prompt closely, making sure each method matched what was expected, especially with things like output formatting and phrases. I tested as I built each part, and when something didn’t work, I used the error messages to figure out what needed fixing. I created each monster type one by one and kept everything organized using Git branc...
Read more

CST 338 - Week 2 - Stuff You Should Know

Week 1 was a fun week that jumped right into some good coding exercises in Java. It touched upon a bunch of different themes like basic Java, Unit Tests, Git, Interfaces and more. I could probably write a lot about how much I fought with IntelliJ (let's be honest it's not the best) but will touch on more substantiative topics. First let's talk about unit tests. I know JUnit would not be considered a first-class citizen, but the way it is autogenerated by IntelliJ is quite sleek. In that sense writing unit tests and running them is extremely easy. We often read about TDD (test driven development) as a paradigm some organizations use, and building out tests in Java for our exercises really makes me see the value for that approach. Not only does it verify the output for a given input, it also helps us write our functions in a more ... well functional kind of way. I would argue that if you can't write a unit tests, that may actually be a code smell more than anything else. ...
Read more