The Best Golang Book | Prime Reacts
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
AI Coding Sucks | Prime Reacts
ThePrimeTime
245.8k views
The Best Programmers I Know - Prime Reacts
ThePrimeTime
234.4k views
"Use AI Now!" Prime Reacts
ThePrimeTime
199.1k views
Bun vs Go Perf | Prime Reacts
ThePrimeTime
129.4k views
Ascii Elden Ring??? | Prime Reacts
ThePrimeTime
310.0k views
Why I Use C | Prime Reacts
ThePrimeTime
242.9k views
Google Claims Rust Is As Productive As Golang | Prime Reacts
ThePrimeTime
95.9k views
Be Less Precious | Prime Reacts
ThePrimeTime
78.4k views
AI Interview | Prime Reacts
ThePrimeTime
82.9k views
The Best Software Engineering Advice | Prime Reacts
ThePrimeTime
599.2k views
Top Comments (10)
Only Prime can make a 4 minute video into a 15 minute one.
Book Mentioned: 100 go mistakes and how to avoid them - Manning Publications. the other referenced : Concuurency in GO - Oreilly publications Zero To Production In Rust - Luca Palmieri personal mention: Learning GO edition 2- Oreilly pub. Learning Concurrent Programming with GO - Manning Pub.
The author of Learning Go has reached out to let me know that his book is not teaching you if statements, but about creating idiomatic ago. Just in case there was any confusion
I used to hate reading programming books, but as I gain more experience, I come to learn that I really cannot trust some random internet dude's blog posts. Books aren't perfect, but they have heavily vetted information, they are well edited, and theres a standard of quality when it comes to book writing that you rarely see on the internet. SO when i jump into a new language for the first time, i generally try to look for a book that will teach me everything i need to know, and also act as a good reference for when i am actually writing code.
Packt is THE publisher that seems to allow anyone to fulfill their dream of writing a shit of a technical book just to tick the box of writing a technical book.
The pipeline from Java to Go looks real to me. I know a bunch of people that switched from Java to Go and have no interest in Rust. Go just seems to be a good match for Java programmers.
Learning from a book is 100 times more productive for me than from a video. 1. Read 2. Explain to yourself in your own words 3. Instantly transcribe to paper or a text editor to test what you've read A video, for me, is much more cluttered. I believe reading transports your brain to a learning state much more easily because it's much harder to do so passively without realizing it compared to watching a video. In the video, there are many elements instead of just you and what you have to learn.
'didn't just give us the tip, full shaft learning', never change Prime, never change.
Thanks for recommending the Rust Zero to Production book so much. I picked it up a few weeks ago w/o any real Rust experience, and it's been great. The best part about it is how he typically shows you the naive approach, then shows you how to refactor it into idiomatic Rust, and THEN how to refactor it even more so using the community libs. The HttpResponse coercion / into Error stuff has def been my favorite part so far.
Loving all the Go content lately🔥
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
Only Prime can make a 4 minute video into a 15 minute one.
Book Mentioned: 100 go mistakes and how to avoid them - Manning Publications. the other referenced : Concuurency in GO - Oreilly publications Zero To Production In Rust - Luca Palmieri personal mention: Learning GO edition 2- Oreilly pub. Learning Concurrent Programming with GO - Manning Pub.
The author of Learning Go has reached out to let me know that his book is not teaching you if statements, but about creating idiomatic ago. Just in case there was any confusion
I used to hate reading programming books, but as I gain more experience, I come to learn that I really cannot trust some random internet dude's blog posts. Books aren't perfect, but they have heavily vetted information, they are well edited, and theres a standard of quality when it comes to book writing that you rarely see on the internet. SO when i jump into a new language for the first time, i generally try to look for a book that will teach me everything i need to know, and also act as a good reference for when i am actually writing code.
Packt is THE publisher that seems to allow anyone to fulfill their dream of writing a shit of a technical book just to tick the box of writing a technical book.
The pipeline from Java to Go looks real to me. I know a bunch of people that switched from Java to Go and have no interest in Rust. Go just seems to be a good match for Java programmers.
Learning from a book is 100 times more productive for me than from a video. 1. Read 2. Explain to yourself in your own words 3. Instantly transcribe to paper or a text editor to test what you've read A video, for me, is much more cluttered. I believe reading transports your brain to a learning state much more easily because it's much harder to do so passively without realizing it compared to watching a video. In the video, there are many elements instead of just you and what you have to learn.
'didn't just give us the tip, full shaft learning', never change Prime, never change.
Thanks for recommending the Rust Zero to Production book so much. I picked it up a few weeks ago w/o any real Rust experience, and it's been great. The best part about it is how he typically shows you the naive approach, then shows you how to refactor it into idiomatic Rust, and THEN how to refactor it even more so using the community libs. The HttpResponse coercion / into Error stuff has def been my favorite part so far.
Loving all the Go content lately🔥