#100daysofgo search results
Day 16 of #100DaysOfGo 🐹 Today I played with Go’s image package, turns out, Go can paint too 🎨 I created an RGBA image with bounds and printed its rectangle limits and pixel colors. It’s wild seeing how Go handles pixels so well #100DaysOfCode #Golang #BuildInPublic
Day 14 of #100DaysOfGo 🐹 Just explored goroutines, Go’s secret weapon for concurrency ⚡️ Crazy how simple it is to run multiple tasks at once with just the go keyword. Feels like unlocking parallel universes with a single line of code 😅 #Golang #100DaysOfCode #GoLangJourney
Day 13 of #100DaysOfGo 🐹 Today was about errors — Go’s way of saying “something went wrong, handle it yourself.” 😅 I learned how to return and check errors properly No drama, explicit handling. Go really makes you own your mistakes 😂 #100DaysOfCode #Golang #BuildInPublic
Day 26 of #100DaysOfGo 🐹 Built a Pomodoro timer today⏳! It counts down work and break sessions using Go’s time package practicing time.Duration, loops, and printing dynamic updates. 25 minutes focus, 5 minutes rest. 💪 #Golang #100DaysOfCode #BuildInPublic
Day 25 of #100DaysOfGo 🐹 Dove into slices and maps again, but this time I practiced mutating maps, appending slices, and using range all together. It felt so satisfying seeing Go handle dynamic collections cleanly adding, updating, looping all in a few lines. #BuildInPublic
Day 22 of #100DaysOfGo 🐹 Today felt so good I built my first real CLI app in Go! 💻✨ A simple Todo app that runs right in the terminal and yes, it actually saves your tasks in a json. Thread 🧵👇 #Golang #100DaysOfCode
Day 21 of #100DaysOfGo 🐹 Today was all about syncing, i made data safe across goroutines using sync.Mutex. 🔒 Built a SafeCounter that increments values from 1000 goroutines without breaking anything. Go’s concurrency + mutex = peace in parallelism 😎 #100DaysOfCode #Golang
Day 8 of #100DaysOfGo 🐹 Today I met methods, basically functions with commitment issues that decides to settle down with a type 😅 Attach a method to a struct & boom behavior unlocked. Clean, simple, no OOP drama. Go just gets it ✅. we go again 🚀 #GoLang #100DaysOfCode
Day 13 of #100DaysOfGo 🐹 Today was about errors — Go’s way of saying “something went wrong, handle it yourself.” 😅 I learned how to return and check errors properly No drama, explicit handling. Go really makes you own your mistakes 😂 #100DaysOfCode #Golang #BuildInPublic
Day 24 of #100DaysOfGo 🐹 Today, I explored JSON decoding in Go After learning to format JSON neatly with json.MarshalIndent 😚 I went deeper into parsing JSON into structs using json.Unmarshal #Golang #100DaysOfCode #BackendDevelopment
Day 23 of #100DaysOfGo💡 Today was all about making JSON look pretty! 😄 I tried out json.MarshalIndent -> it’s great for printing neat, readable JSON instead of messy one-liners. Struct tags like json:"name" define how fields are encoded and decoded. #GoLang #LearnInPublic
Day 25 of #100DaysOfGo 🐹 Dove into slices and maps again, but this time I practiced mutating maps, appending slices, and using range all together. It felt so satisfying seeing Go handle dynamic collections cleanly adding, updating, looping all in a few lines. #BuildInPublic
Day 24 of #100DaysOfGo 🐹 Today, I explored JSON decoding in Go After learning to format JSON neatly with json.MarshalIndent 😚 I went deeper into parsing JSON into structs using json.Unmarshal #Golang #100DaysOfCode #BackendDevelopment
Day 5 of #100DaysOfGo 🐹 Arrays and slices today, not like js style I'm used to It's wild how Go makes you think. Arrays don't move - they're fixed. Slices though? They're like references to arrays 😏 a[1 : 4] -- creates a slice from 1 through 3. #100daysofcode
Day 21 of #100DaysOfGo 🐹 Today was all about syncing, i made data safe across goroutines using sync.Mutex. 🔒 Built a SafeCounter that increments values from 1000 goroutines without breaking anything. Go’s concurrency + mutex = peace in parallelism 😎 #100DaysOfCode #Golang
Day 9 of #100DaysOfGo 🐹 Today I met interfaces🥲 Ngl, I compared it with struct and methods. Struct → noun → what something is ✅ Method → verb → what it does ✅ Interface → rulebook → what actions re expected. ✅ #golangcourse #100DaysOfCode
Day 8 of #100DaysOfGo 🐹 Today I met methods, basically functions with commitment issues that decides to settle down with a type 😅 Attach a method to a struct & boom behavior unlocked. Clean, simple, no OOP drama. Go just gets it ✅. we go again 🚀 #GoLang #100DaysOfCode
Day 4 of #100DaysOfGo Building on yesterday’s structs, today I explored methods, Go's way of attaching behavior directly to data. I like how Go lets you define methods for both value and pointer receivers, giving you control over how data is passed and modified.
🧵 Day 2 of #100DaysOfGo 🐹 Today was all about flow control — for, if, switch, and defer. Go keeps it simple: 1. while loop ❌, only for loop costruct exist 2. no parentheses around conditions 3. switch doesn’t fall to default It just makes sense. 😌 #Golang #100DaysOfCode
Day 10 of #100DaysOfGo 🐹 I pulled everything i’ve learnt so far struct, method & interfaces and built -> ℂ𝕃𝕀 𝔸𝕣𝕖𝕒 ℂ𝕒𝕝𝕔𝕦𝕝𝕒𝕥𝕠𝕣 🧮 Pick a shape, drop in props, Go handles it fast ✅ . no class, no inheritance, simple stuff 💯. #100DaysOfCode #BuildInPublic
Day 11 of #100DaysOfGo 🐹 Today I played with type assertions and type switches, Go’s way of letting you peek behind the curtain of an interface{}. 🎭 With assertions, you grab the real value hiding inside. With type switches, you handle multiple types smoothly.
Day 10 of #100DaysOfGo 🐹 I pulled everything i’ve learnt so far struct, method & interfaces and built -> ℂ𝕃𝕀 𝔸𝕣𝕖𝕒 ℂ𝕒𝕝𝕔𝕦𝕝𝕒𝕥𝕠𝕣 🧮 Pick a shape, drop in props, Go handles it fast ✅ . no class, no inheritance, simple stuff 💯. #100DaysOfCode #BuildInPublic
Day 26 of #100DaysOfGo 🐹 Built a Pomodoro timer today⏳! It counts down work and break sessions using Go’s time package practicing time.Duration, loops, and printing dynamic updates. 25 minutes focus, 5 minutes rest. 💪 #Golang #100DaysOfCode #BuildInPublic
Day 25 of #100DaysOfGo 🐹 Dove into slices and maps again, but this time I practiced mutating maps, appending slices, and using range all together. It felt so satisfying seeing Go handle dynamic collections cleanly adding, updating, looping all in a few lines. #BuildInPublic
Day 25 of #100DaysOfGo 🐹 Dove into slices and maps again, but this time I practiced mutating maps, appending slices, and using range all together. It felt so satisfying seeing Go handle dynamic collections cleanly adding, updating, looping all in a few lines. #BuildInPublic
Day 24 of #100DaysOfGo 🐹 Today, I explored JSON decoding in Go After learning to format JSON neatly with json.MarshalIndent 😚 I went deeper into parsing JSON into structs using json.Unmarshal #Golang #100DaysOfCode #BackendDevelopment
Day 24 of #100DaysOfGo 🐹 Today, I explored JSON decoding in Go After learning to format JSON neatly with json.MarshalIndent 😚 I went deeper into parsing JSON into structs using json.Unmarshal #Golang #100DaysOfCode #BackendDevelopment
Day 23 of #100DaysOfGo💡 Today was all about making JSON look pretty! 😄 I tried out json.MarshalIndent -> it’s great for printing neat, readable JSON instead of messy one-liners. Struct tags like json:"name" define how fields are encoded and decoded. #GoLang #LearnInPublic
Day 23 of #100DaysOfGo💡 Today was all about making JSON look pretty! 😄 I tried out json.MarshalIndent -> it’s great for printing neat, readable JSON instead of messy one-liners. Struct tags like json:"name" define how fields are encoded and decoded. #GoLang #LearnInPublic
Day 22 of #100DaysOfGo 🐹 Today felt so good I built my first real CLI app in Go! 💻✨ A simple Todo app that runs right in the terminal and yes, it actually saves your tasks in a json. Thread 🧵👇 #Golang #100DaysOfCode
Day 22 of #100DaysOfGo 🐹 Today felt so good I built my first real CLI app in Go! 💻✨ A simple Todo app that runs right in the terminal and yes, it actually saves your tasks in a json. Thread 🧵👇 #Golang #100DaysOfCode
Day 21 of #100DaysOfGo 🐹 Today was all about syncing, i made data safe across goroutines using sync.Mutex. 🔒 Built a SafeCounter that increments values from 1000 goroutines without breaking anything. Go’s concurrency + mutex = peace in parallelism 😎 #100DaysOfCode #Golang
Day 21 of #100DaysOfGo 🐹 Today was all about syncing, i made data safe across goroutines using sync.Mutex. 🔒 Built a SafeCounter that increments values from 1000 goroutines without breaking anything. Go’s concurrency + mutex = peace in parallelism 😎 #100DaysOfCode #Golang
Day 20 of #100DaysOfGo 🐹 Built a Fibonacci generator today using goroutines, channels, and select. One channel feeds numbers, another tells it when to stop. Go lets you coordinate routines so smooth🔥 we go again tomorrow 🚀 #100DaysOfCode #Golang #BuildInPublic
Day 19 of #100DaysOfGo 🐹 Today was about goroutines & channels, Go's secret sauce for concurrency ⚡ I split a slice in two, summed both halves at the same time, and sent results through a channel. Go handles parallel tasks so easily 🚀 #100DaysOfCode #Golang
Day 19 of #100DaysOfGo 🐹 Today was about goroutines & channels, Go's secret sauce for concurrency ⚡ I split a slice in two, summed both halves at the same time, and sent results through a channel. Go handles parallel tasks so easily 🚀 #100DaysOfCode #Golang
Day 18 of #100DaysOfGo 🐹 Got deeper into generics today, built a Min function that works with int, float64, and even string 🔥 Defined a custom Number constraint using int,float64 & string One function, many types💪 TIll tomorrow 🚀 #100DaysOfCode #Golang #BuildInPublic
Day 18 of #100DaysOfGo 🐹 Got deeper into generics today, built a Min function that works with int, float64, and even string 🔥 Defined a custom Number constraint using int,float64 & string One function, many types💪 TIll tomorrow 🚀 #100DaysOfCode #Golang #BuildInPublic
Day 17 of #100DaysOfGo 🐹 Didn't touch code today. 😕 No progress, no commits. But showing up to admit that is progress. Tomorrow, I'm back in the Go flow 🚀 #Golang #100DaysOfCode #buildinginpublic
Day 17 of #100DaysOfGo 🐹 Didn't touch code today. 😕 No progress, no commits. But showing up to admit that is progress. Tomorrow, I'm back in the Go flow 🚀 #Golang #100DaysOfCode #buildinginpublic
Day 16 of #100DaysOfGo 🐹 Today I played with Go’s image package, turns out, Go can paint too 🎨 I created an RGBA image with bounds and printed its rectangle limits and pixel colors. It’s wild seeing how Go handles pixels so well #100DaysOfCode #Golang #BuildInPublic
Day 16 of #100DaysOfGo 🐹 Today I played with Go’s image package, turns out, Go can paint too 🎨 I created an RGBA image with bounds and printed its rectangle limits and pixel colors. It’s wild seeing how Go handles pixels so well #100DaysOfCode #Golang #BuildInPublic
Day 15 of #100DaysOfGo 🐹 Half a month in🔥 Readers, streams that feed your program data piece by piece. Built a simple program that reads "Hello, Reader!" in chunks using strings.NewReader and r.Read(b) It’s like watching Go chew data byte by byte #Golang
Day 14 of #100DaysOfGo 🐹 Just explored goroutines, Go’s secret weapon for concurrency ⚡️ Crazy how simple it is to run multiple tasks at once with just the go keyword. Feels like unlocking parallel universes with a single line of code 😅 #Golang #100DaysOfCode #GoLangJourney
Day 14 of #100DaysOfGo 🐹 Just explored goroutines, Go’s secret weapon for concurrency ⚡️ Crazy how simple it is to run multiple tasks at once with just the go keyword. Feels like unlocking parallel universes with a single line of code 😅 #Golang #100DaysOfCode #GoLangJourney
Day 13 of #100DaysOfGo 🐹 Today was about errors — Go’s way of saying “something went wrong, handle it yourself.” 😅 I learned how to return and check errors properly No drama, explicit handling. Go really makes you own your mistakes 😂 #100DaysOfCode #Golang #BuildInPublic
Day 13 of #100DaysOfGo 🐹 Today was about errors — Go’s way of saying “something went wrong, handle it yourself.” 😅 I learned how to return and check errors properly No drama, explicit handling. Go really makes you own your mistakes 😂 #100DaysOfCode #Golang #BuildInPublic
Day 5 & 6 of #100DaysOfGo I’ve used functions inside my structs earlier (as methods), but I hadn’t really broken down how functions actually work in Go, so I spent the last two days exploring them in depth.
Day 12 of #100DaysOfGo 🐹 Played with Stringers today, taught Go how to “talk” 😄 Made a custom IPAddr type that prints 127.0.0.1 instead of raw bytes using a String() method. Errors tomorrow 🚀 #100DaysOfCode #Golang #buildinginpublic
Day 11 of #100DaysOfGo 🐹 Today I played with type assertions and type switches, Go’s way of letting you peek behind the curtain of an interface{}. 🎭 With assertions, you grab the real value hiding inside. With type switches, you handle multiple types smoothly.
Day 10 of #100DaysOfGo 🐹 I pulled everything i’ve learnt so far struct, method & interfaces and built -> ℂ𝕃𝕀 𝔸𝕣𝕖𝕒 ℂ𝕒𝕝𝕔𝕦𝕝𝕒𝕥𝕠𝕣 🧮 Pick a shape, drop in props, Go handles it fast ✅ . no class, no inheritance, simple stuff 💯. #100DaysOfCode #BuildInPublic
Day 4 of #100DaysOfGo Building on yesterday’s structs, today I explored methods, Go's way of attaching behavior directly to data. I like how Go lets you define methods for both value and pointer receivers, giving you control over how data is passed and modified.
Day 10 of #100DaysOfGo 🐹 I pulled everything i’ve learnt so far struct, method & interfaces and built -> ℂ𝕃𝕀 𝔸𝕣𝕖𝕒 ℂ𝕒𝕝𝕔𝕦𝕝𝕒𝕥𝕠𝕣 🧮 Pick a shape, drop in props, Go handles it fast ✅ . no class, no inheritance, simple stuff 💯. #100DaysOfCode #BuildInPublic
⚙️ Days 2 & 3 of #100DaysOfGo Been brushing up on Go’s data types and how they scale into more complex structures. Go keeps things simple. you start with basic types like: string int, float64 bool arrays, slices, maps
Day - 1/100, today I started learning a new programming language @golang. Completed some basic exercises from @exercism_io #100DaysOfCode #100DaysOfGo
Day- 3/100 Learned about Strings and did some exercises in @exercism_io. Did you know in @golang strings are an immutable sequence of bytes #100DaysOfCode #100DaysOfGo
Day - 8/100 - Learned about the function of Golang - Solved two questions of @exercism_io - Understood the importance of floating point literals - Revised the previously learned concepts of @golang #100DaysOfCode #100DaysOfGo
Day- 2/100 Completed the comments, numbers, arithmetic operators, and booleans exercises in @exercism_io. Learned about a new data type Float64, which represents a floating-point number with 64 bits of precision. #100DaysOfCode #100DaysOfGo
Day- 4/100 Learned about conditions if and many more. Did you know that you can use 'gofmt -w yourcode.go' in the terminal to automatically format Go code? #100DaysOfCode #100DaysOfGo
Day- 5/100 - In Go, switch cases don't require breaks like other programming languages. - Learned about struct, which is a user-defined type to store a collection of different fields into a single field #100DaysOfCode #100DaysOfGo
Day - 7/100 Here are the following things that I learned today in @golang - Package math/rand generates pseudo-random numbers, which means it uses an algorithm called DRBG to generate a sequence of random numbers. - For loop #100DaysOfCode #100DaysOfGo
Day- 9 to 14 In between I got sick (common cold). I tried my best to be on track, here's what I learned - Learned about Maps, in other programming languages it is known as dict or associative array. - Learned about Struct types #100DaysOfCode #100DaysOfGo
Day 16 of #100DaysOfGo 🐹 Today I played with Go’s image package, turns out, Go can paint too 🎨 I created an RGBA image with bounds and printed its rectangle limits and pixel colors. It’s wild seeing how Go handles pixels so well #100DaysOfCode #Golang #BuildInPublic
Day - 6/100 Learned about Slices and Variadic Functions - Slices in Go are similar to lists or arrays in other programming languages, It's mutable. - Variadic Functions: a special which can be called with any number of trailing arguments. #100DaysOfCode #100DaysOfGo
Day 14 of #100DaysOfGo 🐹 Just explored goroutines, Go’s secret weapon for concurrency ⚡️ Crazy how simple it is to run multiple tasks at once with just the go keyword. Feels like unlocking parallel universes with a single line of code 😅 #Golang #100DaysOfCode #GoLangJourney
Day 13 of #100DaysOfGo 🐹 Today was about errors — Go’s way of saying “something went wrong, handle it yourself.” 😅 I learned how to return and check errors properly No drama, explicit handling. Go really makes you own your mistakes 😂 #100DaysOfCode #Golang #BuildInPublic
Day 12 of #100DaysOfGo 🐹 Played with Stringers today, taught Go how to “talk” 😄 Made a custom IPAddr type that prints 127.0.0.1 instead of raw bytes using a String() method. Errors tomorrow 🚀 #100DaysOfCode #Golang #buildinginpublic
Day 13 of #100DaysOfGo 🐹 Today was about errors — Go’s way of saying “something went wrong, handle it yourself.” 😅 I learned how to return and check errors properly No drama, explicit handling. Go really makes you own your mistakes 😂 #100DaysOfCode #Golang #BuildInPublic
Day 27 of #100DaysOfCode of learning Go programming. Write a small hit counter program to practice mutex with waitGroup. #100DaysOfCode #100DaysOfGo #golang
Day 15 of #100DaysOfGo 🐹 Half a month in🔥 Readers, streams that feed your program data piece by piece. Built a simple program that reads "Hello, Reader!" in chunks using strings.NewReader and r.Read(b) It’s like watching Go chew data byte by byte #Golang
Day 14 of #100DaysOfGo 🐹 Just explored goroutines, Go’s secret weapon for concurrency ⚡️ Crazy how simple it is to run multiple tasks at once with just the go keyword. Feels like unlocking parallel universes with a single line of code 😅 #Golang #100DaysOfCode #GoLangJourney
Something went wrong.
Something went wrong.
United States Trends
- 1. Northern Lights 35.4K posts
- 2. #DWTS 49.8K posts
- 3. #Aurora 7,329 posts
- 4. Justin Edwards 2,037 posts
- 5. Louisville 17.1K posts
- 6. #RHOSLC 6,288 posts
- 7. Andy 60.5K posts
- 8. Creighton 1,966 posts
- 9. #OlandriaxHarpersBazaar 4,544 posts
- 10. Gonzaga 2,598 posts
- 11. Lowe 12.5K posts
- 12. #GoAvsGo 1,419 posts
- 13. Oweh 2,022 posts
- 14. Kentucky 25.3K posts
- 15. JT Toppin N/A
- 16. Celtics 12.2K posts
- 17. Elaine 40.8K posts
- 18. Robert 100K posts
- 19. Dylan 31K posts
- 20. Go Cards 2,737 posts