I wish this was the same for data tests (vs unit tests). If I codegen my data tests I will have so much noise and spend all my time working through them. 1% of rows have null values. Is that bad, acceptable, or expected? The hard part in data quality isn’t increasing test coverage.

If I could pick only one it would be either fold fitted sheets or make beds

I seem to recall professional writers discussing novelty as a boost. If you always write on a laptop, switch to hand written. Once coffee shop gets old, do outside, then floor desk. Something about making it different makes brain go “let’s do this!”

Mmm, minty fresh counters ✨

Aka my life

My face should make that elevator expression too

🤣

I’m worried. The clam is closed but the magnets are not touching.

Is 5 off by one errors?

Don’t leave me hanging? What’s the 4th challenge with csv’s?!

Seriously in csv hell and I need all the wisdom I can get.

I've tried and liked the "deliver holds later."

I have no idea how they do the math. "You are 56 out of 80 holds with 2 copies available". 3 days later "your copy is ready!"

400 clicks later I'm down to about 10 newsletters that are basically my online friends.

But I'm also mad at substack - those are 400 clicks I could have used to craft something in Satisfactory.

😮 Do you leave things running and do something else, or is that all hands-on keyboard time?

I hit 65 total hours today and am grateful it's feeling a bit grindy at the moment so it's a tiny bit easier to step away.

looks like it's about to pop!

Is it a bear in bull clothing fighting another bear? Or maybe it’s half-bear, half-bull fighting a smaller full bear?

Is it’s a metaphor for the financial markets for 2025?

Or kinda like March, 2025 comes in as a bull and goes out as a bear?