fix(yagni): stop doing useless things

** Estimate 1 vs 100 mais pas 5 vs 8 ( la loi de delphin = vous mettrez toujours deux fois plus de temps que hestimé meme si vous appliqué la loi de delphin)

** Je sais pas mais je dirais 5j FTG (tu viens de t'engager et de te foutre dans la merde (passer pour un incompétant et engagé))
** Suffixer ou Prefixer une interface
** Créer systematiquement Itruc et TrucImpl



** venir avec son pc en reu
** fonction utils array to map ...

@Nathan_damie

@delphinaubin

nathandm

delphinaubin

 mettez toujours en œuvre les choses quand vous en avez effectivement besoin, pas lorsque vous prévoyez simplement que vous en aurez besoin

Ron Jeffries

 Arrête de te prendre la tête

Nathan Damie

Do all my contributors need to use the conventional commit specification?

No! If you use a squash based workflow on Git lead maintainers can cleanup the commit messages as they’re merged—adding no workload to casual committers. A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.

 

Choose your git workflow

Git Blame

 

Git Annotate

Git blame, git annotate

===

Mais qui a fait cette  ******  *'********

Git blame, git annotate

===

Mais qui a fait cette erreur d'innatention





style(git): remove useless commit / convention

* Commit convention for important commit

* Stop merge, prefer Squash and merge

* Adapt your workflow

* Stop git blame, git annotate

/**
 * Return the User who match the given id
 * @summary get user by id
 * @author NathanDM
 * @public
 * @param {string} The id of the user we are looking for
 * @return {User} The user corresponding to the given Id
 * @throws {NotFoundException} if no user matches the given id
 * @example
 * // return { firstName: 'John', lastName: 'Do' }
 * getUserById('12345');
 */
function getUserById(userId: string): User {
    
}






function dataTransfert(): void {
    // extract data from the system
    var externalData = Extract();
    // Transform Data for the transfert
    var formattedData = Transform(externalData);
    // Load transformed data
    Load(formattedData);
}



/**
 * Return true if valid
 * ...
 */
function isValid(): boolean {
    return true;
}




/** 
* Jira-330
*/
function isValid(){...}


 
    if(((y %4==0)&&(y %100!=0))||(y %400==0)){
        return d + 1;
    } else {
        return d;
    }


    // add 1 days if leap year 
    if(((y %4==0)&&(y %100!=0))||(y %400==0)){
        return d + 1;
    } else {
        return d;
    }

    
    if(isLeapYear(year)){
        return numberOfDays + 1;
    } 

    return numberOfDays;

Si vous êtes sur le point d’ ajouter un commentaire, demandez-vous d’abord comment améliorer le code pour le rendre inutile

As a User I want to have my data quickly so that I can be a happy user .

As a Boss I want to have cache .

As a Developper I want to set redis so i can 

impress my coworker and improve my CV.



var cache = { "the": "cache",
              "is": "not",
              "always": "THE",
              "solution": "!!!",
              "A": "good",
              "old": "variable",
              "often": "do",
              "the": "job !" }

As a Product Manager I want a table in db so I can change data in production .

As a PO I want to change configuration without  re deliver the application

  • Sprint Planning

  • Sprint

  • Daily

  • Sprint Retro

  • Demo

  • Know the TODOs

  • Deliver quality, fail fast

  • Synchronize

  • Improve

  • Get feedback from the
    client and interact

Batiste Lecocq

 

 

Long time win

Code review

CI / CD

Bon sens !

Made with Slides.com