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

  1. I'd say the best approach would be a merge between first and second one. Completely decouple the processing from sending, so you can reuse the processing function if needed, and have a generic handler function with all the boilerplate.
    4
  2. So true about the shitty problem descriptions 😂 Thank you for the videos man.
    4
  3. TL;DW Use guard clauses to check state for on/off condition code, switch statements are great and can be used for simplifying the if, ifelse, else chains, enums are also useful for conditions that are always going to be of a set type Reduce duplication by moving common code with similar purpose into their own methods. Single lines don't need to be methods, multiple line duplications probably should be moved unless they're inherently dynamic like DB calls. Make clear variable names for everyone to figure out what each variable is, single and double character names aren't helpful for describing what your variable is in most cases.
    4
  4. As someone who taught many programming students, I'm glad to say I quickly understood the bad code in the last example :D
    4
  5. If you like, you can perhaps make a concurrency playlist that you can make at your own pace? That includes wait groups, select, channels, mutexes, worker pools, stateful goroutines, timers, tickers etc. Its totally up to you though. I am still new to Go and you have the best explanations on YT
    4
  6. I believe one interesting aspect that is often overlooked when doing this type of refactors is "time to understand". Code is read more than written. That means that if we optimize the "time to write new code" we may offer sacrifice "time to understand the codebase". I would rather have the code duplicated as with the two different documents classes because that is self-contained than having abstractions (even if they are proper) but that requires 2-3 clicks more to understand what it does. In this case the examples are trivial but in large codebases, having to do 10-12 clicks just to understand everything that a 20 line snippet does because of all the abstractions is a real pain. Of course, once you familiarized with the abstractions it becomes second nature, but it raises the entry bar somewhat inadvertedly most of the time. "We can solve any problem by introducing an extra level of indirection. …except for the problem of too many levels of indirection" I believe many codebases have many more levels of indirection than they need This is specially important if the dev team is new to an existing codebase, if the team has several jr devs, if one spends more time reviewing code from different codebases, etc.
    4
  7. Hoping your videos will rise at a fast rate. Nothing but idiots all over youtube trying to tout how genius they are by providing crappy examples cause they are awkward nitwits in real life. Not sure why they have high counts or any kinds of likes on their videos. This is the best by far and the examples are perfect.
    4
  8. Just finished the tutorial. I was familiar with Go syntax but had zero experience in backend-development. That tutorial was exactly what I needed and I learned a lot from it. Thanks for that vid, you're my favorite golang youtuber now
    4
  9. Brother your teaching style is phenomenal
    4
  10. Just like the others, I have to say this channel has such inspiring content and covers things that I don't think others do, and in the most educative way. Don't worry, the like button is history. Honestly, I had no idea these endpoints were available. I also think they're not going to be free long, just like Github Copilot, so, while the getting's good :D ... I have to mention that I still don't think I'll be churning out apps really soon, and not as easily as others, but it gives me a sense of how much or what I need to be capable of, and what I need to stop hesitating to do (living in a deteriorating economy).
    4
  11. Amazing video! can you please tell me which program you use to make these illustrations, they are fantastic!
    4
  12. A very good video. Excellent pace and direct delivery. Thanks a bunch.
    4
  13. Bro content might be great but Please don't add background music while explaining something.
    4
  14. Brilliant video. Thanks for easing this out for me ❤️
    4
  15. Awesome, great do moe like theese, which really shows the power of modern software design arch's using Go!
    4
  16. Missed Clojure macros and erlang actor model. It’s expected.
    4
  17. Can't believe you post these for free 🙏. I've had college lecturers who didn't make content this good haha
    4
  18. The last code with DocumentProperties - It looks more like typical using the definition of composition and when it is better than an inheritance.
    4
  19. Great one! Looking forward to seeing the same for the OLID
    4
  20. I already understood what interfaces were, so I was able to follow. But I think that example was pretty terrible. I think you made it even more overly complicated lol. Id say work on that but otherwise, the video was cool.
    4
  21. From now on, you've got one more subscriber. Great content. I can't wait for some more advanced topics like, dependency injection, dynamic typing (interface{}) etc. As a php programmer recently I rewrote one of my microservices, and I was amazed by ease of doing it just with go. Apart of painfully precise data types declaration, and luck of many useful generic functions present in php core, I had almost ecstatic pleasure. Most of the time I do hard core backend staff with data transfer and after speed comparison I fell in love with go 🙂
    4
  22. I really like the explanation. For me, a key part is missing though. Why would I use this when I could have a Giftcard class and several said objects? (I know functional programming would most likely not be possible without closures)
    4
  23. You explain things exceptionally good brother .
    4
  24. what are pointers used for/what are some common use cases?
    4
  25. I think you're making a mistake in TC, we have to add all the calls right? you're considering only at last level but actually we'll sum calls from level 0 to level 3 so there's formula ( sum of calls till level (N-1) = calls in level (N) - 1 ) it's (2^n)-1 so here we don't consider calls in just last level but from 0 till last level.
    3
  26. Thank you for this !! I find your content very insightful and informative never stop uploading
    3
  27. As a teacher myself, I applaud your format. You made this complex idea into something pretty simple
    3
  28. If you could make one on Adapter pattern and Strategy pattern please. These confuse me a lot. Adapter - because i get confused with which needs to be wrapped - the examples around contribute more to the confusion. Strategy because it looks like a if-else which is more like a factory - though factory is a creational pattern and strategy a behavioral one
    3
  29. Thank you sir 🥳
    3
  30. My Golang geek in Tokyo
    3
  31. Please answer my question what company do you work for, where do you want to apply? Is there a recuitment every year?
    3
  32. agave nerd font i think
    3
  33. This video was fun. Almost like the beginning of American Psycho. The music, the routine lol. And also I noticed you are using Goland? I'm curious how and when IDEs help more than editors like VSCode.
    3
  34. Thanks sir ❤ Can you post more videos like this which helps for cracking interviews
    3
  35. Share the template in pdf, doc... how much basic it is this will bring value to your viewers.
    3
  36. Nicely presented!
    3
  37. Good explanation but is that actually what you do in real life? Would you really write an interface for a DB by yourself? I think you would rather import one from your ORM or some other packgages no? I think creating a DB interfaces can get pretty extensive
    3
  38. This pairs beautifully with the self study videos.
    3
  39. Thanks for inspiring us always .🤖
    3
  40. Not getting any job in Go 😢..... Now it feels I made a mistake learning GO
    3
  41. 5:04 must be 1 not 0
    3
  42. The quality of this content is amazing, well done!
    3
  43. Glad you're back to making Go videos man... They're super useful
    3
  44. Great video brother. Hope you keep it going. I suggest though that you make the videos in 10 minutes series instead of a single large chunk. It becomes pretty overwhelming and difficult to index when I am trying to refer to your videos when working on something. But ey, you just got yourself a subscriber
    3
  45. Awesome tutorial! Subbed
    3
  46. This is a hidden GEM on youtube. Thanks for the amazing explanation, and a hello from Brazil!
    3
  47. Many times, a fn with lots of params is built in and not worth making a wrapper just to key the values with an object. In that case, I will give each passed in value a descriptive variable. Even comments are fine there.
    3
  48. Its only a simple example for the video you know right?
    3
  49. "A Swe at Japan" Bro you living in my dream!
    3
  50. Hi Kantan nice vid. Learn a lot from this. for the take function my initial thought to control the amount of data taken from the stream was to do something like counter := 0 for r := range generator(done, randNumFetcher) { if counter == 10 { done <- 1 break } fmt.Println(r) counter += 1 } how much different is this from the take function you used? and which is better and why?
    3