10 Pines Blog
Agile2011 is over. Back to where it all began. and with most of the people that initiated this movement, 10 years ago. For me, it was my first Agile conference and I must say it was a blast. Being able to hear these guys in the different sessions and talk to them in the hallways during the breaks was amazing.
What I enjoyed the most? Let me think…
2 Sep 2011
smalltalk smalltalks-2010 agile
Click ‘Read on’ to see the presentation
12 Nov 2010
agile agiles-2010 story-mapping
Click ‘Read on’ to see the presentation
22 Oct 2010
Deploying Ruby On Rails in a Windows environment can be very painful. I couldn’t find any blog which really helped me, so I decided to summarize all the necessary steps I followed to successfully deploy a Rails application in a Windows 2008 server from scratch. I won’t give much explanation on each step, so if you like to know more about it, at the end of this post you’ll find a list of articles I found useful.
19 Oct 2010
agiles-2010 automatizacion agile
Las metodologías ágiles son muy claras respecto al siguiente punto: todas las tareas repetitivas que se realizan en forma manual deben ser automatizadas! Existen actualmente excelentes herramientas que nos ayudan a automatizar el build, las ejecuciones de los tests y el deployment de aplicaciones, pero comenzar a utilizarlas no siempre es una tarea trivial. En esta sesión presentaremos Maven junto con un grupo de plugins y herramientas que nos ayudaran a automatizar las tareas rutinarias cuando trabajamos con una gran aplicación multi-módulo Java enterprise.
13 Oct 2010
Patagonia is a conference registration web based system written in Pharo using Seaside, whose main purpose is to fulfill the ESUG conference registration needs. It was developed at 10Pines under the sponsorship of ESUG. It has been develop using some design principles that were “grown” developing other two systems, being Patagonia the latest version of them. These design principle’s objective is the development of “robust” software, that is, software that can easily change in a safe fashion, being at the same time self defensive when used incorrectly and self “teachable” to new programmers of the system.
2 Oct 2010
OOSCM (Object Oriented Software Configuration Management) is a tool we are developing to better support traits that are unique to object oriented development. Current SCM tools (CVS,SVN,GIT,Monticello, etc) are file based solutions, the file is the minimum versionable element, but when developing with objects files are not the elements we manage, we manage and version classes, methods, packages, etc. OOSCM will keep the history of changes of these elements (from basic changes like modifying a method to composite one like renaming a class) providing at the same time means to treat products, baselines, projects, etc. as first class versionable elements with the objective of helping team development in all its steps (programming, integration, etc). The talk provides a description of the tool’s objective, architecture and current development state.
2 Oct 2010
But … Isn’t this a requirement for all approaches? Why do I have the impression that in Agile, the technical aspect is more important? When I was at University, I remember vividly having heard (and unfortunately later repeated) that the programmer had one of the less important tasks in the chain of producing software. The most important, more senior and smarter people are the architects/designers that analyse and design the application, giving the programmers some diagrams that they ‘just’ have to translate into code. That seemed like an easy task!!
22 Jun 2010
Nowadays, more applications are RIA oriented solutions. RIA (Rich Internet Applications) is a new kind of application with more advantages than traditional applications. It emerges as a combination of features offered by web applications and desktop applications. Even multimedia capabilities are covered because these environments have internal players.
24 Sep 2009
testing smalltalk esug-2009 esug
During the 70s, mutation testing emerged as a technique to assess the fault-finding effectiveness of a test suite. It works mutating objects behavior and looking for tests to “kill” those mutants. The surviving mutants are the starting point to write better tests. Thus, this technique is an interesting alternative to code coverage regarding test quality.
18 Sep 2009