Mickaël’s Weblog

Pour ceux (en france) qui ont reçu un avertissement comme quoi ils utilisaient un logiciel peer-to-peer, voici un site de vidéo clip tout ce qu’il y a d’officiel : http://www.jukebo.com/.

Ce site est sponsorisé par la pub ce qui permet de redistribuer des droits aux auteurs.

Deplus, vous pouvez récupérer le morceau d’HTML permettant d’inclure les vidéo de votre chois dans vôtre propre site.

Les internautes peuvent poster des vidéo, mais le site recherche aussi automatiquement sur internet les vidéo de bonne qualité pour un clip donné.

Voici une vidéo de James Blunt:

Fredrik has written a nice post on AOP : Remove code smell with AOP.

I’m personnaly not a fan of AOP. Sure, it can be extremely useful in some areas…exactly as is describing Fredrik. The only concern I have, is that AOP pros are always using the same argument: it’s useful for log, security, authentication…etc. I fully agree: AOP is useful for transversal services and ensure a better separation of concern…but I do not think AOP is more useful than this.

I’ve seen recently another case of usage of AOP. We are looking at adding unit test for a web application using mock. The problem is in this kind of code:
[java]
public List getFirst(int count)
{
  Context context = JsfContext.getInstance() …
[java]
Mocking works well if you inject interface, but in our case we have to deal with the singleton’s hell.

In this case AOP can provide an answer even if can only be temporary has this kind of design is not fine for me (singleton vs DI).

“Reusablility is just a welcomed side-effect.”

I agree on this assumption, and reusability should definitly not be a graal or a goal…simply something to have in mind when designing.

There are so much more realistic concepts as Separation of Concern and Single Responsability for example. How many times a componant or a (set of) class(es) that were supposed to be reusable and finaly completely rewriten as soon as they are reused.

Product owner is a role within scrum methodology that represent the customer. The question is about a team that would like to apply Scrum methodology without such role.

The answer is definitely “No” obviously. How to use such methodology in an organization that do not provide such role. I think this can be hardly achieve by managers assuming this role but they have to be fair. The team will assume its responsibilities (sizing, self organization…etc) and the manager will validate the acheivement of the stories even if this has no value from a customer point of view. The manager then will do the buffer with the “real” customer, and takes his responsibilities.

The hard point is for the manager:

• have an iterativ approach at least (1 month is perfect) 
• create new user stories if the customer is not fully satisfied with the implementation and track them as new items,
• describe precisely the content of the user stories to help the team do a precise and accurate sizing,
• provide support to the team if they have questions on the impelmentation during the srpint,

The key point is not to have a manager which is only simple bridge between the customer and the dev team, but fully assume the role of Porduct Owner. Sure this is not easy, but this can be done this way.