Error handling: wrapping conventions in your team?
pale-beech-10
late-yarrow-282 more
Mostly for small helpers over slices and maps. Rarely anything bigger.
copper-hazel-521 more
Same experience here.
The second time went a lot better once I stopped rushing it.
pale-fern-15
Honestly the cheap option was fine for the first few years.
wild-moth-354 more
Keep it flat until it hurts, a single package goes a long way.
copper-pine-383 more
Thanks, this is exactly what I was looking for.
pale-sparrow-342 more
Honestly the cheap option was fine for the first few years.
woven-hazel-72
pale-sparrow-34 wrote:
Honestly the cheap option was fine for the first few years.
Ha, I thought I was the only one.
dusky-lichen-79
pale-sparrow-34 wrote:
Honestly the cheap option was fine for the first few years.
Strong disagree, but I appreciate the write-up.
amber-otter-29
Table-driven tests are the one pattern I take to every other language now.
quiet-otter-94
The standard library gets you surprisingly far. Reach for dependencies late.
dusky-reed-01 more
One main package until it hurts. Then split.
copper-thistle-45
Thanks, this is exactly what I was looking for.