Hi and thanks so much for the feedback here If I got it right, the summary is as such: 1- License: I'll add soon, forgot about it (literally) 2- Where is the

Hi and thanks so much for the feedback here If I got it right, the summary is as such: 1- License: I'll add soon, forgot about it (literally) 2- Where is the solution: I hope you all read the contributing guide, I clearly mentioned solutions are not the MAIN point for this repository, it is rather giving problems which are intended to *guide* me/you through hands-on practical constraints on how to face those "go" weird scenarios. I also clearly stated I'm not that much top notch Go dev to provide you with solutions for now 3- No, this is neither chatgpt, nor claude code generated repo. 4- I'm till waiting until someone with enough experience that worked on these problems in real life can either suggest solutions or provide support 5- The project is a hands-on documentation, maybe on-going process. IMHO is better (for me at least) than a youtube video that I forgot about the next day. Struggling into the problem and implementing an okkeyish solution would force me ask and search for the foundational knowledge behind it, read books *with this goal in mind*, what videos *with that intention*, and so on. I'm very hands-on learning person. 6- Would be very nice to have these questions here in form of Github issues as well, then maybe seasoned devs can support both me and you better 7- I haven't expected it to escalate to ~ 1.7k stars in two weeks, with not much effort, and this is IMHO a proof many devs struggle with that exact gap I'm trying to tackle