background preloader

Programming

Facebook Twitter

Monads

Typing Systems. Haskell. Programming conventions as signals. Programming conventions as signalsSome time ago, I spent a great deal of my waking and sleeping hours thinking about Contract Bridge.

Programming conventions as signals

I especially thought about bidding systems. Bidding in bridge is a very hard problem: you are trying to coöperatively seek a maximal payoff contract using an incredibly limited vocabulary that is a scarce resource: the pool of legal bids shrinks with each bid. And that’s without considering the fact that two opponents are competing for the same resource to try to seek your minimal payoff and frustrate your attempts to communicate. Anyhow. Given the limited information available, it is critical in bridge to use every possible bidding sequence productively.

Brainfuck. Brainfuck is an esoteric programming language noted for its extreme minimalism.

Brainfuck

The language consists of only eight simple commands and an instruction pointer. Nevertheless, it was shown to be Turing-complete.

Ruby

Lisp. Functional Programming. 10 Papers Every Programmer Should Read (At Least Twice) I spent most of yesterday afternoon working on a paper I’m co-writing. It was one of those days when the writing came easy. I was moving from topic to topic, but then I realized that I was reaching too far backward – I was explaining things which I shouldn’t have had to explain to the audience I was trying to reach. When I first started writing, one of the pieces of advice that I heard was that you should always imagine that you are writing to a particular person. Erlang. Linq. F# C# Delta Debugging - Chaire de Genie Logiciel (Prof. Zeller)

SOLUTION VS PROBLEM ABSTRACTIONS, DOES IT MATTER? As Google just launched a "new" general purpose programming language (what for?)

SOLUTION VS PROBLEM ABSTRACTIONS, DOES IT MATTER?

More and more people are asking about and somewhat demanding better abstractions. The question is should they be problem or solution side abstractions or possibly both? Udi recently complained about solution side abstractions: A re-introduction to JavaScript. Why a re-introduction?

A re-introduction to JavaScript

Because JavaScript is notorious for being the world's most misunderstood programming language. It is often derided as being a toy, but beneath its layer of deceptive simplicity, powerful language features await. JavaScript is now used by an incredible number of high-profile applications, showing that deeper knowledge of this technology is an important skill for any web or mobile developer. It's useful to start with an overview of the language's history. JavaScript was created in 1995 by Brendan Eich while he was an engineer at Netscape.