The kind of thing that slips right past code review too

Its beating me up too

I had a pretty hard time with this one!

That's great!!

First try at part B, i did it the naive way. Let the solution run for about 15 minutes while i rewrote it the "smart" way.

The "smart" way finished in 80ms.

scripts or it didn't happen

Done!

And fixed two more bugs as well

Interesting note about Othello: since the score swings wildly back and forth, a bot that uses a minimax algorithm is pretty easy to beat.

That's great feedback. I'll try to add that.

One of the things im proud of here is a nice set of tests:
github.com/djmetzle/ast...

Vitest does a great job.

My little solution template ive been using this year:
gist.github.com/djmetzle/c6a...

This guy webs.

A plus for Ruby, if we're talking about only using the language _batteries included_, for sure.

I've been digging Hanami, but it has some quirks.

I think it could be something off with power management in some core system package. I've been seeing it on recent fedora releases. Hoping some update or bug fix will come out to patch it up. But I don't really know what the problem is