I think I found my very first programming book. It was likely “Basic Fun”.

Im utterly failing to find out French textbooks from early elementary.

Thank you

Don't get me started on the fact that folks with strong TDD and BDD backgrounds have a great background for writing prompts.

I'm also finding the concepts translate well to the LLM/AI era where you can't fully predict what an API call to an LLM will do.

Treat that call as legacy code, apply the ideas in the book and put some Characterization Tests around that call. You'll be glad you did.

Also...that's just eval.

Thinking about this more...its all about situational awareness. And situational awareness requires understanding what's going on around you, both seen and unseen.

And understanding or at least *knowing* what's going on around you comes from curiosity.

Oh, I didn't realize.

For example, the big cat had her checkup about a month ago, but it was too soon for some vaccine boosters.

So she goes back this week for a nurse visit for that. They'll take her back, give the shots, feed her a Churu or three, and then bring her back to me. Usually with a goody bag.

I've been pretty happy with Atlantic Vet on Rainier.

A couple minor blips, but generally we've been able to sort things out quickly.

They're also generally really, really clear on followups and what is a vet visit versus a nurse visit.

The best managers I've had know when to slow down and just let people ruminate and think and be upset and ask questions and ask them again.

And I try to be that manager too. I don't always succeed.

I don't always get the timing right.

I'm not prefect, but I can try to be okay.

But before I offer the plan I want to make sure that folks have had time to be upset, sad, disappointed, frustrated, happy, or whatever else they're feeling. I want to make sure they feel heard.

I've even said things like "today is for feelings, there is a plan and we can talk about it tomorrow."

Making time for feelings and respecting feelings and listening to feelings has become a huge part of how I approach management.

I'm a fixer. I want to be trusted and respected. Its instinctual for me to jump immediately to solutions and planning.

And sometimes having a plan is what people need.

One thing I do when working with others is try to identify the invisible work. Both mine and theirs.

Here's a hint, it is often hidden around the word "just" as in "Why can't you just..."

Compromise is easier when you feel seen and respected.

Sometimes its invisible because the work doesn't produce artifacts folks can see. The time I spend researching for video is one example.

Sometimes its invisible because you make it look so easy they don't understand how hard it was.