Doing chores, playing music, playing video games, laying about, walking. I also tend to browse random Haddocks and source code on my phone the same way I browse other websites.
It's mostly a subconscious thing. I can't tell you how many times I've had a Haskell problem to solve (highly-abstract and systems programming alike) and I take a couple days off the keyboard and come back and write code that'll last years.
Of course, there's still a time and place to do the whole tight feedback coding loop thing. But it isn't how most of my Haskell comes to be.
Yeah, I'm a very type-driven dev. So sometimes I'll get stuck with my types and not know a way forward. Usually the answer pops in my head out of nowhere. Reminds me of when Nietzsche said ideas were out in the world, waiting to be bumped into on a walk.
Sometimes it's more that I have a tedious problem and think surely there's a better formulation. That also is a good thing to grind in the subconscious.
There are still some problems for some project I haven't solved too! It'll come.
Comments
Haskell is a beautiful, elegant language. And the tooling is a trainwreck that keeps me from using it.
> And the tooling is a trainwreck that keeps me from using it.
What's the worst part of Haskell tooling in your opinion?
Different strokes. I literally use ghci + plain text editor and are in no way tooling bound no matter the project scale.
I'd say 25% of my Haskelling happens at a computer though.
Where do you do the rest of your Haskelling?
Doing chores, playing music, playing video games, laying about, walking. I also tend to browse random Haddocks and source code on my phone the same way I browse other websites.
It's mostly a subconscious thing. I can't tell you how many times I've had a Haskell problem to solve (highly-abstract and systems programming alike) and I take a couple days off the keyboard and come back and write code that'll last years.
Of course, there's still a time and place to do the whole tight feedback coding loop thing. But it isn't how most of my Haskell comes to be.
I didn’t understand where you were going the first sentence but then paragraphs 2 and onwards were fun.
Are you usually thinking in terms of type abstractions and enforcing invariants through types?
Yeah, I'm a very type-driven dev. So sometimes I'll get stuck with my types and not know a way forward. Usually the answer pops in my head out of nowhere. Reminds me of when Nietzsche said ideas were out in the world, waiting to be bumped into on a walk.
Sometimes it's more that I have a tedious problem and think surely there's a better formulation. That also is a good thing to grind in the subconscious.
There are still some problems for some project I haven't solved too! It'll come.