Get Started for FREE
Sign up with Facebook Sign up with X
I don't have a Facebook or a X account
 Your new post is loading...
Your new post is loading...
Scoop.it!
Programmer en binôme c’est se retrouver assis devant un écran d’ordinateur à deux et passer la journée à résoudre en tandem des problèmes en lien avec des projets informatiques. La pratique divise dans l’univers du développement de logiciels. Certains managers sont d’avis que leurs entreprises ont à gagner du partage de connaissances entre développeurs en duo. D’autres leur opposent le fait que l’approche implique un gaspillage de ressources humaines. La liste des points de contradiction es 
No comment yet.
Sign up to comment
Scoop.it!
Leading real-time platform for conducting live developer interviews with video, code editing and execution, and screensharing, with an audience of over a million developers already on EXLskills
Scoop.it!
Whether you work on a distributed team or just have the occasional problem-solving session with a friend, you'll find a remote pair programming tool here.
Scoop.it!
(Previously called PairProgramming is like sex) I created this presentation to explain to IT students what is PairProgramming. The second part of my talk they …
Scoop.it!
From
github
A mob/pair programming timer, inspired by the MobProgramming/MobTimer.Python. Runs great on Mac, Windows, and Linux. Learn all about mobbing at the MobTimer.Python github page, and at mobprogramming.org. Mobster was built with delight in Elm and Electron RPG ModeYou can play through the mob programming RPG to practice mobbing skills with your team. This is a port of Willem Larsen's excellent Mob Programming RPG. This is a fantastic way to learn about some of the subtleties that are essential to effective mobbing, such as the Driver/Navigator Pattern (also known as Strong-Style).
Scoop.it!
In February 2016, I celebrated my 4th anniversary developing using full-time pair-programming. By full-time I mean that when I arrive in the morning at work I …
Scoop.it!
Pair programming offers an extensive list of benefits. While it still remains a controversial practice, many teams have adopted pair programming
Scoop.it!
From
dzone
A developer explains the benefits that pair programming can have in an Agile environment, and some pitfalls to look out for when doing pair programming.
Scoop.it!
From
medium
Whoever gave Mob Programming its name clearly wasn’t in marketing. Who would want to be in a mob?
Mickael Ruau's insight:
So what exactly is mob programming? Put simply: 3 (or more) developers, one keyboard. No, that’s not something weird that you’ve seen on the internet. It’s about working collaboratively towards delivering high quality software. Given that most programmers get in hot sweats just thinking about the idea of working with other people, I’ll delve into more detail as to what that looks like. Imagine we have a developer, Steve. Steve works on an app where users can view recipes. One day Steve is tasked with adding a ‘favourite’ feature to the app. With this feature users are able to save recipes to a a private list called ‘my favorites’. If they want to view a saved recipe again, they can simply open the favorite list and select the recipe. Steve wants to use mob programming to implement his feature, so he books a meeting room and asks his colleagues John and Sarah to join him in a mob. John and Sarah show up to the meeting laptops in hand, ready to take on the challenge of the favorites feature. So at this point, Steve needs to lay down some rules (yes mobs have rules). The rules might be something like this:
And that’s it — you now know about mob programming. Add it to your CV.
Scoop.it!
Cross-Programming : Forging the future of programming talk at Conférence Agile France
|
Scoop.it!
How to choose the right branching strategy for your project
Mickael Ruau's insight:
Choosing the right branching model can save you a lot of time in development. It also helps your dev team to work efficiently. Coming to the point, we are gonna discuss two branching models today
Branch based developmentThis is a very common strategy and most of them know it. You have a stable branch like a master. Then you have a feature branch like develop. So whenever you develop new features or fix any bugs, you take a branch from develop and finish your work. Then you raise a PR to the feature branch. After the code review, the branch will be merged. When you have finalized the changes, then you merge the feature branch to master for the main release. I know how common it is. Most of the open-source software use this method.
Trunk based developmentOn the other side, trunk based development doesn’t use branches or has very limited use of branches. You have the main branch like master Every developer will do all the changes in the main branch and push it directly to the main branch. There are no PRs, branches, merge conflicts. Just push directly to the main branch.
Seems very dangerous right? With trunk-based development, you mostly can’t control who pushes the code and which code is being merged to the stable branch. But there are things we have to consider with Trunk based development. Trunk based development is useful when you want to deliver software in a fast phase. And this method is always accompanied by best practices in writing software like TDD, CI/CD integration, Automation testing, high code coverage, pair programming, etc. Trunk based development is a required practice of Continuous Integration (CI). With CI you get a deployment pipeline where you can run all tests and other integration jobs and safely deploy the code to production. Most companies who are practicing CI often welcome Trunk based strategy. Trunk based development is often practiced in a group of professional engineers. Because they have experience in writing software and know the best practices often. This comes with a high advantage. Imagine a small group of professional engineers (maybe 10) who know best practices in development like TDD, Automation testing, etc, and are following Trunk based development. This group can deliver software in a fast and efficient way to its full potential. This type of development is highly encouraged in Agile methodologies where you have to ship software frequently to get feedback often.
Scoop.it!
Built from scratch, based on 20 years of experience developing IDEs. Fleet uses the IntelliJ code-processing engine, with a distributed IDE architecture and a reimagined UI.
Mickael Ruau's insight:
Distributed for flexibility
Scoop.it!
À l’instar des autres pratiques de développement, la revue de code ou le mob programming ne peuvent pas se mettre en place indépendamment de considérations sur la culture de l’entreprise qui souhaite encourager ces pratiques. Certaines cultures d’entreprise favorisent activement la formation d’équipes en cohésion (principalement en ne plaçant pas d’obstacles à leur formation). Dans d’autres cultures, la notion même d’équipe est dénuée de signification réelle. De la même manière qu’aucune pratique de développement ne saurait être « copiée/collée » d’une entreprise à l’autre sans considération du contexte, il est apparent que toutes les entreprises ne sont pas égales devant le défi que constitue le développement d’un logiciel de qualité. La présence ou non des revues de code dans leur corpus de pratiques est à mon sens une preuve de cette inégalité.
Scoop.it!
Travailler en Pair Programming permet d'améliorer la qualité d'un logiciel et la collaboration des membres d'une équipe, mais cela peut être compliqué à mettre en place. Quelles sont les raisons qui rendent cela difficile et comment déterminer les bonnes pratiques de Pair Programming pour votre équipe.
Mickael Ruau's insight:
Marcos explique un exercice de rétrospective appelé "Cette personne et cette personne" pour conclure sur une liste de bonnes pratiques de Pair Programming. C'est à l'origine une activité de rétrospective postée par Paulo Caroli, coach Agile chez ThoughtWorks et Taina TC Caetano, développeur consultant chez ThoughtWorks. Divisez un mur en deux sections, "Ne soyez pas cette personne" et "Cette personne déchire !" : dans la première, les membres de l'équipe écrivent un exemple de comportement qu'ils n'ont pas aimé, dans la seconde des exemples de ce qu'ils ont vraiment aimé. Laissez ensuite l'équipe discuter de chaque exemple. La conversation devrait tourner autour du ressenti de l'équipe concernant certains comportements, les membres sont-ils d'accord que c'est une bonne chose à faire ? Dans certains cas, le comportement peut être apparent. Mais dans d'autres cas, cela peut mériter plus amples discussions. Je vois cette activité comme une bonne façon de booster le moral de l'équipe. Avoir cette conversation mène généralement les gens vers une plus grande ouverture vers les autres, ce qui mène à plus de conversations. Une bonne manière de prendre la température d'une équipe est d'observer à quel point les membres communiquent. Une équipe silencieuse est souvent synonyme de déconnexion et d'un manque de partage d'informations.
Scoop.it!
In a way, pair programming is like riding a bicycle. You could read a book about it, you could watch videos of other people doing it, but you can only really learn it by doing it.
Scoop.it!
Visual Studio Code's Live Share extension brings remote collaboration to the IDE and its huge user base.
Scoop.it!
Ne pas avoir son propre ordinateur mais partager le même ordinateur avec son binôme : voilà ce qui explique le pair-programming à temps complet.
Scoop.it!
From
xebia
Without exception in all teams I’ve developed software in people have expressed their aversion against pair programming. It’s not that developers don’t want to try, or that they don’t believe it will help. On the contrary, they are usually very enthusiastic about trying it and give it more than a fair chance. After a few days they sit alone behind their keyboard coding like zombies with headphones. What’s going on? Is pair programming too hard? Doesn’t it pay off? In this post I’ll try to explain what I think is happening, and I will give you some clear pointers to avoid the traps. At the end I will go into distributed teams and what part of the game changes there.
Scoop.it!
From
dzone
If you have never tried Pair Programming, try it. Give it a couple of weeks before assuming that you know enough to say it doesn’t work for you.
Scoop.it!
From
dzone
When I encounter a team that’s reluctant to try pairing, sometimes I’ll suggest another technique that I call buddy programming.
Scoop.it!
Limitations et extensions des méthodes agiles - WikipédiaLes méthodes agiles sont des groupes de pratiques pouvant s'appliquer à divers types de projets, mais se limitant plutôt actuellement aux projets de développement en informatique ( conception de logiciel). Les méthodes agiles ne sont pas apparues avec le Manifeste agile en 2001 mais celui-ci détermine leur dénominateur commun (consacre le terme d'" agile " pour les référencer).
Mickael Ruau's insight:
Sommaire
|
