Although many of my disaster stories involved places I've worked, this one takes place in the city I live in, Arlington, Texas. The Story Arlington is best known as the largest city in the US with no public transportation, and home of one of the most dense retail

I read Programmers Don't Like to Code a few weeks ago and spent some time thinking about it before wanting to comment. There is much to like in the article yet I'm not sure I can really agree with the title. If you ask any real

One sign of a good programmer is their absolute need to understand. Whether the environment they are coding in, the language or frameworks they use, or even the theory behind what they are trying to develop, the need to understand is a driving force in people who make good programmers.

After seeing this Programming Languages Chart again, I thought about all the programming languages that I have learned and actually written code in: * Dartmouth Basic * Fortran II * APL * Applesoft Basic * 6502 assembly * Z80 assembly * Fortran 66 * IBM JCL * Fortran 77 * Jovial J73 * Mil Std 1750a assembly * Z8000 assembly * Turbo Pascal

Since returning to Apple ten years ago, almost everything that has come out of Apple has been amazing. Not everything has been successful (the Cube) but everything has grabbed people's attention in ways no other technology company has. The primary reason is that Steve refuses to put out

The Apple iPhone is the world's first (as far as I know) portable device with a fully programmable interactive user interface. That is the real revolution that will affect us all in the near future. Other than a few simply buttons, the entire functional interface of the iPhone

During my many years as a consultant, contractor and employee I've seen a lot of really bad code, especially in larger companies. So who's to blame? The funny thing is that is isn't usually the programming staff that's to blame (though it