Things I Want in Common Lisp

This post contains some things I want in Common Lisp, in no particular order. I’ll try to keep things short and to the point.

Shared Libraries

Right now, the concept of a “library” in idiomatic Lisp is a .asd file along with some Lisp source code. I don’t always want to distribute the source . . . → Read More: Things I Want in Common Lisp

Programming as a Profession

Thomas, a friend of mine, recently posted an article on his experiences in programming in an enterprise environment. In particular, he talked about someone called the Career Programmer. Very minimally paraphrased, a Career Programmer is described as follows.

We’ve all seen them. The ones who never coded in school outside of assignments. These . . . → Read More: Programming as a Profession

Culture Shock: Programming for the Enterprise

As a disclaimer, this is my experience, and not a broad generalization about enterprise work environments, or the software industry as a whole.

Background.

Some background about myself will probably help you understand where I’m coming from, so here’s the skinny: I’ve been developing software for a decade, and contributing to open source projects . . . → Read More: Culture Shock: Programming for the Enterprise

Becoming Patient in Writing Programs

People say writing Lisp will change the way you think, and most often that is referring to the sorts of paradigms that Lisp programs typically follow. After having programmed some non-trivial Lisp, you will more easily see things like code-data duality, functional patterns, expression-oriented programming, and so forth. But I’d like to mention one . . . → Read More: Becoming Patient in Writing Programs

The Wretched Google Interview Experience

I would like to describe my experience interviewing with Google, and specifically outline why I thought the experience was poor by way of telling my story. As you shall see, this will be especially difficult to convey because you, the reader, will likely be convinced my poor experience is likely only a result of . . . → Read More: The Wretched Google Interview Experience