misty-birch-591 more
Table-driven tests are the one pattern I take to every other language now.
Reply
late-thistle-9
Counterpoint: it depends a lot on how much time you have.
Reply
pale-beech-104 more
Wrap with context at every boundary, and only log at the top.
Reply
amber-sedge-231 more
pale-beech-10 wrote:
Wrap with context at every boundary, and only log at the top.
That's fair. I hadn't looked at it that way.
Reply
sunlit-wren-15
amber-sedge-23 wrote:
pale-beech-10 wrote:
Counterpoint: it depends a lot on how much time you have.
Reply
amber-heron-14
pale-beech-10 wrote:
Wrap with context at every boundary, and only log at the top.
Counterpoint: it depends a lot on how much time you have.
Reply
mossy-otter-26
pale-beech-10 wrote:
Wrap with context at every boundary, and only log at the top.
Do you have a source for that? Not doubting, I just want to read more.
Reply
misty-yarrow-352 more
One main package until it hurts. Then split.
Reply
wild-moth-351 more
Agreed, and I'd add that it takes a while before it clicks.
Reply
wry-thistle-74
wild-moth-35 wrote:
Agreed, and I'd add that it takes a while before it clicks.
Same experience here.
The second time went a lot better once I stopped rushing it.
Reply
sunlit-clover-331 more
Mostly for small helpers over slices and maps. Rarely anything bigger.
Reply
slow-sedge-40
Counterpoint: it depends a lot on how much time you have.
Reply
amber-otter-292 more
Keep it flat until it hurts, a single package goes a long way.
Reply
still-willow-23
That's fair. I hadn't looked at it that way.
Reply
slow-sedge-40
amber-otter-29 wrote:
Keep it flat until it hurts, a single package goes a long way.
Agreed, and I'd add that it takes a while before it clicks.
Reply
misty-rowan-88
The standard library gets you surprisingly far. Reach for dependencies late.