I would ask yourself what an algorithm really is. It's not just sorting or searching. It's really just a recipe of things to do in the order you have defined th

I would ask yourself what an algorithm really is. It's not just sorting or searching. It's really just a recipe of things to do in the order you have defined them to get an end result. Pretty much every web dev related thing you make is an algorithm at the end of the day. Think of something as simple as a contact form. What's the algorithm to make this work? 1. Get input from user. 2. Validate input from user. 3. Setup mail headers. 4. Setup mail message. 5. Call a send message function. Those steps can be expanded on to handle invalid input or errors in any of the steps, etc.. Your programming language will likely have #5 done for you too, but whether or not you're the one implementing the functionality has no bearing on the situation. It's easier to teach the material when you're dealing with basic data structures like building a stack or queue in C using an array rather than some higher level web dev task. Btw, I'm just someone who spent a few years not taking any CS courses and then took a few online courses to learn the things you're talking about + more. It was probably the best move I've ever made.