Hello and thank you for your comment! The other videos in this series are as follows: 1. Intro and Linear Search: kzbin.info/www/bejne/q3-VooKul7qBnZo 2. Binary Search: kzbin.info/www/bejne/gaLWlHWkg6aFkMU The series just has these three videos!

You're welcome! Very happy to be of help =)

Hello and thank you for your comment! Looking back at this, it does look horrible.... I probably used an ISO in the range of 800 - 1200, then brightened it up further in post. The compression didn't help either, even the screencapture parts look bad now. Heh, if anything this gives me an excuse to go back and redo some of my earlier stuff!

You're welcome! Glad to be of help =)

You're welcome! Glad to be of help =)

You're welcome! Glad to be of help :)

Hello and thank you for your comment! While this is a sound summary I think it also makes a few more assertions than I have in the video - The recursion isn't converted to iteration (at least, not necessarily). It simply doesn't have to keep the call stack populated as meticulously as if we are doing a series of function calls. I also make no statement about the size of the executable - That's again dependent on the approach of the compiler.

Hello and thank you for your comment! Glad you liked the video :)

Hello and thank you for your comment! Alt Gr is used to type additional characters and symbols, if the operating system has been set up for it (more info here: en.m.wikipedia.org/wiki/AltGr_key) I don't believe it can cause the problem you describe.

You're welcome! Very happy to be of help =)

Hello and thank you for your comment! Glad you liked the video =)

You're welcome! Very happy to be of help =)

Hello and thank you for your comment! I'm assuming this question is in the context of Blender, which I used in the video. Different software work differently. 1. In Blender, ensure you're using the Eevee renderer. Go to "Render Properties" (camera icon) → Render Engine → Eevee 2. Construct your scene. Additionally, add a reflection cubemap. Shift+A → Light Probe → Reflection Cubemap 3. Scale the cubemap so it covers your scene. 4. Under "Render Properties" (camera icon), pop open the Indirect Lighting menu and click "Bake Indirect Lighting". This should render and apply the cubemap. Screenshot for reference: i.imgur.com/dtSqxzn.jpeg While you're on that screen you might want to try enabling "Screen Space Reflections" as well. This tends to be a better approach than cubemaps, at the cost of a bit of extra computation.

@@NERDfirst Thanks so much for your time to respond me! This is going to level up my texturing process!

You're welcome! Glad to be of help =)

You're welcome! Very happy to be of help =)

Hello and thank you for your comment! This isn't a use case I have much experience with I'm afraid, because this involves cross-process communication which is generally a can of worms. Have you considered using libraries that can help you "talk to" FFMPEG directly from within Python code? I haven't really tried any of them either, but here's one that might be of interest to you: github.com/kkroening/ffmpeg-python

You're welcome! Glad to be of help =)

Yes! Not actively making videos but still alive in the comments section :)

@@NERDfirst have a good year, best wishes to you and your family

Thank you very much! Have a good year too =)

Hello and thank you for your comment! I only use Creative Commons / Public Domain licensed soundtrack, so it's entirely possible that you might have heard them in other videos or even in video games! The main theme of this shown is "Blown Away" by Kevin MacLeod: kzbin.info/www/bejne/rHXcdX53qdtnkKc Theme at the end is "Outro" by boringXtreme: kzbin.info/www/bejne/nIq7aGZoqpmXhpo

Hello and thank you very much for your comment! Yeah, I think some of the options are definitely more intuitive than the others, so understanding what they actually do can help in figuring out which best to use! Glad you liked the video =)

Hello and thank you for your comment! Ghost, also known as wind! I have a fan going.

Hello and thank you for your comment! Glad to be of help =)

Hello and thank you for your comment! What you've described sounds correct (though note that strictly speaking it's chain -> data. The chain pin sends the overflowing bit out of the shift register and into the next). You'll need one shift register to select rows, and two to set column values. How you order them is actually up to you as long as the code follows the order. If you were to do something like (Columns for Left Matrix) -> (Columns for Right Matrix) -> (Rows for both), then your shiftOut code should follow the reverse order: shiftOut(DATA_PIN, SHIFT_PIN, LSBFIRST, 0b00100000); // Select a row shiftOut(DATA_PIN, SHIFT_PIN, LSBFIRST, 0b10101010); // Left matrix graphic on row shiftOut(DATA_PIN, SHIFT_PIN, LSBFIRST, 0b10101010); // Right matrix graphic on row store(); // Send out your updates to the LED matrices

You're welcome! Glad to be of help :)

Hello and thank you for your comment! Yeah, I see where you're coming from. It can definitely be a sign of the golden hammer antipattern. Having said that, in the real world some situations may call for doing this (eg. already having an existing codebase and not wanting to spend the time to convert it, or wanting to have a cross-platform solution). Plus, I wouldn't necessarily say that HTML isn't designed for GUI. I've used both TkInter and JavaFX a fair bit and I'll say It's just another approach for doing GUI. They all have their learning curve and pros and cons. I don't think any user of tools like Eel, Electron or Cordova that wraps a web application as GUI for a standalone program would deny it's a hack. Sometimes it's just the path of least resistance and the time saved from doing this could be used in better ways.

Hello and thank you very much for your comment! Glad you liked the video :)

Hello and thank you for your comment! Yes, if you have a 16x16 LED matrix and you stick to the same 8-bit shift registers, you'll need four of them. However, Arduino's shiftOut() is designed to work with bytes (8 bits), so realistically, you're going to either have to call shiftOut() twice to shift 16 times, or you'll have to roll your own equivalent function. By the way, that's a 16-bit number you're looking at, so the range goes up to 65535, not just 511!

Heh, yep, made it my entire brand!

Hello and thank you very much for your comment! No professorship unfortunately, but I _do_ start lecturing at the degree level next year :)

where at???

Well, I'm based in Singapore so I'll just say it's one of the private universities here. Don't think I want to say any more than that on the internet!

Hello and thank you for your comment. Yes, zip bombs can be dangerous anywhere, as long as the software decompressing it doesn't correctly guard against this and "unpacks" the archive indiscriminately. Legitimate applications will not contain zip bombs, so there isn't a "real function" so to speak. These are exploits on compression algorithms designed to cause crashes and disrupt regular operation.

Hello and thank you very much for your comment! Glad you liked the video :)

You're welcome! Very happy to be of help =)

Hello and thank you for your comment and support! Glad you like my work =)

You're welcome! Glad you liked the video =)

You're welcome! Very happy to be of help =)

Hello and thank you for your comment! Glad you liked the video =)

Hello and thank you very much for your comment! Glad to be of help =)

Thank you very much for sharing! Both are FOSS as well, which is doubly great! EDIT: Comment pinned and links to the two programs added to the description!

Hello and thank you very much for your comment! Glad you found the video useful =)

Hello and thank you for your comment! Yes indeed, lots of pretty smart features!

@@NERDfirst just realised it was 9 years ago sorry lol

Hello and thank you for your comment! Unfortunately command-line interfaces aren't for everyone. Not to mention that video encoding is a complex topic as well. If you're looking for a non-command line equivalent, you may want to consider software like Handbrake. I haven't used it myself but people seem to like it!

@ too late, I figured it out

Hello and thank you for your comment! If you're talking about being "insane" at CS, that takes time. One year isn't much in the grand scheme of things. There's a long-time saying that it takes 10000 hours of practice to become at expert at something. While this is debated, it hopefully helps define the scale of the amount of effort required. There's another point to make as well - I didn't come up with this algorithm. Most people use algorithms invented by someone else. In Computer Science, many things fall into "standard patterns" that can be addressed by pre-existing algorithms. It sounds like you're a second year CS student, so you might not have had many chances to look into the standard Data Structures and Algorithms that exist out there, but that'll come.

@@NERDfirst right now im doing DS1 also how do u think like a programmer because for DS im thinking kinda visually

There's nothing wrong with thinking visually. A lot of the time, we actively encourage it as a teaching/learning tool. In fact many algorithms like Linked Lists, Trees and Graphs actively require you to visualize an abstract problem in graphical terms. It's only an issue if you find that you can't "convert" the pictures in your mind to an algorithm. That typically indicates that your fundamentals aren't strong enough and you might need to revisit concepts or get in more hands-on practice so you can improve on your computational thinking.

@@NERDfirst how about you how do you think like a programmer ?

Honestly, I don't go out of my way to think about things in a special way. A lot of Computational Thinking frameworks will list techniques like problem decomposition, and pattern and abstraction recognition. I realize that I apply a lot of these subconsciously, but actively trying to do them in a vacuum can also be challenging. You can read up more on the topic of Computational Thinking if you're interested, but again, I don't feel that thinking about these techniques in the abstract are really helpful. At least, not more so than just getting the practice in. Start with very simple problems and work your way up.

Hello and thank you very much for your comment! Very happy to be of help, and you have a great day too =)

Hello and thank you for your comment! Good point, I don't think I ever explicitly defined the two terms. Here's my definition, which I hope helps complete your understanding: Sampling refers to taking periodic measurements of a signal. Typically, we would sample an analog signal, allowing the samples to be saved digitally, with the intent of recreating that signal using those sample points. Sampling rate simply refers to how often each sample is taken. It is measured as the number of samples taken per second, with the unit Hertz (Hz).

Thanks for sharing! Scrcpy has a bunch of useful keyboard shortcuts that I can never remember.

You're welcome! Glad you liked the video =)

You're welcome! Glad to be of help =)

Hello and thank you very much for your comment! Glad to be of help =)

Hello and thank you for your comment! This isn't generally something that can be easily done. I wouldn't be surprised if even calculators use approximations or look-up tables. But if you wanted to do it anyway, the method is described in detail here: math.stackexchange.com/questions/4680996/find-arctan-without-calculator