PUBLIC MARKS with tag dev-theory

The really interesting thing I want you to notice, here, is that as soon as you think of map and reduce as functions that everybody can use, and they use them, you only have to get one supergenius to write the hard code to run map and reduce on a global massively parallel array of computers, and all the old code that used to work fine when you just ran a loop still works only it's a zillion times faster which means it can be used to tackle huge problems in an instant.

- Normalised data is for sissies - Keep multiple copies of data around - Makes searching faster - Have to ensure consistency in the application logic

Here’s a radical idea: don’t even think of making your own language until you’re sure that you can’t do the job using one of the Big Five: XHTML, DocBook, ODF, UBL, and Atom.

Ce document présente la Programmation Orientée Objet (POO) du langage PHP.

These pages are a brief overview of each of the patterns in P of EAA. They aren't intended to stand alone, but merely as a quick aide-memoire for those familiar with them, and a handy link if you want to refer to one online. In the future I may add some post-publication comments into the material here, but we'll see how that works out.

MVC implementation in PHP

This site is an overview of agile development. It covers the foundations of agile development, the benefits it offers, and important topics such as contracts for agile projects.

Recursion is a tool not often used by imperative language developers, because it is thought to be slow and to waste space, but as the author demonstrates, there are several techniques that can be used to minimize or eliminate these problems. He introduces the concept of recursion and tackle recursive programming patterns, examining how they can be used to write provably correct programs.

Content, structure and presentation are now precisely defined, but I believe that the behaviour layer is too tight for javascript, javascript is not only about events, and separation is not good for the evolution of javascript. Modern javascript is in fact breaking the layer-model we thought was correct. I believe it’s perfectly logical to have presentational javascript which can go throughout structure and presentation.

With every programming language I have worked in it has become normal practice, after having developed an initial series of programs, to identify a common structure to which all subsequent programs should be built. This may take some time as it involves a bit of trial and error in playing with the different ways in which a task can be achieved in order to find the methodology that gives the most advantages in the long term.