So I solved this Lychrel problem with about 5 lines of code that consisted of a recursive definition and a lambda expression. When I first saw recursive stuff, I didn't quite get it. And I'm unsure if I do yet, but I'm at the point where I design programs with recursive functions without even noticing it. Just seems so much more elegant than some while loop. Moral is that Functionally Imperative is awesome. I can't stand purely functional, but I find myself afloat in goo when mucking in the ugly of imperative. I've even looked at the prefix f(x) notation a couple times confused, thinking it might actually be easier to look at it as (f x)

(Python is a bit of a hack on the functional stuff, like how lambdas can only be single expressions (And recursive functions don't even get tail recursion optimizations). They say nobody uses the functional paradigm of Python, yet I see it being used everywhere. Inside and out, I just couldn't see Python in the same light without it(I like brief code too, I've kind of been wanting to use some APL rooted languages. Too bad that besides J there's only K (I suppose the APL niche is a hard one to fit that many languages in, so not surprising). And that one is proprietary. I cry for the world that let's a language be owned(Oh well, got J working. Silly things requires I press CtrlR to test, such a strain)))

So, to keep you unbored with all my python blah, a find by Jukio:(I've been using colons more. I even tried using a colon after an if with GM while doing Parallax)

Got me off of Endosymbiosis for writing music

I should go write that assignment now that I need a 50 on to pass Careers and which is needed to be completed by Wednesday. But it just seems so oblong

I've finally been able to complete the impossible task of getting the ever so unaggressive Poly angry. I lay the mockeries to rest, at last