AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
Go for beginners ♻️
Go Time: Golang, Software Engineering
Gopher Sizes
If i didn't build things, i know, i sort of just stopped learning. I think that's also a really good am what i say, companion or complimentary to what jaun dos says. John tell it tells a little bit about that, yes. So, gopher sizes was kind of me saying, you know, if i was starting over and i just wanted some random exercises to build that weren't completely boring, but would challenge me.
00:00
Transcript
Episode notes
Speaker 2
I think that's also a really good am what i say, companion or complimentary to what jaun dos, which is, ok, you have an ignition, you know the basics and the foundations, the next thing you ought to do is gopher sids, right? John tell it tells a little bit about that,
Speaker 1
yes. So, i mean, basely, whenever i learned, what i generally found was that it didn't matter if i was coating the prettiest code or anything. It generally came down to, if i coted a lot, i learned a lot. And if i didn't build things, i know, i sort of just stopped learning. And i think a lot of times, i've talked to tons and tons of people who re like, you know, i'm trying to build things, but i can't come up with a good project. And what's even worse is, if they come up with a project they like, like a friend who did this all the time, he'd say, i have this cool project, and he'd present it to me, and i'd be like, well, it's going to be really hard for you to do that project at your current skill level, because there's like six other factors that you don't know much about, and i know from experience that they're going to be very hard. Youknow, like the wone to get data from it an they'll assume there's an api to get some data, and it's like, now, that doesn't really exist. You're probably have to like, scrape web pages, and that's going to be terribly hard. So, gopher sizes was kind of me saying, you know, if i was starting over and i just wanted some random exercises to build that weren't completely boring, but would challenge me, would teach me to read the docks, to look at different a p is in the standard library, to do stuff like that, what would they look like? And i basely just sat down and picked out 20 projects that, i sort of picked them intentionally to try different stuff. I didn't want to keep using the same thing, so i didn't want to build like 20 web applications. But the idea was like, you know, if you go through all f these and you code them all, and you actually give it an honest shot of trying to solve each problem on your own, you will learn a ton in the process. Even if you don't complete them fully, or you don't understand everything, or your code's pretty ugly, it doesn't matter, you will still learn a lot doing it.
Get the Snipd
podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered
AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
Discover
highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Discover
highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any
moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Save any
moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share
& Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
Share
& Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
Discover
highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Discover
highlights
Listen to the best highlights from the podcasts you love and dive into the full episode