Skip to main content

Coding Horror: The PHP Singularity

Media_httpwwwcodingho_fldkj

A good take on the ghoulery of PHP. It's a fairly extreme viewpoint as there are plenty of people making good products from PHP and that's what the real result should be, not just good quality code bases (although the two depend on each other after a couple of iterations of development).

The real problem is people. You could invent a new programming language, one to rule them all... but there will always be crap programmers. People who don't care that much about it, just do a bit on the side, work for themselves and just lay little bad eggs for multiple customers and move on. There are still people I have spoken to *very* recently that were arguing against design patters / OO programming and other fundamentals. You won't escape that. The answer is to chill out about it. The more crap programmers, the better you will look and the more it will keep you in work sorting out their mess.

So really what I am saying is "Thank you crap programmers" :-)

Comments

Popular posts from this blog

NESTA - Next Gen.

via nesta.org.uk Following on from an article on the BBC about Raspberry Pi, this next gen report has some interesting findings. The scariest stat which I picked out from the BBC website was "out of the 28,767 teachers who were awarded Qualified Teacher Status... in 2010, only three qualified in computing or computing science as their primary qualification" Having worked as a computer science teacher for a year in a school that was a specialist in Computing I can concur that the uptake in Comp Sci was woeful. 2 Students for A2... The other teachers backgrounds in Computer Science was also fairly woeful (most knowing a bit about Office but still a paltry amount even about that). I couldn't speak for my counterpart that I was covering however. I suspect they were fairly up on things. All in all what kills me is that Computer science is not a secondary level subject. Areas are often covered, a little in IT, a little in DT subjects (if kids choose Systems and Contr

Accessing the UI Thread with Tasks in F#

I have a Windows Forms program written in F# that can deploy a code base to n number of sites at once (you select the sites you would like to deploy to and it goes off and completes a number of tasks (backing up current sites, various unpacking and moving of files etc... ). Once you start it, it begins it's merry journey and begins to update the UI with what has happened. At the moment this method of updating the UI is not pretty because the threads I am doing the work on can't update the UI so I perform some fiendery to make that happen (don't ask). I knew there was a better way using some newer .NET features but I just hadn't got round to having a fiddle yet. I have now found that if you use the built in Task class but break your code up in a nicer way and then chain the tasks together you can then pass the correct context into the task that you want to talk to the UI. Here's a little script to give you a feel for it. You can press the "start" butt

Reigniting posterous again perhaps

I'm taking another look at Posterous again. I'm not really sure why as I haven't written a proper blog for a while but this seems an easy way to share between all my other tings...