Hearted Youtube comments on Kantan Coding (@kantancoding) channel.

  1. It actually depends A LOT on what you're doing. Sometimes it's just better to inline, even if it's complex. It's called software engineering. You need to engineer a solution BASED on your context, not on some well-defined general rules.
    16
  2. I agree with everyone else's comments. You've done an incredible job of taking a complex and difficult to understand topic and make it clear with a great example demonstrating it. Thank you so much! You've also gained another subscriber.
    16
  3. oh im so glad i found you! love how youre just real about your day in life, and not mention your in japan! WAKU WAKU!!
    16
  4. to much animation. going back and forth multiple times was making it hard to keep track, because you expect a forward progression, but then be pulled back unexpectedly, then forward again, you quickly lose the sense of knowing what to expect. furthermore, the second and third techniques were glossed over compared to the first one, which feels imbalanced and incomplete. however, the overall structure was well, as well as the individual animations, and the examples as well. im sure some minor changes will make the production quality even better. it seems like you forgot to account for how the audience will process the content, getting absorbed in your own understanding, which is a very common pitfall. all that aside, i am looking forward to the next one!
    16
  5. Thank you for explaining a decorator in a way that I can understand
    16
  6. I’m loving these videos. The visualizations are great and the concise video length doesn’t make me want to click away as opposed to some 20 min+ vids. These have really helped me. Thank you!!
    16
  7. Same here. Bad abstraction is always worse than some code duplication. Obsessive removal of code duplication can become premature optimization in a sense we all don't know how code will change in a near future. Like for example, if I write a common method to remove duplication however later it turns out I need two separate version? If I were to have two copies of same code, then no problem! Just edit one to adapt to design change and let other copy work as is. What about opposite case? I should think carefully about side effect of editing single common method that supports functioning of multiple classes/functions so that it's harder to consider every corner cases and hence preventing adding new behavior or changing it. So that's why it's almost always a better option to start with duplication. You can either do a) clear things up a little later or for better b) just fix one with problem and have fun ❤
    15
  8. Thanks! I've been coding for 20 years, but I'm mostly self taught. I've recently been interviewing for a new job and big O notation has come up a bunch of times. I really needed an explanation because it's not something that comes up in daily coding life. Your series was exactly what I needed.
    15
  9. single word: "incapsulation" u shouldn't pass so many parameters into yr method, but u could pass them over class constructor, it's more readable and easily to maintain
    15
  10. As a rule of thumb, always go for the composition over inheritance :D
    14
  11. Ok, so I think I understand it. The time complexity will depend on the efficiency of the algorithm. The time complexity can be used to say "how long will it take for this to be sorted? or, in this case, how long until we reach our base case? (if (n===0) return "Done"; " So, using this algorithm, the time complexity would be O(log N) , as N = 8 while O(log 8) = 3 If we used an algorithm that instead just subtracted 1 each time, our time complexity would be O(n), as it would take 8 iterations to reach our base case Great video by the way. I had all the pieces from my reading but this just locks them all in place
    14
  12. Please do not stop making videos! You are the first person to explain this to me in a way I truly understand! Thank you so much!
    14
  13. A bad abstraction isn't the problem, it's the 900 gigs of other things that depend on that wrong abstraction that's the issue. A bad abstraction can also introduce all kinds of coupling that is near intractable in a real system
    14
  14. Great explanation. The fact that you explained why a closure is named as such helps a lot, thanks!
    14
  15. At 6:43, this was like my lightbulb moment lol. Then, possibilities started coming to mind. Thanks so much; you just saved me a lot of time.
    14
  16. Top-notch quality content. A tutorial on how to deploy this to the cloud would be much appreciated.
    14
  17. Unit tests catch the easiest kinds of bugs at a cost of a massive test suite that needs to be written and maintained. Unless you're nasa and are going to do every other kind of test under the sun as well you're probably one of those companies that has more lines of test code than production code and yet still ships buggy software. Applying cost benefit analysis and developing in a manner that catches the kinds of bugs that are actually problematic is much more efficient in terms of developer resources. It's a bit of a bold assertion to say that in all circumstances you should write unit tests. Especially with examples like this. Few people suggest you shouldn't test your code. No one worth listening to does. But people very often have good points and strong arguments for not writing unit tests, especially not by default for every piece of code. Your argument is arrogant and misguided.
    14
  18. True, but let’s say you’re working with React, Vue of something. It’s better to turn your longer conditionals into computer state for better readability. In terms of executable code, I agree. It’s not necessary to create a small isValidUser func if you’re only using it once.
    14
  19. I’ve been watching your videos for a while now but I never really comment. I just wanted to let you know how much I love your content for once so you’re aware. Whenever I see that you posted a video it’s just a reflex for me to click and watch immediately. You’re awesome bro!! - Andrew [nov 2023]
    13
  20. How is this pattern better than using the constructor? Perhaps I've not yet seen a real case where this would make sense, maybe if we're dealing with really big constructors with a lot of parameters? Idk
    13
  21. U literally hand holding us. Thank u so much...
    13
  22. Thanks man, sometimes my codebases get very chaotic, these really help
    13
  23. I was struggling a lot trying to understand the basics of time complexity. Especially exponential time complexity. This video was so precise. Thank you so much for helping us out!
    13
  24. Your videos about concurrency in Go are very good.
    13
  25. Very good tips, but I like to keep the conditionals more granular. It's easier to write better log messages or throw more specific error codes
    13
  26. Thanks Kantan, another amazing video. But I believe the main challenge for students studying concurrent and distributed systems lies in "recognizing" these patterns within real-world applications. In other words, they encounter practical situations but often struggle to determine which patterns are suitable for solving their problems. Therefore, I'd really appreciate it if in your future videos show us how these patterns can be applied to real-world problems.
    13
  27. Yes I would like to see how this works with a non recursive function!
    12
  28. Similar origin story. I still have my 2015 macpro.I started on it as a web dev, then android, then ios, now I'm on Windows doing Java :( but its not so bad.
    12
  29. Very helpful video. Glad so many of us found use in it. The writing hand is a bit distracting but this video is a gem
    12
  30. I found this video informative, detailed and on point. You prepared yourself properly, vídeo is structured, with proper pace and sequence of events. Your voice is calm too, haha
    12
  31. Youtube has a built in pause function. All you got to do is click on the screen. You’re welcome.
    12
  32. I've been programming for over a decade but never took the time to understand Big O notation. I landed a Google interview next month and I'm finding myself in a critical timeline to learn algorithms and Big O notation. These videos have been amazing at explaining these concepts very simply. I cannot thank you enough. This is amazing.
    11
  33. Show me the tests, unless everyting is just junior code
    11
  34.  @kantancoding  But unlike what you claim in the video, changing it to string concatenations doesn't solve the issue then? Grepping the entire message will not get you the culprit line, because you don't know where to put the "+" in your search string
    11
  35. Great to have you in this YouTube community ! A lot of effort was put into this video , great
    11
  36. enUm
    11
  37. I'm so glad I found your channel. Keep creating and educating, you deserve so many more subs!
    10
  38. Bruh, I have a Go interview tomorrow, just finished your Master Go Programming With These Concurrency Patterns video, and watching this now. A big thank you for this content.
    10
  39. Context is important for that general rule. It's clearly true for your standard business and web applications, but if you are on a microcontroller or in your main game loop, you have to think about what you're doing to the compiled code. Constants are no problem anywhere of course.
    10
  40. Great video, again you are explaining how things are used in real world, which is missing in most of the videos on youtube. any teachers end goal should be their students/listeners should be be productive after going though the videos, should have all the knowledge required to write any application they want. Thank you, keep teaching... and we are waiting and following your channel...
    10
  41. problem in second law is, when trying to avoid duplication, I also need to do transaction in SQL, and every transaction function always differ from other
    10
  42. I'm interested in learning more about small-cost abstraction constructs, similar to Rust's enums, which can be evaluated at compile-time. Could you make a video of such examples? Also, you mentioned string interpolation earlier. Rust has a similar feature with its print macro. While I'm not a big fan of Rust, I find that feature quite neat.
    10
  43. the last part how you explained the go routines is mind blowing this was a mind bending concept and cleared in a easy way
    10
  44. Please make a detailed course of design patterns or suggest me some resources from where i can learn these topics.
    9
  45. Look at that beautiful side shot. So many slots and ports!
    9
  46. The best golang youtube software engineer
    9
  47. 1. Learn the topic 2. Teach/Explain the topic 3. Find gaps in your knowledge by composing a list of things you don't know 3.a. Study the focus points from step 3 and fill in the gaps 3.b. As you study keep adding new questions that you have to the list and keep finding out what those things are 5. Organize and simplify. Rewrite your notes in an organized and easy to understand manner
    9
  48. Make functions that do a single thing (single responsibility) and give them a name that self-explains what the function does. As an extra effort of good developer experience, write doc strings above the function signature so your editor can show the explanation of the function when hovering over it.
    9
  49. The mutable default arguments thing is wild - Python normally sacrifices performance for the sake of usability but for some reason they left this one footgun in there.
    9
  50. I feel like a better example from Haskell would be how it unifies lists and generators. After showing how enums work in Rust you can explain how the equivalent works in Haskell and build a linked list with that. Then, since the order of evaluation in Haskell almost barely matters, if you have a pair of function where one produces a list and the other one consumes them, together they can be compiled to a simple loop if the compiler is clever enough. And in case it isn't, they will still be generating and consuming about one element at the time because the default lazy evaluation will only ask the producing function to generate the next one if the consuming function is trying to consume it. Then you could even show stuff like creating infinite lists and doing actually useful work with them!
    9