I've been studying some Lisp recently. Yesterday before I fell asleep, I was thinking about how to implement a certain algorithm. And when I wake up, I felt like a list!
That was wierd.
I have experienced something similar many times before (like, seeing brown checkered patterns after playing too much Sonic The Hedgehog), but not like this.
Have any of you guys ever felt like you were a datastructure?
Too much Lisp
Started by geon, Jul 27 2007 06:02 AM
8 replies to this topic
#2
Posted 27 July 2007 - 07:46 AM
We're all just compiled DNA scripts..
http://iki.fi/sol - my schtuphh
#3
Posted 27 July 2007 - 08:30 AM
I was just going to say. You are nothing but the product of a digitally encoded ternary datastructure.
If Prolog is the answer, what is the question ?
#4
Posted 27 July 2007 - 12:40 PM
yep!, thats too much lisp for you....
you need a vacation...
or, a girl...
you need a vacation...
or, a girl...
#5
Posted 27 July 2007 - 02:23 PM
Probably a vacation. I'm already married. :happy:
#6
Posted 03 August 2007 - 08:44 PM
Dude, I know exactly what you're talking about.
For roughly 1½ weeks now I'm working on an instruction scheduler for C64Plus DSP code. I spare you the details, but that job is much more complicated than scheduling for vanilla CPU code, and that's non-trivial either. You do one simple mistake and the DSP will do mess up big time. The rules and constraints even change if you have interrupts enabled or not. Strong tabacco - hardcore assembler coding - even for someone who claimed he has seen it all.
DSP-coding is not for pussies
After the second day, when I had enough framework stuff done to sequences simple code sequences, my brain had endless fun to dream up difficult instruction sequences and I scheduled them in my dreams. I still do so, every night. Excessive drinking and having fun with my fiancée does not help.
I've asked myself why I ever started to write an algorithm to do the scheduling job for me. After all - I'll be most probably the only guy who will ever use the scheduler (just joking - that code will schedule Just-In-Time compiled code and has to deal with several million variants of different rendering and blitting variants. I could get better code using precompiler tricks, but the sheer amount of code won't fit on a DVD - let alone the compile time).
I think working and thinking about new and interesting stuff. Something that opens new perspectives and ways to tacke a problem - let it be lisp, or dynamic code generation, or a new concept or whatever - happends not only in the hours you sit in front of your computer. If you explore such new things and you're a "real coder"™ you'll think about it 24/7 until the day you have grasped the concept. Gained insights and now what's doable for you and what not
You're not alone,
Nils
Btw - I've spend the last two days doing different stuff (writing documentation, doing minor enhancements to old projects) just to take the burden of my mind to constantly think about that crap.
For roughly 1½ weeks now I'm working on an instruction scheduler for C64Plus DSP code. I spare you the details, but that job is much more complicated than scheduling for vanilla CPU code, and that's non-trivial either. You do one simple mistake and the DSP will do mess up big time. The rules and constraints even change if you have interrupts enabled or not. Strong tabacco - hardcore assembler coding - even for someone who claimed he has seen it all.
DSP-coding is not for pussies
After the second day, when I had enough framework stuff done to sequences simple code sequences, my brain had endless fun to dream up difficult instruction sequences and I scheduled them in my dreams. I still do so, every night. Excessive drinking and having fun with my fiancée does not help.
I've asked myself why I ever started to write an algorithm to do the scheduling job for me. After all - I'll be most probably the only guy who will ever use the scheduler (just joking - that code will schedule Just-In-Time compiled code and has to deal with several million variants of different rendering and blitting variants. I could get better code using precompiler tricks, but the sheer amount of code won't fit on a DVD - let alone the compile time).
I think working and thinking about new and interesting stuff. Something that opens new perspectives and ways to tacke a problem - let it be lisp, or dynamic code generation, or a new concept or whatever - happends not only in the hours you sit in front of your computer. If you explore such new things and you're a "real coder"™ you'll think about it 24/7 until the day you have grasped the concept. Gained insights and now what's doable for you and what not
You're not alone,
Nils
Btw - I've spend the last two days doing different stuff (writing documentation, doing minor enhancements to old projects) just to take the burden of my mind to constantly think about that crap.
My music: http://myspace.com/planetarchh <-- my music
My stuff: torus.untergrund.net <-- some diy electronic stuff and more.
My stuff: torus.untergrund.net <-- some diy electronic stuff and more.
#7
Posted 04 August 2007 - 10:57 AM
Yeah, hell, it was the same here. I was working on my university homeworks like mad for the last two weeks - I always wanted them to be PERFECT, so I wrote and wrote and wrote... Aside from that, I've been working on a project to optimize the number of layers on a board needed for the hardware implementation of a digital scheme and it turned out that I would dream of ROBBDs multilayer gatters and matching of binary trees. Wicked...
#8
Posted 04 August 2007 - 03:05 PM
"Stupid bug! You go squish now!!" - Homer Simpson
#9
Posted 08 August 2007 - 04:46 PM
geon said:
Have any of you guys ever felt like you were a datastructure?
I wonder if that makes me "procedural" rather than a "data structural"?
geon said:
I have experienced something similar many times before (like, seeing brown checkered patterns after playing too much Sonic The Hedgehog), but not like this.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












