I wanted to get proficient in Haskell so I decided to follow An [Essential] Haskell Reading List. There I stumbled upon Typoclassopedia, while the material is great, I couldn’t find solutions for the exercises to check against, so I decided I would write my own and hopefully the solutions would get fixed in case I have gone wrong by others. So if you think a solution is wrong, let me know in the comments!
I’ve had a Kindle for more than a year now, but I’ve only recently started to read books on it frequently, I used to read paperworks before that, and I still do sometimes prefer paperbooks if available. Anyways, my Kindle has helped me to fall asleep without struggling with all my thoughts, all I have to do is read until I fall asleep, so in a way, it has also been a remedy for my insomnia.
Now to read the Kindle in bed, you would have to hold it using your hands or buy a stand or make one, motivated by The Pursuit of Laziness I set to create mine, but I didn’t use a piece of steel, instead I used a single box of cardboard I had in home to create one in minutes. :D
I just want to leave this here as I often tend to look it up myself and the first time it was not as easy to figure out.
When using Travis CI along with GitHub (or other git integrations), Travis runs two tests:
Most of the time you see both tests passing and you do not have to even wonder how they are different, but it has happened to me that one of the tests fails while the other passes and I started to wonder why.
prtest is a test run on the result of a merge between the pull-request branch and the main branch. As an example, let’s say your pull-request’s branch is called
fix-user-authand your main branch is
master, in this case,
masterand then runs the tests on the result of the merge.
On the other hand,
pushis run on the pull-request branch itself, without merging. So in our example above, Travis would checkout to
fix-user-authand run the tests.
A case of difference
A case in which this difference might be more apparent is when your pull-request is based on a branch other than
master, and some changes that your pull-request depends on are missing from
master, in this case the
pushtest may pass, but the
prtest will fail.
So I just went on my first primitive living practice trip in the woods, alone, with only a pocket knife.
I decided I’m going to share the lessons I’ve learned in each trip as they are certainly going to be useful if you want to practice primitive living, I would find these useful if I could find them anywhere. I spend a lot of time reading and watching primitive living guides and experience reports, but they are never exhaustive, and this series is not meant to be exhaustive either.
When it comes to relationships, most (unsuccessful) people are chasing the good ones. They spend time trying to find their dream partner, the perfect match, but hey, do you qualify as the dream partner of your dream partner? You fantasize about your dream partner, but have you ever thought what kind of partner does he/she dream of?
The cyclic process of “pushing yourself hard for a week, getting something done, and then feeling depressed and fucked up for the next week”
Sounds familiar? Read on.
We are all going to die, we all know that well.
Now I want to take you to a world of immortals where humans don’t die, they live and live and live and… you know, live. From now on, pretend I’m a human on this world of immortals, I’m immortal bitches.
I have been doing Open-source for a while, I don’t call myself an “expert” or something like that, but I’d like to share my opinion and experience on contributing to, and maintaining open-source code.
In this article, I’m going over creating an autocompletion/prediction system using a data-structure called Trie, it’s fast and easy to customize.
Array comprehension is a new feature proposed for ES7, with a new syntax to create new arrays from existing iterables, comprehensions can replace map and filter.
BroadcastChannel API is a new API used to communicate between same-origin tabs opened by the same user.
I’ve been working on the CSS Filter Editor widget in Firefox Developer Tools for a couple of weeks,
it should land soonIt’s here!. Thanks to Patrick Brosset for mentoring me and Tim Nguyen for his great contributions.
subscribe via rss