54 karma · joined July 7, 2009
2010-03-01 07:16:21: (mod_fastcgi.c.2926) backend is overloaded; we'll disable it for 2 seconds and send the request to another backend instead: reconnects: 0 load: 131 2010-03-01 07:16:24: (mod_fastcgi.c.3569) all handlers for /haskell-json.fcgi on haskell-json.fcgi are down.
I doubt there were 131 requests to the FastCGI process at the same time but I'll have to seek more information about it. http://redmine.lighttpd.net/issues/1825
For now I've set it back to four backends as that never had this problem.
case fileExists "sausage.txt"
True -> putStrLn "Gonna do something with the sausage."
False -> putStrLn "Woop."
And/or if do fileExists "sausage.txt"
then putStrLn "Gonna do something!"
else putStrLn "Woop."
Or lambda with alternate lambda cases. (\case of (Just a) -> a; Nothing -> b)
I wrote a little mini-lang to do this to see how much I liked it. I liked it a lot, Lou!But Haskell is terse and predictable so one puts up with not having macros.
The Computer Language Shootout Haskell samples are low level, if you read them. Some are high level but many are nearly C, using malloc and such. But this is a good thing; you can write the "tight loops" that you need within Haskell.
People at work tend to yawn when I talk to them.
I predict nothing consequential will come of this drama.
This has broken grammar, and they can't spell ‘vigilant’. In the second paragraph. Don't the Telegraph writers use a spell checker? Well-written text is kind of important for a bloody newspaper. I'd send an errata to the author, but they don't provide an email address and the author's profile takes me to a 404 page. Also:
> Antibiotics are widely available to buy without prescription in India and Pakistan and this has meant hospital doctor there have had to resort to
Waves arms about.
Hello!? Writing standards!?
(define (add-squares x y)
(+ (* x x) (* y y)))
This is a program which evaluates a squares-adding language in which we have a limited number of expressions. Such as: (add-squares 2 4)
(add-squares (add-squares 4 3) 5)
etc.My last two job interviews lead to being hired, and my approach is generally:
(1) be very picky about which company I apply to; (2) go the company's web site to get a history, which is important for: (3) write an interesting letter saying what you like about the company, and give attachments and links to things that they can go take a look at, and (4) to actually provide some critique of the work the company has done, and provide solutions. Anyone can point out mistakes; we need someone who solves problems, like The Wolf.
Also, in reference to language skills, I like a quote by Dijkstra:
“Besides a mathematical inclination, an exceptionally good mastery of one's native tongue is the most vital asset of a competent programmer.”