The great thing about it is how it integrate with emacs/slime. For instance, let's say you want to close all the windows from the second/third workspace, you write the code in emacs and evaluate it in the context of stumpwm.

Here are some others:

   - Python/C API Reference Manual http://docs.python.org/py3k/c-api/
   - Higher-order functions and operations on callable objects http://docs.python.org/library/functools.html
   - Google http://www.google.com

IIRC, when calling a function, the compiler first looks at the name and only then will try to match the parameters (and choose the right function if there're multiple ones).

So, in that case, it tries to find a function with the name "func" in the Derivate class.. it finds one. Then, it tries to call it and fails because it has the wrong argument. I.e. It won't look at the Base class since it already found a function with the right name.

TL;DR: First = search by name, Second = Match parameters.

1. Find "all" the functions accessible bearing the same name. This would include functions available from the base classes.

2. Now match parameters

Seems like the order actually used is:

1. Find the function by name in the specific class (not including base classes)

2. If found, go to 4.

3. Include functions from the next base class (end if no more) and match by name only. Go to 2.

4. Try matching by name.

$('form').superLabels({ slide:false });

I've been a Perl hacker for 15+ years and still spend too much time reviewing code from CPAN to understand what's going on. I've been using Clojure for about 6 months and find that I can read and understand many of the major Clojure projects on GitHub quickly. Some may claim that says more about Perl than Clojure, but I'm chalking it up to Clojure :)

The summary:

- Any serious codebase is going to exceed the complexity you can hold in your mind at one time

- Once that happens, it's crucial that you can reason about the part you are focusing on

- Interactions between components are MUCH harder to reason about if they share mutable data

- It's possible to design cleanly isolated components in any language

- But we found that Clojure makes it natural to write concise, testable and isolated code

- So much so that writing sloppy/badly designed systems _feels awkward_ in Clojure

- For us, that was more beneficial than a book full of patterns or best practices

- YMMV, but I'd try it out and be sure to get over any aversion to Lisp before passing judgement

edited for formatting

This alone makes me think that Clojure developers are just regular people who care of the maintainability aspect of their code (and quite possibly the readability). Not just a "hacker" that writes code and jump into the next shiny stuff.

As a non-participating viewer from afar, Clojure community seems to have less hipster, less emotional, less roller-coaster, but more mature feeling when it comes to software development.

It also helps that they have a unified build+dependency tools, not a bunch of "upcoming great projects that will solve your build+dependency problem for the umpteenth time".

I wonder if the average age of clojure hackers is higher? I'm not in the Clojure community but it appeals to me (in my forties) coz... well... Lisp! Brings back fond memories of when I shared an office with the dude who did the Common Lisp implementation for Poplog.

The folk I know who are into Clojure are all in their 30s-40s.... but it's probably just sampling bias.

We are not going to get any younger so I very much welcomed the existence of such community.

However, I think the question was about projects built with Clojure, i.e. how to ensure that future developers in the company I work for will be able to continue where I left off? The global Clojure talent pool, while growing, is still on the small side (e.g. compared to even Ruby).

http://janestreet.com/minsky_weeks-jfp_18.pdf See part 4 "Personnel" for Jane Street's experience hiring OCaml devs.

That said, I don't think the matter is quite that straightforward where I come from; I would imagine Clojure dev head count in the whole of Finland is in the low double digits. If I were making business decisions involving future staffing, I would not feel confident I could replace the (hypothetical) only in-house Clojure dev in this job market.

That said, as others have noted, if you're hiring quality people, there's no reason they can't learn Clojure on the job. Plus if you make an investment in your people they're more likely to be invested in you ;)

That beauty transformed into this: http://www.youtube.com/watch?v=hY-vXcmpZIw

Please, don't blame the musicians.

Frank Zappa made a career of playing rock music instead of jazz or classical which many people consider a greater art form. It never was really "pop" music but still there are many that criticize him for it.

I'd be very careful to avoid derision on the basis of popularity. That fact that you have distaste for Lady Gaga's genre doesn't mean she's not a valid artist. There's a difference between relying on autotune because you're a talentless hack and an artistic decision.

I'm not blaming anyone - the music industry is a strange beast. But the true rarities are people like Gaga (as much as her I dislike her music), who can write and perform their own material well.

I feel like not doing so is really lacking respect for the teams who put hours filling it up. Add on top of that the fact that some demos are not even tried.

As some people like to say, applications are only for the people who didn't find a better way to get in.

It's not a matter of manning up or having respect. Do the math on what it'd take to email 3,000 rejected applicants.

Imagine reading 3,000 applicants!

1. How did you manage to get all these awesome resume templates?! That's fairly impressive for a one month project.. I could have had only one of them and I would be proud!

2. There's no talk about the 10,000$ in the blog.. where does it come from? Is it 100 sales? Is it less but with more urgent need (For instance, clicking "1 day" or "custom color").

3. About the process of converting the html template to a pdf.. how does it work and how good is it? For instance, is it a simple html->pdf which could give ugly conversion or end-of-page text to be displayed wrongly on the next page?

And as a suggestion, it'd be interesting to give a demo of the cv. For instance, I'd enter my data, it'd show me the resume but with a clear "Demo" written on each page of the pdf.. or something similar.

2) Yes, if you multiply the over 100 sales by our purchase price, we did over $10,000.

3) We don't convert html to PDF. Customers pick a resume design, upload their resume content (in Word or TXT or whatever,) and then we custom typeset it and send them a PDF as a digital file. Our graphic artists are great at making multiple pages look outstanding. There's also a revision process to make sure it pleases the customer.

4) The demos are really the designs you see on the site. Since all of our resumes are custom-typeset in inDesign by a graphic artist, we can't demo a customer's actual resume until we go through the entire process.

I don't know, I somewhat believe that once you put something on the web, be it facebook or not, it's now public. Yeah, on my facebook I have pictures that I'd rather not show to any employers but if they choose not to hire me for that, I'd rather not work at a place like this.

But, while writing this, I kind of realised that not everyone is in my position.. and not everyone is as open minded to accept homosexuals.. so I guess I understand what it's unethical.

There's a number of answers to that:

1) Biology is unfair. Birthing a child obviously takes much more effort and time from the mother than the father. We have societally chosen to make up for that a little bit by giving the mother a legally protected break from job demands.

2) It should come out in the wash on the back end. When it's time for reviews and raises, the new mother has three or six months less of productivity and accomplishments, so it's natural and not discriminatory for her to receive less reward here.

3) Maybe it IS unfair and that's why companies would seek to avoid hiring likely-to-become-pregnant women if they were not legally barred from doing so.

The truth is probably somewhere in the middle of all these, in different situations. Some women can bear a child and not miss a beat in productivity at a job. Some perhaps do use maternity leave as an excuse for a vacation.

In which case we should collectively pay for it rather than dumping the burden on her employer, especially since as you note that creates a disincentive to hire any woman of childbearing age.

When it's time for reviews and raises, the new mother has three or six months less of productivity and accomplishments, so it's natural and not discriminatory for her to receive less reward here.

Her attorney might see things differently.

And that's how it is in most of Europe, for example. But companies are still known to try to avoid it because of the hassle of getting a replacement for the duration of maternity leave.

If you make it clear in the interview that there is a deadline - we are working to a product launch in 6months and we need you to start immediately, and you took the job without telling them that you were immediately planning to take 6months off then the employer would have a pretty good case in most jurisdictions.

I did actually read The C++ Programming Language when I was in high school.. at that time I thought it was a very important book. Now, with the insight, how dull it was and useless!