Como me preparou a Orde de Operacións para a Programación

Algebra has always been a favorite subject of mine. There's not much theory involved, just a toolbox of methods and the order of operations to solve in. If you reach back into high school, you'll remember (quoted from Math.com):

1. Primeiro faga todas as operacións entre parénteses.
2. A continuación, faga calquera traballo con expoñentes ou radicais.
3. Traballando de esquerda a dereita, fai toda a multiplicación e división.
4. Finalmente, traballando de esquerda a dereita, faga todas as sumas e restas.

Here's the example from Math.com:

Aplicar isto ao desenvolvemento é bastante sinxelo.

1. Operations within the parenthesis equates to my page layout, in a simple HTML format. I begin with a blank page and steadily populate it until it has all of the elements I'm looking for. To ensure flexible user interface design, I always work with XHTML and CSS. En calquera lugar onde haxa expresións (por exemplo, base de datos ou resultados programáticos), comento o código e escribo texto ficticio, imaxes ou obxectos.
2. A continuación, traballo con calquera expoñente ou radical. Estas son as miñas funcións programáticas ou de base de datos que extraen, transforman e cargan (ETL) os datos como desexo amosalos na miña páxina completada. Realmente traballo nos pasos nesa orde a menos que o formato na consulta real produza un mellor rendemento.
3. A continuación é a multiplicación ou división. Aquí é onde simplifico o meu código. En vez dunha enorme escritura monolítica, eu abstracto tanto do código como podo incluír ficheiros e clases. Co desenvolvemento web, adoito traballar de arriba a abaixo, por suposto.
4. Finalmente, traballando de esquerda a dereita, toda suma e resta. Este paso é o proceso final, aplicando as últimas noticias de validación de formularios, compoñentes de estilo, manexo de erros, etc. De novo, adoito traballar de arriba a abaixo.

Good development is not any more complex than a great Algebra problem. You have variables, equations, functions… and a logical order of operations to get the best results. I see a lot of hackers that simply ‘get it to work' but you find (as I have) that if you don't plan out your methodology and take a logical approach, you find yourself writing your code over and over and over when problems or changes are needed.

Algebra has always been a lot like a jigsaw puzzle to me. It's always been challenging, fun, and I knew a simple answer was possible. All the pieces are there, you just need to find them and put them together correctly. Writing code is no different, but it's more enjoyable because your puzzle output is whatever you would like it to be!

I'm not a formal developer, nor am I even a great one. I have; however, received compliments on the code I've written throughout many projects. I believe much of it is because I do a lot of preplanning, whiteboarding, schema extraction, etc. before I even write that first script tag.