CST 370 - Week 1 - 8 Coins but every single day

The example of the 8 coins problem (9 coins in our quiz), was really interesting and pretty mind-blowing. My initial instinct was binary search, or halving the pile until I found it in three weighings. But there’s a faster way. By initially dividing them into groups of three, you can find the fake in just two steps.

This was a really interesting and practical example that made me think about efficiency in the real world. Algorithm efficiency isn't just textbook theory ... it’s about optimizing problem-solving. 

I feel like I actually execute algorithms unconsciously all the time. For example when I lose my keys. I don't look at the whole house randomly, I retrace my steps backward, eliminating irrelevant search spaces just like an efficient function. Overall it's exciting to jump into class and I'm excited to see where else I can make my own thinking more efficient.

Comments

Post a Comment

Popular posts from this blog

CST 300 - Week 4 - Writing With Purpose

  Part One One of my ultimate goals with the CS Online Program is to have a better foundational understanding of computer science concepts. I have years of experience building applications at scale, but am excited to learn more about key concepts. Specifically CST 370 and being able to better understand algorithmic efficiency and complexity. Being able to apply those concepts to commonly used data structures or database queries will help me feel more confident in decisions I am making at work. With a CS Degree in hand, I plan to continue my education and go for an MBA. This should help to round out my business acumen and help me land the leadership roles I’d like to obtain in the future. Part Two My career goal is to be a Director Level leader at a Fortune 500 company. Simple right? Truly I believe this program, along with an MBA will help me qualify for this. I already have the requisite experience, so the education is the last piece! Part Three Hard to say, I feel as if I took it...
Read more

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 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