miniblog.

Haskell Wingman is a fun project that provides hole-based refinement to any editor that speaks LSP! It's a great example of how to describe complex features in terms of user benefit too. https://haskellwingman.dev/

I'm coming to the view that NP-complete problems are harder to work with than tasks equivalent to the halting problem. For the halting problem, you know you're never going to solve the general case. For NP-complete problems there's a slew of complex algorithms to explore.

I average about two pull requests per week across my personal GitHub repos. It's easy to let them pile up. Easy PRs (uncontroversial fix, green build) are fine, but harder PRs (old project, broken build, complex feature) can be a chore in aggregate. Any tips?