** UnhandledExceptionEventHandler :: OFFICIAL LC / CHATTER THREAD **
06-24-2012
, 11:13 AM
I wonder how much space you'd need if you'd do a daily wikipedia diff. Might be fun to keep an uptodate wikipedia on some machine with daily diffs so you can trace how it developed etc 
06-24-2012
, 02:42 PM
06-24-2012
, 07:39 PM
Well, okay, I had to look that one up. In writing circles, this is considered by many to be the "writer's curse," in that once you write down the entire issue, you no longer have an issue, and thus nothing to write about. Sort of like "You don't give up on The Blues, The Blues gives up on you."
Let me now continue talking to the rubber duck. or in my case, my pillow, since I am lacking in the stuffed / fake animal department, which apparently needs to be fixed if I ever want to consider myself a valuable piece of the programming world...
This isn't technically the first time I've been exposed to it. It was the first time I realized it, and now my entire sense of the world is blown.
This one piece of code encapsulates the entire first 3 chapters of SICP:
Basically, the book introduces some easy concepts at each chapter, and toward the end, there is some notion of how to create code from pure magic. All this time, yes, create a function that takes a function as an argument and returns a function as it's answer, which can be passed into a function that returns a function as an argument, which....
Then there is one part where they talk about queues and using queues to emulate signal and message passing, and all of this really breaks down into seeing how to write the nth variation of factorial(n).
And of course, data abstraction, encapsulation, and modular design paradigms.
The above is an over-simplification for certain, but the code in question truly exposes and explains all of it in on tight package, and I've never been able to think of how it all comes together and how it is used in a specific example.
To create a new page:
simply pass an argument into a new function.
Up until the toy, I was thinking that web pages where made sort of like this:
So that in the file system, there is one distinct page for each page.
I never really seen Clojure code before, but I know that it is hard-core functional, and I know that there is a way to create code from magic. And noir has a link to this fully functional blog:
https://github.com/ibdknox/Noir-blog...views/blog.clj
And woah, there it is! I see that it's possible to have one page that creates N pages. How cool is that? 90% of what is visible in amazon.com could literately be one 200-line file that does a database call and creates thousands of product pages!
Those 2-3k lines of code transcribed + hw from SICP finally adds up to a whole piece. I'm still reeling after 2 days.
edit to add: Of course, I don't know which technique creates a faster page: individual files or one file.
Yeah, I've been thinking all this time that web coding is the dumbest thing in the world. Of course, this is coming from a guy who hard-coded HTML and CSS for the past few years, can't do JS or PHP, and thought Drupal was the shiz-bomb.
Now with something like this, the whole thing can be very interesting.
Let me now continue talking to the rubber duck. or in my case, my pillow, since I am lacking in the stuffed / fake animal department, which apparently needs to be fixed if I ever want to consider myself a valuable piece of the programming world...
This one piece of code encapsulates the entire first 3 chapters of SICP:
Code:
(defpage "/" []
(common/layout
[:h1 "Hello!"]
[:p "you are on page "]
[:p "see ya!"]))
Then there is one part where they talk about queues and using queues to emulate signal and message passing, and all of this really breaks down into seeing how to write the nth variation of factorial(n).
And of course, data abstraction, encapsulation, and modular design paradigms.
The above is an over-simplification for certain, but the code in question truly exposes and explains all of it in on tight package, and I've never been able to think of how it all comes together and how it is used in a specific example.
To create a new page:
Code:
(defpage "/new-page" []
(common/layout
[:h1 "Hello!"]
[:p "you are on page "]
[:p "see ya!"]))
Up until the toy, I was thinking that web pages where made sort of like this:
Code:
import_template = (.....) new_page = (.....) Do code here: Name the new_page to something_else Export to file something_else.php(?)
I never really seen Clojure code before, but I know that it is hard-core functional, and I know that there is a way to create code from magic. And noir has a link to this fully functional blog:
https://github.com/ibdknox/Noir-blog...views/blog.clj
And woah, there it is! I see that it's possible to have one page that creates N pages. How cool is that? 90% of what is visible in amazon.com could literately be one 200-line file that does a database call and creates thousands of product pages!
Those 2-3k lines of code transcribed + hw from SICP finally adds up to a whole piece. I'm still reeling after 2 days.
edit to add: Of course, I don't know which technique creates a faster page: individual files or one file.
Now with something like this, the whole thing can be very interesting.
06-24-2012
, 09:44 PM
06-24-2012
, 10:02 PM
06-24-2012
, 10:41 PM
i try to stick to the defaults as much as possible when learning a new system. then i don't have to worry about whether my non-standard configuration is somehow causing the next weird problem.
worry about other stuff when you have a use case. learning a new language and a new web framework will keep you plenty busy on their own
.
worry about other stuff when you have a use case. learning a new language and a new web framework will keep you plenty busy on their own
.
06-25-2012
, 01:19 PM
06-25-2012
, 02:37 PM
06-25-2012
, 02:47 PM
06-25-2012
, 02:59 PM
06-25-2012
, 04:21 PM
06-26-2012
, 12:20 AM
06-26-2012
, 12:31 AM
