Archit Agarwal
Archit Agarwal @architagr ·
🧩 Go’s Strategy Pattern makes swapping logic easy. But what if you want strategies loaded at runtime from .so plugins? What’s your approach? 👇 #Golang #GoPatterns #SystemDesign
Impossible in Go 0.0%
Use plugin pkg 0.0%
Reflection wrapper 0.0%
Needs cgo 0.0%
0 votes · Final results
21
Archit Agarwal
Archit Agarwal @architagr ·
😈 Go’s Strategy Pattern can hide silent bugs. If your builder accidentally returns (nil, nil) as a strategy — what happens next? 👇 💡 Go’s “typed nil” trap catches even pros. #Golang #GoPatterns #CodingBugs #SystemDesign
Panic on Export() 0.0%
Compile-time block 0.0%
Runtime panic later 0.0%
No effect 0.0%
0 votes · Final results
3
16
Archit Agarwal
Archit Agarwal @architagr ·
🎯 Go hides design patterns in plain sight! Which of these Go features best reflects a Strategy Pattern — swapping behavior without touching core logic? 👇 # Golang #GoPatterns #CleanCode #SystemDesign
sort.Sort + comparator 0.0%
context deadlines 0.0%
sync.Mutex vs RWMutex 0.0%
errors.Is / errors.As 0.0%
0 votes · Final results
3
15
Archit Agarwal
Archit Agarwal @architagr ·
🧠 Go’s Strategy Pattern keeps logic clean — e.g., exporting data as JSON, XML, or CSV. But here’s a subtle bug 👇 If one strategy forgets to implement Export() for an empty dataset… what happens? #Golang #GoPatterns #CleanCode #SystemDesign
Go inserts defaults 0.0%
Nil pointer deref 0.0%
Empty string 0.0%
Depends on code 0.0%
0 votes · Final results
3
22
Archit Agarwal
Archit Agarwal @architagr ·
👀 Go’s Observer Pattern looks simple—publisher notifies all subscribers. But naive implementations have hidden costs. Which one bites the most? �� #Golang #Concurrency #GoPatterns
Too many goroutines 0.0%
Slow sub blocks chain 0.0%
Memory leaks via subs 0.0%
All of the above 0.0%
0 votes · Final results
5
19
Archit Agarwal
Archit Agarwal @architagr ·
#️⃣ Go’s Observer Pattern twist: Charlie blocks author1, then unsubscribes & re-subscribes. What happens next? 🤔 #Golang #GoPatterns #SystemDesign
Block list reset 0.0%
Block list preserved 0.0%
Notifications duplicated 0.0%
Compile error 0.0%
0 votes · Final results
2
14
Archit Agarwal
Archit Agarwal @architagr ·
⚡ Scaling Go HTTP servers? Imagine adding logging + rate limiting dynamically. Inheritance won’t work in Go… so which pattern scales better? 👇 #Golang #GoPatterns #SystemDesign
Factory Pattern 0.0%
Decorator Pattern 0.0%
Singleton Pattern 0.0%
Proxy Pattern 0.0%
0 votes · Final results
20
Archit Agarwal
Archit Agarwal @architagr ·
Go’s Decorator Pattern lets us wrap objects to add behavior. But stacking decorators can backfire. What’s the most common pitfall devs face? 🤔🍦 #Golang #GoPattern@s @golang@golangweekl@y @GolangTrends
Recursive call leaks 0.0%
Skipping wrapped calls 0.0%
Interfaces not reusable 0.0%
Only works with structs 0.0%
0 votes · Final results
3
20
Archit Agarwal
Archit Agarwal @architagr ·
Go’s Decorator Pattern adds behavior by wrapping objects—no inheritance involved. So in Go terms… Which idiom does it align with most? 🧐 #Golang #GoPatterns
Embedding + interfaces 0.0%
Goroutines + channels 0.0%
Error wrapping (%w) 0.0%
Context cancellation 0.0%
0 votes · Final results
3
27
Archit Agarwal
Archit Agarwal @architagr ·
👉 Imagine two decorators wrapping the same ExistingIngredient object. Which order of method execution will occur in Go? 💡 Hint: Think about how wrappers forward calls down the chain. #Golang #GoPatterns #ProgrammingPoll #SystemDesign #100DaysOfGo
In code-defined order 0.0%
Last decorator first 0.0%
Based on chaining 0.0%
Random / not guaranteed 0.0%
0 votes · Final results
4
31