VirtualTam's bookmarks
-
2024-02-17 -
2019-03-15 -
2018-11-27 -
2018-02-23 Guides:
- https://tuple.app/pair-programming-guide/
- https://www.codefellows.org/blog/peer-programming-5-reasons-learning-in-a-group-beats-studying-on-your-own/
- https://dzone.com/articles/what-is-pair-programming-advantages-challenges-tut
- https://blog.jayway.com/2017/02/10/efficiency-of-pair-programming/
- https://www.cs.utexas.edu/users/mckinley/305j/pair-hcs-2006.pdf
- http://www.jucs.org/jucs_15_16/understanding_tools_and_practices/jucs_15_16_3101_3125_schuemmer.pdf
- https://www.slideshare.net/uhpnou/pair-programming-a-pratical-guide
- https://www.slideshare.net/istepaniuk/effective-pair-programming/9-Strengthening_the_case_forPair_ProgrammingL
- http://kata-log.rocks/pair-programming
Approaches:
- http://blog.xebia.com/practical-styles-of-pair-programming/
- https://www.quora.com/What-is-your-review-of-Pair-Programming
- https://www.quora.com/Is-there-a-good-development-environment-for-remote-pair-programming
- https://www.quora.com/Why-do-programmers-use-paired-programming-What-do-remote-teams-use-for-paired-programming
- https://www.quora.com/What-are-some-techniques-for-effective-pair-programming
- https://www.quora.com/When-pair-programming-what-makes-it-a-bad-experience-and-what-makes-it-a-good-experience
Tools:
-
2018-02-23 - https://git.github.io/rev_news/2018/02/21/edition-36/
- https://twitter.com/cdibona/status/957822400518696960
- https://sfconservancy.org/blog/2018/jan/30/shawn-pearce/
- https://gitenterprise.me/2018/01/30/shawn-pearce-a-true-leader/
- https://groups.google.com/forum/#!topic/repo-discuss/B4P7G1YirdM/discussion
- https://linuxfr.org/news/la-communaute-git-en-deuil-de-shawn-pearce
-
2016-11-21 -
2016-01-02 -
2015-06-12 - Why Jenkins don't love me? http://m.memegen.com/oqruus.jpg
- Much stable. Success. https://raw.githubusercontent.com/ahmednuaman/meme-says-jenkins/master/assets/img/build-blue.jpg
- A code review fail http://m.memegen.com/oojxsc.jpg
- No idea https://regmedia.co.uk/2015/01/28/dog_meme_.jpg
- We will invade http://www.mememaker.net/static/images/memes/3675436.jpg
- Your own code http://devopsreactions.tumblr.com/post/120682285491/reading-your-own-code
- I have done my code reviews http://cdn.meme.am/instances/500x/58587913.jpg
- Too complex? https://i.imgur.com/nXrYiub.jpg
- Ship it https://qph.ec.quoracdn.net/main-qimg-d656a4e5537062cd665afe7c9ff46c53
-
Original script @ https://gist.github.com/yuvipanda/5174162
-
- https://en.wikipedia.org/wiki/SHA-1
- http://stackoverflow.com/questions/1867191/probability-of-sha1-collisions
- http://en.wikipedia.org/wiki/Birthday_problem
Some thoughts we had while toying with Gerrit, which artificially tracks different commits to group them as "patch sets", by using a Change-Id SHA-1 in the commit message:
-
2014-12-02 -
2014-04-26 -
2014-04-10 Someday, all software will be built this way.