Posted by Maarten Winkels mid-morning: April 20th, 2011
As promised in a previous blog, I’ll devote this blog to how to extend the RESTEasy framework with support for mapping form fields on object-graphs with complex associations, like lists and maps.
These extensions have been reported to RESTEasy as two issues with patches. If you like these features, please vote for these issues.
(more…)
Posted by Arjan Molenaar in the early morning: March 31st, 2011
When it comes to distributing Python packages, Python has its own mechanism. The tooling (either easy_install or pip) allows you to install a Python package and its dependencies. Typically, those packages are installed as Python Eggs (Java has Jars, Ruby has Gems and Python has Eggs). However, one can not expect Mac users to use these command line tools to download and install Python applications, especially GUI applications.
Posted by Niklas Odding mid-morning: February 28th, 2011
In my last blog I presented an illustration which shows the two primary aspects of the architects’ role. On one side they play a role in strengthening the heartbeat. On the other side, they play a role in envisioning the future.
The focus in this blog is on the solution architect or application architect. The way the Enterprise architect deals with Scrum will be explored more in detail in a later blog. This blog combined with the previous 3 blogs can be also downloaded as a whitepaper from the Xebia website: http://www.xebia.com/architects_scrum
What is the role of the architect?
Last blog I presented the illustration as shown below. In this blog I will focus on the parts of this illustration in which the solution architect / application architect plays a role
Posted by Herbert Schuurmans mid-afternoon: February 23rd, 2011
Changing to a new architecture can be a real pain. In particular if it changes from an unstructured architecture to an IT driven SOA. My current assignment “implementing an ESB” is just that. The process is slow, it is difficult to get something done and there seems to be quite a lot of resistance. I have given it a lot of thought why we can’t just build the damn thing. Our team has enough technical skills, we know what we want and how to get there. But apparently that is not enough to make it a success. Why is that?
Posted by Geert Bossuyt late at night: February 21st, 2011
I regularly run workshops to highlight certain aspects of an agile way of working and to help participants achieve a deeper understanding of these topics. I would like to share two of best received workshop sessions with you so that you can run them too. Today I’m describing the “Think Left” workshop.
During the “Think Left” workshop participants will work with the four values of the Agile Manifesto to gain a deeper understanding. In small groups each of the values will be worked on in a peer brainstorming fashion to better understand each of them. As a result of the workshop participants will realize that acting more on the left side or more on the right side of the Agile Manifesto is a choice.
Posted by Wian Vos in the early evening: February 21st, 2011
I am a strong believer in the fact that we don’t need Devops. We’ll at least I believe we shouldn’t need Devops. And I’ll tell you why.
Devops is a set of methods and procedures that is geared towards integrating the Operations specialist into the development team. This is done to the ends of developing an integrated software product consisting of the end-users application and related infrastructure components like middleware and operating systems.
Let’s take a closer look.
Posted by Geert Bossuyt at around evening time: February 16th, 2011
MoreAgile organizations support the following principles :
Complexity is a choice; we choose simplicity.
We carry out our vision and strategy
so that our people can make decisions in line with the mission of our organization.
Effectiveness is worth inefficiency.
We optimize the end to end value chain to maximize the result of our work.
We support selforganizing stable teams.
We create an environment that encourages people and teams to take responsibility and show entrepreneurship.
Our primary measurement for success is realized business value.
Our customers are the people that use our products.
Even when they are not the ones paying for our products.
We establish equal relationships on all levels
to empower knowledge sharing, commitment and shared responsibility.
We create opportunities from change, to continuously improve our products.
We prioritize all work in line with our vision and strategy.
Planning is a natural product of priority and sustainable pace.
We work smart, rather than hard, and learn every day.
Posted by Kris Geusebroek in the late evening: February 14th, 2011
At our project the focus is at making the application stable and controllable. So instead of building cool new features
we are spending our time making sure the application is able to run stable in the production environment.
After the first few issues the so called ‘Transaction timeout’ issue raised it’s ugly head.
Every now and then the application threw an exception due to a transaction timeout.
This was very strange since the timeout was set to 30 seconds and the complete processing of the whole
application was done in less than 2 seconds (spread over more than 1 transaction).
(more…)
Posted by Wilfred Springer mid-afternoon: February 9th, 2011
Roger Bodamer from 10Gen, the company that develops and supports MongoDB, has agreed to come speak about all things MongoDB on Wednesday February 16th, at Xebia in Hilversum. We will start with a basic technical introduction to MongoDB but Roger knows MongoDB inside and out so feel free to suggest topics that you would like to hear more about. Of course there will be a Q&A at the end.
For more information about Roger and 10gen, have a look at their team page (he’s third from the top).
Note that we need to put a limit on the number of registrants, so if you considered joining, register now. You can register at the Dutch NoSQL Meetup page found here.
Posted by Niklas Odding mid-morning: February 9th, 2011
In my last post I stated that there is a lot of emphasis on the fact that architects have to help to get the scrum team to work better, faster en with more quality. By following the agile values the architect will help “strengthening the heartbeat” of the scrum teams. However the activities of architects should encompass more. In this blog I will explain what this is and how to incorporate this in your way of working with scrum teams.