Win a copy of Programming with Types this week in the Angular and TypeScript forum
or The Design of Web APIs in the Web Services forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Knute Snortum
  • Henry Wong
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Frits Walraven
  • Joe Ess
  • salvin francis

extreme programming

 
Ranch Hand
Posts: 72
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
is the extreme programming created because the software product is so easy to have bugs? so they suggest there should be two person programming together?
 
Leverager of our synergies
Posts: 10065
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
So there would be twice as many bugs?
 
Ranch Hand
Posts: 664
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, but the minimum requirement is that both programmers should be of opposite sex or beating around the same...er...bush
Shura
 
Mapraputa Is
Leverager of our synergies
Posts: 10065
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Another definition I read was that in pair programming one person is actually writing code, while another is thinking about code
 
Rancher
Posts: 13459
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Are you allowed to think about the code as you write it, or do you have to swap seats first?
 
Ranch Hand
Posts: 1865
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've been ignoring the concept of Extreme Programming until today when I read a review for a book on the subject. I was surprised to find that Extreme Programming seems to be very similar to a software development process that I used while managing a software group at a semiconductor equipment company. After working there for several years as a programmer I understood that the practice of having new hires work alone simply was not productive. They usually required a couple years to come up to speed on our product. Since the turnover rate for engineers was closer to eighteen months it was clear that working alone wasn't a good idea. When I was offered the opportunity to setup a new software department in the service organization I hired an equal number of entry level software engineers out of school and machine hardware experts from the manufacturing and service organizations. The idea was to have the hardware people learn C language programming from the software engineers and have the software engineers learn the operation of the machine from the hardware experts. Very quickly the two man teams proved to be amazingly productive.
Prior to the creation of my department, the company shipped a new version of software every 18 months. Since a software bug in the semiconductor industry can easily cost the customer tens of thousands of dollars each day, the 18 month cycle time was devastating. Even worse, new features intended for customer A often created problems for customer B. We found that an improved process was to immediately ship new features and bug fixes directly to the customer that requested the modification. The result was customers that got their modifications at the earliest possible date and the other customers got fully tested code at a later point in time when they decided to upgrade. The incremental code releases occurred as needed and averaged about once every two weeks. Each new version of code was built on top of the previous so integration occurred continuously. The release process for a major code release was nothing more than an exercise in paper work that simply glorified a previous incremental release.
The engineers in my department all worked very closely with the customers and our applications engineers and field service engineers to improve quality on a daily basis.
I left that company two years ago. It's funny that it has taken a couple years to learn that our process now has a name.
 
Ranch Hand
Posts: 45
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
 
This will take every ounce of my mental strength! All for a tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!