News for hackers. Stuff that matters.

skilldrick

Re:Magic in software development on Thursday April 28, 2011 @11:51AM (#2493782)
Haha I love "little laptop pixies" :) That's exactly what I was talking about.

I think I'm going to have to get this TECS book (no pun intended) - it sounds just what I'm after. Need to finish SICP first though :P Not enough hours in the day.

Re:Magic in software development on Thursday April 28, 2011 @11:04AM (#2493587)
Interesting. Yes, I came a similar route - no CS background. I read ESR's TAOUT [0], which assumes quite a high level of Unix knowledge - I'd love a book at that level!

[0] http://www.catb.org/~esr/writings/taoup/html/index.html

Re:Magic in software development on Thursday April 28, 2011 @10:44AM (#2493501)
Wow, those sound very interesting.

I've been toying with the idea of a series of blog posts (or possibly even a separate site) that give a bottom-up explanation of all the stacks we work with - starting with electronics => circuits => computers => programming languages. It would be a way of teaching myself the material and provide a useful resource to others.

Feels like a lot of work though :P

Re:Magic in software development on Thursday April 28, 2011 @07:42AM (#2492946)
That's kind of my point - you need to accept the 'magic' you're given, at least for the time being.

I feel a bit uncomfortable leaving it at that though, I always want to know how things are working. But it's not essential.

Re:Magic in software development on Thursday April 28, 2011 @06:39AM (#2492820)
Just so people know, I'm not talking Rails magic here - more the idea that there's stuff we don't understand that's going on that to all intents and purposes is magic. In other words:

> anything below your current level of abstraction that you don’t understand

Re:Closures explained with JavaScript on Friday April 22, 2011 @02:24PM (#2474920)
Crazy! Yeah, Metaprogramming Ruby is on my wishlist. I understand why the rules in Ruby are complicated - it's to make the common case simpler. But I still like the simplicity of JavaScript.
Re:Closures explained with JavaScript on Friday April 22, 2011 @12:46PM (#2474599)
Thanks, and a really interesting perspective.

I find Ruby's rules on scope (and pretty much anything) pretty confusing. I really like the way Ruby does a lot of things, but it doesn't have simple rules like JS.

I added this to the post in the end - on reflection I think you're right that it's worth mentioning.
Yes, I nearly put that in, but it didn't feel right. I've only given a very basic introduction to the language - the purpose of the blog was to teach the language rather than give its history.

Not quite - "Several brainfuck compilers have been made smaller than 200 bytes." - http://en.wikipedia.org/wiki/Brainfuck

Yeah, you're right about the cells usually being bytes. I followed the "spec" far enough for it to be a compliant implementation, but its fairly quick-and-dirty, and will probably break on more advanced programs.
Cheers :) Just give it half an hour...
Re:Zen and the art of statefulness on Monday February 14, 2011 @06:57PM (#2219322)
The point of an IIFE is that it is immediately invoked, i.e.: `(function () { })()` - the outer function is used to return the inner function at that point. So you're returning the inner function, and it's this function, a closure, that is returned.

I'm not sure what's iffy about the terminology here...

Re:A startup's "Why we use Lisp" story on Thursday January 14, 2010 @12:30PM (#1053068)
Of course! I take it all back.
Re:A startup's "Why we use Lisp" story on Thursday January 14, 2010 @11:57AM (#1052988)
I don't understand why a Lisp hacker wouldn't match parens properly when ending a parenthetical statement with a smiley:

  (commentless, of course :)
Hasn't he seen xkcd: http://xkcd.com/541/ ?