Ir al contenido principal

Pair Programming

Pair Programming

It results outstanding to me that the idea of having a pair or a group of programmers working on the same computer is relatively new to the programming world, the phrase of "two heads are better than one" has been existing from a long time ago prior to computation and it is has been proven to work (also it is quite logical), so why pair programming hasn't shine as it's supposed to be?

The only thing that disturbs pair programming is the human factor, humans change their mind but at the same time don't, if they have worked all their lives alone and the results have been good the change to a pair programming will be difficult, they'll think that they are superior than their comrade, the suggestions of the last one will be ignored mostly, no help will be asked, making the pair programming more of a hassle than a good programming method.

Other thing that involves the human factor is the interaction with others, maybe we can get along with someone but that someone is busy and we have to pair with the prick that we hate, nothing good comes from that and I know it from experience, a solid relationship must be made for pair programming to work, not necessary a human relationship but for work there must be, it can be easily accomplished by according that the failure from one will become the failure of both, although this sounds a little menacing and I think is better as a last resort statement, is better to first build a trust and to agree that they must act cooperatively so the work between the pair can be flawless and so that pair programming can shine appropriately.

Pair programming is like the basis for a good work, each one of the duo learns and teaches (without even knowing) even when the pair is the same most of the time, it is a process where everybody wins something, the programmers, the business and the users, each gets a benefit of a good work.

Comentarios

Entradas más populares de este blog

Rich Hickey on Clojure

Rich Hickey on Clojure Clojure and his ability to easily communicate with Java makes it the perfect contender for best language, being able to simply call Java code con Clojure code and looking that they work without trouble at start is something that is rarely seen but that when it does appear, is like when God decides to touch you with all his greatness. Programmers and enterprises have noticed this, that's why Clojure is one of the most well-paid languages on USA. Inheriting from LISP the investigation-oriented theme makes a language that cannot be managed by anyone but when mastered, it really shows its true potential, sadly this isn't enough for making LISP, Clojure or the functional programming in general a popular thing, although Clojure with its JVM implementation and macros seeks to fight the problems that stopped LISP from getting mainstream. Thanks to functions that Clojure has, it makes it way easier and direct to solve problems and to actually combine or to...

The Roots of Lisp

The Roots of Lisp Lisp as the main root of functional languages has a rather confusing way of working, it is as basic as it can be so to write a function without the need for it to be complex can quite confusing like the eval functions presented on the document. Is funny that on this paper I read about interpreters and on my SW Design and Architecture I also learn about interpreters. I have to thank that newer and improved versions of Lisp have emerged like Clojure that make simple to write functions that are interpreted into all this complex code that was explained just to do something relatively simple. Enough from complaining about, on the bright side, the benefits from having a simple and basic language is that it can be molded to whatever we want from the ground up (basically like how Clojure or any "upgraded" version of any language came to be) and that is why Lisp is still being so functional and useful even today. The simple notation that Lisp uses is what giv...