Accéder au contenu principal

Reporting Tool

Reporting time used in project is a boring task that most of us must do to please our manager, especially in big firm.

Why is it boring ?
Because it has no interest for the worker ? And why tell what we are doing if the work is done ?
Because we must do it multiple times ? One for the accounting departement, one for the project manager and one during team meeting ?
Because the tool are frequently slow and horrible to use ?

I think we can find many reasons to hate reporting our work time.

However It's an important thing to keep track of what are you doing for your managers but also your coworker and even for you.

So why not try to change a boring into something usefull ?

I have some ideas and I want to try to present something.

To help me, I have recently discover Grails. Yet Another new java framework ? oh yes but this one is really cool. It takes the main idea of Ruby on rails with all java environnement.
The most impressive advantage of Grails is that you can have your next Web 2.0 project done in weeks instead of months.

I have let aside this project for too long and I hope I will keep enough time to advance this project. Moreover I will try to present some info about my advancement. Maybe directly on my twitter account because it's more easier for me for quick update.





Commentaires

Posts les plus consultés de ce blog

Summary of 'Clean Architecture' by Robert C. Martin

Summary of 'Clean Architecture' by Robert C. Martin
Uncle Bob, the well known author of Clean Code, is coming back to us with a new book called Clean Architecture which wants to take a larger view on how to create software.

Even if Clean Code is one of the major book around OOP and code design (mainly by presenting the SOLID principles), I was not totally impressed by the book.

Clean Architecture leaves me with the same feeling, even if it’s pushing the development world to do better, has some good stories and present robust principles to build software.

The book is build around 34 chapters organised in chapters.
Programming paradigm After some introduction, there is an overview of three paradigm of programming:

structured programming which imposes discipline on direct transfer of controlobject oriented programming which imposes discipline on indirect transfer of controlfunctional programming which imposes discipline upon assignment

Uncle Bob tells us that each of these paradi…

Summary of 'Words are windows, Introduction to nonviolent communication' by Marshall Rosenberg

Summary of 'Words are windows, Introduction to nonviolent communication' by Marshall Rosenberg
“Words are windows” is an introduction to non violent communication (abbreviated as NVC). Marshall Rosenberg presents in this book the process that allows us to communicate more serenely with others as well as with ourselves. This mode of communication allows us to become more and more caring, authentic, and empathic with others. It can therefore be used in all interactions of everyday life: as a couple, with our children, at work … NVC is proving to be a very effective way to manage conflicts, and also to better identify our own needs.

At the source of Non Violent Communication NVC has 4 four key components:
Observation – specific facts/data, no evaluation/judgmentFeeling – state how we feel (many failure modes here)Need – the need underlying this feelingRequest – must be specific action to address need
First we observe what is really happening in a given situation. These observatio…

Le développeur incompétent est un mythe

Sous ce titre complètement arbitraire et très clairement provocateur, je vais passer un contre pied aux derniers articles que j'ai lus sur le métier de développeur.
Par exemple :
http://patricelamarche.net/2011/05/24/lincomptence-des-dveloppeurs/ 
http://blogs.codes-sources.com/tja/archive/2011/10/04/etre-un-bon-d-veloppeur-c-est-aussi-une-question-d-attitude-personnelle.aspx 
Ça tombe bien c'est juste avant la soirée du Paris JUG sur le métier de développeur ! Et comme on se plaint que les présentateurs ne sont pas de vrais (?) développeurs, je vais en profiter pour donner mon avis.

Alors voila, d'après ces articles, un bon développeur connait ses fondamentaux.
Ok soit mais quelle est cette liste de fondamentaux ? 
Chez certains, c'est les maths et l'algorithmie pure, d'autres c'est C++ par coeur et savoir retourner une chaine de caractère en moins de 3 instructions et une seule allocation mémoire, d'autres c'est Java JEE, ses 100 jsr et frameworks in…