<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on pepegar.com</title><link>https://pepegar.com/posts/</link><description>Recent content in Posts on pepegar.com</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 27 Feb 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://pepegar.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Tools for thought</title><link>https://pepegar.com/posts/tools-for-thought/</link><pubDate>Sat, 27 Feb 2021 00:00:00 +0000</pubDate><guid>https://pepegar.com/posts/tools-for-thought/</guid><description>For quite some time I’ve been searching for the best tool for supporting my studying. I’m a programmer, and am interested in quite a lot of different subjects, ranging from programming languages, distributed systems, compilers, machine learning, big data, etc.
Something I&amp;rsquo;ve noticed is that, propietary tools come and go, and having all your notes siloed on someone else&amp;rsquo;s servers is not what you probably want. So, I&amp;rsquo;ve been looking at plain text implementations of knowledge management systems lately.</description></item><item><title>Applicative Programming</title><link>https://pepegar.com/posts/applicative-programming/</link><pubDate>Tue, 20 Sep 2016 01:26:43 +0200</pubDate><guid>https://pepegar.com/posts/applicative-programming/</guid><description>I want to explore the Applicative functor, more than a functor and less than a monad. The reason to use it is that, by being less powerful, it can be applied in more situations.
This post is a companion to the talk I gave at HaskellMAD, you can find the slides of the talk here.
Applicatives or Idioms, as they were named back then, were introduced in 2008, in a Functional Pearl named Idioms: applicative programming with effects.</description></item></channel></rss>