PinnedInLevel Up CodingbyArchit Agarwal·Apr 23, 2025Stop Spawning Infinite Goroutines: Use Tee-Channels in Go for Scalable Event HandlingImagine you’re working on an app that allows users to sign up for free. But you also want to make sure that someone from the sales team…A response icon3A response icon3
PinnedInLevel Up CodingbyArchit Agarwal·Jan 22, 2025Go Singleton Pattern: Using sync.Once for Safe and Efficient One-Time InitializationLearn how to use Go’s sync.Once for safe, one-time initialization in concurrent applications. Prevent race conditions and optimize resource
PinnedInLevel Up CodingbyArchit Agarwal·Dec 18, 2024Why Every Go Developer Must Master context.Context to Avoid Production NightmaresImagine this:A response icon1A response icon1
PinnedInDev GeniusbyArchit Agarwal·Dec 11, 2024Are You Checking Error Types Correctly in Go?As a developer transitioning from languages like Java, .NET, or TypeScript, you’ve probably missed the convenience of try-catch blocks…
PinnedInDev GeniusbyArchit Agarwal·Nov 27, 2024Unlock the Power of Custom Formatting in Go: A Deep Dive into the Formatter InterfaceIn this article, we’ll dive into one of Go’s lesser-known yet powerful features which is the Formatter interface. If you’ve ever wanted to…
InLevel Up CodingbyArchit Agarwal·2d agoA config 5x longer took 28.7x longer to validateIt worked in dev · Episode 21 · technique: count the links, then union-findA response icon1A response icon1
InLevel Up CodingbyArchit Agarwal·2d ago999 more stores made the delivery map 213x slowerIt worked in dev · Episode 20 · technique: two sweeps instead of a queue
InLevel Up CodingbyArchit Agarwal·6d ago499 new links made the network count 608x slowerIt worked in dev · Episode 18 · technique: connected components, one sweep
InLevel Up CodingbyArchit Agarwal·6d agoInvalidation got faster; computing it got 540x slowerIt worked in dev · Episode 19 · technique: multi-source BFS
InLevel Up CodingbyArchit Agarwal·Oct 26Your category report changes its answer on refreshIt worked in dev · Episode 17 · technique: depth as an index, read in order
