I know it is hard for someone without experience to come to a good case scenario on programming but it actually does relate to real life situations here but let's explore a view possibility and hopefully you will find a better story on what was listed.
---------------------------------------------------------------------------------------------------------------
1. Extreme Programming: Simply it is like pair programming, where one is the coder and one tells the other what to program. It is much better than hacks and the quality of the work actually improves overtime.
One of my over exaggerated examples is: a solo coder working with a network of programming experts, factoring out on the amount of knowledge that you know about a particular system.
This includes random bugs finding where occurrences is non logical and requires an intuition of a non-technical expert to resolve the problem, url of a HTTP connection becomes a HTTPS without the references of such connection ever could be established from a simple REST server; or in different case scenario, a sudden speed up of Android emulator thanks to a quick automated updated which it didn't do so in the beginning after so many tries.
I know my ones are a special kind of extreme programming. It does suggest sometimes this works and makes my life better and work quicker and at other times it doesn't work and make me can't work out a simple test examination scenario that was used in a job interview.
Let's jump out of this box and think of a relation as a Turing test where it does helps you and destroys you as well.
Know this wisely.
2. API reading: This is invented also as a good guy in disguised. I seen poorly written API and what I found doing is how to find out on using them. It makes me think that I am actually pasting code every time that there is a solution.
If you know what it means, then I would ask why don't they make a API for every solution that there is?
This asks you should to learn how to test functionality of a particular method, generally good coder use a different set of methods than the ones that commonly used and because from API reading, it actually has methods that does the same thing in a different way.
3. Quick full references: I tried one time using a Selenium tutorial in jumping out a lot of words to reference a limited part of coding. Don't type the code until you realise what it does to the command prompt.
What I did was jumping back and forth until I worked out what the whole program does without a single input in place. If you made the wrong move and setup the server wrong, it won't behave correctly if you try to re-code it into another way.
This is a one way street, not bidirectional.
I managed to setup using just one server running for selenium (I think it was called Complex Cube or something) rather than using two servers running on the same computer (which it sounds strange).
Just don't believe on what it says until you understand all the technology running behind it.
You never know what fools you until you know what it is.
----------------------------------------------------------------------------------------------------------------
These are just better explanations on the strange things that happens with programming.
I think it is best describe as something like "semi-logical meanings" of "perfect sequence of coherent coding" brings to what it really means in reality.
So now you know of what "Happy coding!!" we hear so much actually is.
