Just a quick thought for the day. I am building an AJAX PHP library .. (which is done) and am now implementing it into the vmFramework.. running into some odd things actually getting it to work with a MVC, but it’s coming along pretty good. It will be used for my next cash site.
15 Oct 2007 vMonkey 2 comments
Well, I revived the cash loan site for the fun of it. I took my old site and applied my MCD vmFramework to it. It seems to work pretty well, the site itself is still using a table type design rather than a CSS compliant version, but I didn’t want to take the time to convert that over also.
I did find one error in the framework code that I need to work out still. It is the handling of autoloading library files that are dependant on other libraries that either have not been loaded yet or have been loaded, but not initilized. A small bump in the road, but I’ll get it.
13 Oct 2007 vMonkey comments off
New favorite piece of code that I’ve run across:
if($var == '=='){ $var = '==='; } else { $var = '!='; }
11 Oct 2007 vMonkey comments off
I found this on my friend Ryan’s site/blog… I have pasted the first few paragraphs below and placed a link at the bottom for the full essay. I was intrigued by the authors ability to capture what actually goes on in a programmers head. Either way… a good read..
A good programmer working intensively on his own code can hold it in his mind the way a mathematician holds a problem he’s working on. Mathematicians don’t answer questions by working them out on paper the way schoolchildren are taught to. They do more in their heads: they try to understand a problem space well enough that they can walk around it the way you can walk around the memory of the house you grew up in. At its best programming is the same. You hold the whole program in your head, and you can manipulate it at will.
That’s particularly valuable at the start of a project, because initially the most important thing is to be able to change what you’re doing. Not just to solve the problem in a different way, but to change the problem you’re solving.
Your code is your understanding of the problem you’re exploring. So it’s only when you have your code in your head that you really understand the problem.
08 Oct 2007 vMonkey comments off