
Yahiya
1.2K posts

Yahiya
@yahiyadev
Senior Golang Developer ex @smcglobal ex @project10k_tech | Building Fintech products | Tweets about backend, performance & Go.






I'm getting a lot of DMs asking for a roadmap or where to start learning Golang. Here's what I would do If I was starting to learn golang as a beginner: Some important topics are Interfaces, arrays, slices, maps, variadic functions, strings and runes, Mutex, defer, recover etc. (Spend 60% of your time on these topics below) master concurrency, goroutines, channels and then jump to concurrency patterns. Check out Concurrency in Go book. It's a good Book. Go to t.co/tZUYnDJgEW it's good for beginners and then see Golang's official Documentation. After that try to do some coding problems using go. Try to do string/data manipulation problems & try to think "how would I solve this problem in Go? What functions should I use? This will help you get comfortable & boost your confidence while learning Go. Make a habit of solving 3-4 problems daily. Write code daily even if you're following some tutorial, don't just copy paste the example, try to write by yourself. Do this for 1-2 months or take more time if you feel you're not comfortable. Then move on to build mini projects using the cobra cli library, APIs and utilise goroutines and channels. Explore frameworks gin, go-chi, echo etc. try to write API using each framework and use popular features of framework. analyze these frameworks, do the comparison side by side and decide which one would be best for your project. Implement authentication mechanism, circuit breakers, rate limiter etc. For example, you can create an API to fetch client's data from DB and write to a PDF file. Use pdfcpu library (you can find this on GitHub). If client's data is coming from different tables (3 or more), then use goroutines to write that data to pdf concurrently. This example taught me a lot of things. After you're done with this then learn about grpc. Tip:- don't learn everything in one go. Learn one thing then implement it and then move to another topic and in that 2nd topic try to use the 1st topic. Do this for all topics. You can look at my old tweets I've shared some good concepts All the best👍



Congrats to the @cursor_ai team on the launch of Composer 2! We are proud to see Kimi-k2.5 provide the foundation. Seeing our model integrated effectively through Cursor's continued pretraining & high-compute RL training is the open model ecosystem we love to support. Note: Cursor accesses Kimi-k2.5 via @FireworksAI_HQ ' hosted RL and inference platform as part of an authorized commercial partnership.
















