disvalued craft

most of the time project managers (in cases of non-agile team) tend to forget that end of the day, software has to delivered. thinking that by ignoring the non-functional requirements will save them cost. however, it is so obvious that as early as UAT, issues like slow server response time, hero developers cry for code rewrite, loss of repository data integrity, etc. what really cause these issues? well again, it is obvious. these managers believe that it is always the functionality that can only make the project owner happy. what can you do? what can we do? we are just developers. developers that can see through a fancy graphical interface. let's just wait and see until everything blows.

maven - convention over configuration

one of the features of maven is build automation. you can imagine ant with more advanced plugins and elegant environment development structure. if you are in the stage of inception of a new project, maven is the right choice. however, if it is a legacy java project, good luck. you may end up writing multiple poms trying to emulate a maven structure. maven is designed based on a template which is basically claimed as the combination of best practices in java development. if there will be a comprehensive tool to migrate legacy build platforms to maven, then maven will not be only "convention over configuration" but "configuration to convention".

javascript namespacing

before :

function myfunction() {
alert('before');
}

after :

var namespace = {
myfunction : function() {
alert('after');
}
}