It is fairly common that you might be contributing to multiple git repositories which make different git configuration necessary. Mine and probably the most common case is that I am using different contributor email addresses for my private and work git repositories. You might also want to have separate global git ignores or other options that differ in multiple repositories. The way I do it is having one ~/.gitconfig which looks like this: ...
The Three Flaws in Software Design & How to Avoid Them http://www.youtube.com/playlist?list=PLOU2XLYxmsIJ7HGm2bv20QrtwcWemSRCI Github: Updated Services UI https://github.com/blog/1827-updated-services-ui Atlassian: Now in JIRA Agile Labs: an all new control chart http://blogs.atlassian.com/2014/04/now-jira-agile-labs-new-control-chart/ Atlassian: 6 key ways to optimize development with a control chart http://blogs.atlassian.com/2014/04/6-key-ways-optimize-development-control-chart/ How Disqus Went Realtime with 165K Messages Per Second and Less than .2 Seconds Latency http://highscalability.com/blog/2014/4/28/how-disqus-went-realtime-with-165k-messages-per-second-and-l.html 3 ways to do eager loading (preloading) in Rails 3 & 4 http://blog.arkency.com/2013/12/rails4-preloading/ Drowning in problems: http://game.notch.net/drowning/ There were also some rants about TDD, which I am not going to bother to list
Today I gave a talk at WeLovePHP, which is a quarterly talk and workshop series organized by Softonic in Barcelona. They also do one about JavaScript. I can highly recommend them if you are interested in PHP, JavaScript or related topics. I talked about the processes and tools we are using at Splendia. There are no pictures in the slides … sorry.
As hopefully most people working on software projects nowadays we are writing unit tests and do code reviews. Work-flow at Splendia As our project is a large PHP site we are using PHPUnit for unit testing and various static code checking tools (checkstyle, phpmd, pdepend, phpcpd) to verify the quality of our code. All of these are run on our integration branch, whenever a new feature is integrated. Before this can happen the code will be reviewed by other people in the team and only if there is a consensus it will be merged into the integration branch. ...