Category Archives: programming style

last day at be2, my career at be2 in a sequence of words

LinkedInGoogle BuzzDZoneDiggDeliciousShare
Posted on February 11, 2011 by Narek Alaverdyan

software engineering, java, j2ee, jboss, mysql email marketing, blacklisting, smtp, rmi, jms, crm, friends, travel, munich, specification, review, coding, esp, project management, gantt chart, matchmaking, tracking, pixels, company event, travelling, hibernate, spring, tomcat, invoker, redundancy, scalability, data complexity, performance,  partitioning, sharding, activemq, broker, soap, http call, queue, strategy, social networks, facebook, lean, agile, architecture,  scrum, scrum alliance, agile manifesto, sprint, continuous integration, hudson, static code analysis, transparency, communication, iteration, definition of done, spm, srm, user story, failure, success, confidence level, pair programming, retrospectives, groovy, grails, nosql, mongodb, rest, jersey, value stream, london, development management Continue reading →

Posted in Agile, Definition of Done, NoSQL, SCRUM, UnitTests, development, dynamic languages, groovy, pair programming, programming style, tdd, test-driven-development, value stream | Tagged , , , , , | 1 Comment

Pair Programming Matrix / Board

LinkedInGoogle BuzzDZoneDiggDeliciousShare
Posted on December 24, 2010 by Narek Alaverdyan

Pair Programming Matrix / Board

Pair Programming Matrix is a tool that helps the team to visualize the Pair Programming procedure. It shows who worked with whom, and who has not worked with anyone else at all.

Set up a board, that has a matrix with team Continue reading →

Posted in Agile, SCRUM, development, pair programming, programming style | Tagged , , , , | 13 Comments

Fighting the Software Uncertainty principle. SCRUM+TDD+CI+SELENIUM+cfEngine

LinkedInGoogle BuzzDZoneDiggDeliciousShare
Posted on December 20, 2010 by Narek Alaverdyan

“The outcome of the execution of E-type software entails a degree of uncertainty, the outcome of execution cannot be absolutely predicted”, or more fully, “Even if the outcome of past execution of an E-type program has previously been admissible, the … Continue reading →

Posted in Agile, Automated Testing, Definition of Done, SCRUM, UnitTests, checkstyle, programming style, tdd, test-driven-development | Tagged , , , , | 8 Comments

Hudson + Grails + CodeNarc -> Groovy Style Check

LinkedInGoogle BuzzDZoneDiggDeliciousShare
Posted on November 15, 2010 by Narek Alaverdyan

Today I am going to search for plug-ins for Hudson to analyse the quality of groovy code checked-into the repository. The build and test run processes are set up already and the code coverage reports are being generated. It is … Continue reading →

Posted in checkstyle, configuration, continuous integration, dynamic languages, groovy, hudson, programming style | 1 Comment