java training in chennai

1
Programming Java Pair to the rescue once again
2

• Some time ago I wrote how peer java programming
  can help maintain high quality code. But that is
  not all!
• Today I want to explain why I should practice
  torque programming to incorporate a new
  carpenter. This makes the entire process faster
  and more efficient.
• A new jeweler joins the team
• On most of the projects we were working on, we
  assumed that a new carpenter would have a
  negative impact on team productivity for
  approximately the first three months.

3

• That you have to help them settle down in their
  new job and help them establish everything. That
  you have to share all these little hacks in your
  projects and the configuration of your tools.
• There will be questions and they will wait for an
  answer for each and every one of them.
• They will bring ideas, suggestions, comments.
  There will be a lot of "why" during those days.
  And that's good! This confirms that letting them
  join the team was a good choice.
• But those are three months! Three long and
  exhausting months. For both parties the team and
  the new carpenter.

4

• Let's solve an error
• The idea is to give a new carpenter the
  opportunity to learn the application by
  investigating a succulent mistake. They will have
  the opportunity to see and learn everything, will
  not they?
• However, even if you truly believe it works,
  there are some problems with this approach.
•  Core Java training program, youll learn to
  design, write, compile, and run basic Java
  applications that incorporate fundamental
  programming concepts and accepted programming
  techniques.

5

• The new members do not understand the commercial
  domain or the technical aspects of the
  application. It's obvious, but compared to
  introducing a new feature, the lack of knowledge
  in this case makes things much more difficult.
  They will ask, of course, but the first steps are
  generally attempts to understand everything by
  themselves. The next steps take them to Google.
  And then, at the other extreme, there will be
  questions. So it will take a long time.
• You should also remember that in resolving an
  error there is the possibility of landing in some
  forgotten places.

6

• Passing through code
• "Just review the java code and ask any questions
  you want." You can start here, here and here.
  "I've said it a couple of times in the past, what
  was the effect?" Google hours and tons of
  questions. At first glance, you might even see it
  well, but the problem is that a new carpenter
  asks and learns things / modules / places that
  almost never touch.
• The purpose of incorporation is to change the new
  application to something comfortable to work
  with. Do not fill the new carpenter's head with
  as much detail as possible.

7

• Knowledge exchange / documentation sessions
• It's great if there is documentation for your
  application. It's great if you're organizing
  knowledge exchange sessions. But this can only
  work as an accomplishment for other activities in
  the core java programming, not as a substitution.
• Even if you provide a detailed session and have
  rich, up-to-date documentation, it is impossible
  to remember everything. Even if someone is eager
  to learn, there is little chance that they will
  remember more than a small percentage.

8

• Torque programming for the rescue
• For some time, I thought letting a new carpenter
  get to work on our current products is the best
  option programmimng. However, the interruptions
  remained the problem. Questions are a constant
  during the merger and can not be eliminated. What
  can you do instead? You can eliminate the
  negative impact they bring if you have to
  interrupt other people's work to ask. If you pair
  then you completely eliminate these interrupts!