Wrapping Goroutines to Handle Return Values in Go
Goroutines cannot return values. Wrapping them so results and errors reach the caller safely, without leaking goroutines or quietly swallowing failures.
A local-first profiling workbench for Go and .NET — attach to a running process, explore flame graphs, GC and diffs in your browser, and keep every profile on your machine.
Open and explore multi-gigabyte JSON and NDJSON files on your desktop — indexed in place, never fully loaded into memory.
An offline-first, encrypted personal-finance tracker for Indian investors — every rupee stays on your device.
Goroutines cannot return values. Wrapping them so results and errors reach the caller safely, without leaking goroutines or quietly swallowing failures.
Go's concurrency principle in practice: passing data over channels instead of guarding it with mutexes, and why that removes a class of bugs by design rather than by discipline.
Go 1.18's workspace mode lets you develop across several modules at once without the replace-directive dance in go.mod. Setting one up, and what changes about the workflow.
Stack Overflow answers, blog posts and LLM output all derive from the same place - the official docs. An argument for going there first, and for weighting your sources deliberately.
A short case for drawing the truth table before writing the if/else chain, using a filtered orders page where the combinations quietly got out of hand.