technologies used @ moccabeans
enterprice open source
we use a best of breed mix of open source projects that qualify for enterprise class project, have an active community and have been used before.
we started early with XP (extreme programming) with small teams, with big teams. with distributed teams, with critical clients and total non-believers. and we did fail in the beginning, XP needs experience, needs the right people and maybe is not for all projects.
for the last couple of year iterations (2 - 4 weeks) and unit testing have become the base of all our development. the first thing for a new team (new client/ new project) is to setup the process, explain, gently push people to use what has the biggest benefit for themselves and it works. over a couple of iterations the process becomes natural and developers don't want to miss it.
management usually takes longer to catch on, but the more the developers deliver predictable results and the more features are decided upon not via a checklist but whats needed, the more a user story not only defines a feature but also helps to get the customer to sign functions off as implemented, the more also management loves it.
latest in the game is scrum - very short daily meetings and no intervention during a scrum (iteration). management knows what gets delivered when and developers need not listen to ad hoc feature request.
we use everthing macintosh for our personal workstations and laptops.
want to know more? get in touch!
server side software
some of the projects we work with regularly and have developed expertise in bigger projects are apache, postgresql, jboss, tomcat, jetty, spring, xfire, imagemagick ....development tools
for development we use tools like eclipse, ant, maven, jira for project management and tracking.development process
we have been through many development processes over the years. from c and pascal to more object oriented objective c, c++, modula, some scripting, currently java but its not the language or the tools. its the process that makes or breaks projects.we started early with XP (extreme programming) with small teams, with big teams. with distributed teams, with critical clients and total non-believers. and we did fail in the beginning, XP needs experience, needs the right people and maybe is not for all projects.
for the last couple of year iterations (2 - 4 weeks) and unit testing have become the base of all our development. the first thing for a new team (new client/ new project) is to setup the process, explain, gently push people to use what has the biggest benefit for themselves and it works. over a couple of iterations the process becomes natural and developers don't want to miss it.
management usually takes longer to catch on, but the more the developers deliver predictable results and the more features are decided upon not via a checklist but whats needed, the more a user story not only defines a feature but also helps to get the customer to sign functions off as implemented, the more also management loves it.
latest in the game is scrum - very short daily meetings and no intervention during a scrum (iteration). management knows what gets delivered when and developers need not listen to ad hoc feature request.
webobjects
older projects are based on the still unbeatable - free but not open source - webobjects framework.some partners
we partner with linbit for linux and security projects and with indoqa for everthing cocoon.servers
we worked with oracle on projects for austrian airlines, die presse and others, support sun solaris for our apps but generelly we deploy on debian linux.we use everthing macintosh for our personal workstations and laptops.
want to know more? get in touch!