The VB King

I recently came across a link http://stackoverflow.com/questions/218123/what-was-the-strangest-coding-standard-rule-that-you-were-forced-to-follow/220101#220101

In the past I have dealt with similar people and it has really given me a much greater appreciation for how politics are done.

As programmers we often wonder how someone like that gets in charge and stays despite protests.

I have two answers.

1.  Everyone just avoids the problem because they don't want to be the next target.  

2.  Because that person has never been challenged by any difficult programming they spent that time becoming a good business analyst.  But programming pays better so they claim to be a good programmer.

PHP/Coldfusion/ruby/etc and object oriented programming

Recently there has been a trend where all the web scripting languages have added in object oriented programming and all the developers of those languages are starting to try and make object oriented designs.

The big problem they seem to have is that they have learned their design off of relational databases and they don't really get that java has been wrestling with the object oriented/relational mismatch for 10+ years.

So they don't really get the advantages of mapreduce/nosql/etc aside from the fact that they have heard that it scales.  But on a more fundamental level it is about having one design rather than two designs that mismatch.

http://www.reddit.com/r/programming/comments/25su19/tdd_is_a_feedback_tool_not_a_religion/

Has a very good comment that basically describes the issue

• someone comes up with an idea
• others like the idea
• The less experienced use said idea to avoid making actual decisions
• The more experienced use it as another tool to make better decisions in general
• eventually the less experienced become experienced and start realizing the idea isn't the panacea they thought it was
• There's a backlash and lots of infighting
• It eventually settles down and everyone tends to have a more pragmatic idea of when it's best to apply the idea, and when it isn't. When it works, and when it falls down (and why). In other words, all of the infighting had a net positive effect.
• Someone comes up with an idea...
• Ad Nauseum.

Drools rules

Lately I have been looking at drools as an answer to dealing with simple rules that shouldn't involve an engineer.

So far I am impressed. Guvnor seems a little shakey, so I am sticking with the simplest features and a design that doesn't rely on it. But it aids in learning the language.

GWT and browser security

I used a html element for the submit button because it wasn't uploading the file otherwise.

Google app engine GWT limitation

Currently owned relationships are a bit fuzzy when it comes to lists. If you have an owned list and an unowned value the data wont persist. If both are owned then it will warn you.

Switching it all to unowned ihings for anything complicated is probably best.

Canvas only seems to work on large sizes

I will need to set it up so that all the objects are like size 90 instead of 1

for finding the rotaton of that canvas

// for(var i = 0; i < 3 ; i++){
// setTimeout( function (rotation){
// frontCanvas.transform.rotateX(-rotation);
// console.log(rotation);
// },500 * i,i);
// count = count + i;
//}