Category Archives: development

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

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

Build quality in every line of code produced

There is one thing in common with a lot of software development companies, or companies that have a software development unit. That’s the system labeled with the monstrous name “Legacy”.

So what’s in it, really?

Is your software change tolerant? Is your software easy to adapt to changes proposed by the business, or the tech department itself? Are you software’s modules independent and enable change? Does your software enable quick releases?

If you were nodding your head negatively about all of the above mentioned questions, then… I am really sorry but you’re dealing with Legacy software.

There’s something else that makes the system Continue reading

Posted in Agile, Lean, UnitTests, build quality in, development, testing | Tagged , , , , , | 18 Comments

Pair Programming Matrix / Board

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