Codeshare and Pairprogramming

Have you ever had this peice of code that compiled but just didn’t work properly? Situations like this can be exhausting and take for hours! Yesterday i had a situation like this while writing some code for my Virtual StockExchange project. I am the kind of programmer who likes strongly typed programming languages but i enjoy the benefits of the weakly typed too much to let’em go. In particular I use  Javascript and JQuery to add that spice which transforms a white canvas to living art. Only problem is that all these languages give you is a white canvas if they do not work! This usually leaves me with 2 options

  • Spend hours searching for that missing semicolon
  • Send a codesnippet to a friend using jsfiddle.net

The first option is a great learning experience, but sometimes you just need to get some work done and is therefore not an option. Next step is therefore to send the lines of code you think might be the problem to a friend/co-worker etc. But we all know this usually won’t work since we might have sent the wrong piece of code in the first place and it’s hard to work through others complex code when all you recieve is a snippet.

Codesharing with Codeshare.io

What if  you could share your entire code in a great format and then invite your friend/co-worker to join the bug-search? Say hi! to Codeshare.io. All you have to do is press “New Codeshare”, and you can copy/paste your code to the browser even without signing up. Then you simply send the generated link to person that will assist you and you’re all set. The team behind Codeshare even added a videochat function via WebRTC.  Now this is all you need to share your code and start the codesharing. See this example codeshare of some of my code from my Virtual StockExchange project.

Pairprogramming

Pairprogramming is softwareconstruction practice where every workstation is used by two programmers in stead of one. This has many positive effects on the development process.

  1. Two points of view
  2. Simple mistaskes is avoided
  3. Combining knowledge
  4. Learning platform

This is just some of them but in general two are better than one. Two sets of eyes will catch many of the simple mistakes and the solutions found by two will be usually be much better. By putting two developers on the same workstation will also make them share knowledge between them and they are force to discuss solutions before taking action. The outcome of this is a better product and the idea is that time is saved since the fewer mistakes and better solution require less testing and bugfixing effort at the end of the project. It is a fact that a defect found after release cost as much as 5-10 times more than a bug found in the development process. See this infographic TypeMock made.

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>