1.7 KiB
| title | description | date | preview | draft | tags | categories | lastmod | |||
|---|---|---|---|---|---|---|---|---|---|---|
| Solving Puzzles with Code | 2022-12-01T03:10:01.568Z | false |
|
2022-12-01T03:38:00.008Z |
The Advent of Code is upon us once again. Every year Eric Wastl weaves together a daily series of clever challenges into a delightful story. They can be solved in any language and method you want, including brute force, and I look forward to it every December.
Which is an odd thing to say maybe considering I've never made it further than a dozen days in. It just seems like every year the work project I'm on catches fire and needs my full attention and my drive to work on coding challenges for fun just fizzles out.
I'm fully expecting it to be true this year, too. I just started a new project this week, and the whole reason I'm here is they are short-staffed and under the gun to deliver a fully functional robot in three months, if not sooner. I've already accepted the fact that it's going to ratchet up the pressure over the next few weeks and not loosen up for the holidays. I'm ok with that.
Still, I'm ready. I've been wanting to loosen my reliance on GitHub (same as I'm loosening my reliance on Twitter, Instagram, etc.) so this was the perfect time to try out Gitea. Programming is surprisingly social (especially coding challenges like AoC) so I spun up git.kestrelsnest.social and created a placeholder repo for my 2022 solutions. When the first puzzle lands at midnight, I'll be ready to go.
And if I only make it three days, that's ok.