wireleaf

programming.go

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.
Reply
copper-hazel-521 more

Same experience here.

The second time went a lot better once I stopped rushing it.
Reply
pale-fern-15

Honestly the cheap option was fine for the first few years.
Reply
wild-moth-354 more

Keep it flat until it hurts, a single package goes a long way.
Reply
copper-pine-383 more

Thanks, this is exactly what I was looking for.
Reply
pale-sparrow-342 more

Honestly the cheap option was fine for the first few years.
Reply
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.
Reply
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.
Reply
amber-otter-29

Table-driven tests are the one pattern I take to every other language now.
Reply
quiet-otter-94

The standard library gets you surprisingly far. Reach for dependencies late.
Reply
dusky-reed-01 more

One main package until it hurts. Then split.
Reply
copper-thistle-45

Thanks, this is exactly what I was looking for.
Reply