The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
In 1637, René Descartes published his "Discourse on the Method of Guiding One's Reason and Searching for Truth in Sciences." In this work, Descartes described four rules he followed to make sure he always came to true conclusions.
1. Doubt everything.
2. Break every problem down into smaller parts.
3. Solve the simplest problems first, and build from there.
4. Be thorough.
Let's face it: Agile, Scrum, Pair-Programming, Kaizen, TDD, etc., have made little difference in programming team productivity, reduction of errors, achievement of development milestones, and the ultimate goals: reliable software that can be maintained efficiently, and extended (or ported) without draconian costly re-design and re-development.
Arguably, such techniques ... all forms of intentional modifications of interpersonal interaction ... have led to increased rates of work-place violence, increased rates of employee absences due to physical and mental illnesses, and obsessive-compulsive forms of group behavior similar to those exhibited in cults whose members have been "brain-washed."
While mechano-structuralists argue that the central problem is that people (dammit) have "personalities," and the semiotic-culturalists view the problem of work-group team co-ordination as a matter of the tension between an innate drive for symbiotic emotional and intellectual union, and competing drives in intra-psychic individual construction of reality: the fact remains that software development is a bloody mess.
Note that we choose to ignore in this discussion the "ornamentalists" whose belief is that some arrangement of visual elements, and the use color, sound, motion, animation, etc., is the primus inter pares which transcends the collective aspects of software development, and that it is simply a matter of working backwards from visual design to code.
Now, I must ask you, dear reader: where on our melting-ice-caps' planet can we find a new ... a revolutionary ... not just evolutionary ... way to make software development efficient, wholesome, pleasant, facilitative of individual development of potential, and group harmony ?
I believe your mind(s) (at least O'Hanlon's, OriginalGriff's, and other CP savants') have already quantum-leaped to the conclusion of which this aged vessel, so far past its fifteen-minutes of deservedly obscure fame that it could be in the Oordt Cloud, who writes this now, is only, by chance, a sorry mouth-piece:
Yes, this new method, which I've given the temporary working-name of "JUICE," already exists in the collective minds of CodeProject's (soon to be ten million) members !
Well, yes, "JUICE" is an acronym ... "Just Unbelievably Incredible Collective Enlightenment" ... but: so what ? Let us not be distracted by such linguini at a time when the reality itself is not yet al dente.
I can see you are jumping up-and-down, now, a la Ballmer; you may wish to pause for a moment, close your eyes, take a deep breath.
Because, yes, you will soon (if not now) be asking me the same question I am asking you now: if it already exists, where is it ? If it is "among us:" in what form is it present ? And, so on.
But, to quote Milton's great heartfelt sense of cosmic soothing, after his timeless cri de coeur of the agony of his oncoming blindness in his immortal sonnet: "that murmur soon replies:"
And, the murmur, as I hear it, the calming susurrus of listening to an empty sea-shell, says:
All we need to do is simply articulate it, to infer its form from the shadows we see now (if through a glass darkly, cast on the walls of the cave by a light whose source seems omnipresent).
All CP need do is to start a Forum named "Juice," and, just as 700-pound stones can move by themselves in California's Death Valley [^]: JUICE will manifest.
And now, like an emerging imago seeing the cracked chitinous remains of the pupa it leaves behind: you need not another word from me.
“Human beings do not live in the objective world alone, nor alone in the world of social activity as ordinarily understood, but are very much at the mercy of the particular language which has become the medium of expression for their society. It is quite an illusion to imagine that one adjusts to reality essentially without the use of language and that language is merely an incidental means of solving specific problems of communication or reflection." Edward Sapir, 1929
The logo shall borrow from the CP hue, so we shall have Orange JUICE. For the iAfficianado, we can have Apple JUICE and the hobbyist may choose Raspberry JUICE. I feel that the opportunities are endless.
I was brought up to respect my elders. I don't respect many people nowadays.
A worthy goal indeed! And certainly merits a collaborative CP attempt.
I’ve known many fine developers and programmers who have made me feel that I am but a hack in the wrong profession. I’ve also see these same fine people spend hours debating tabs vs. spaces, white space, same line/new line curly braces and how to use revision/version numbers.
We are people after all, as you pointed out. If we can agree on the essence of the methods and not so much the implementation or style, we may have something.
My dear sir, I have been using JUICE programming for some considerable time now.
By preference, I choose the JUICE of the Juniper berry, well preserved in alcohol. I oftentimes add a little extra JUICE obtained from the bark of the Cinchona tree, together with what little JUICE can be obtained from a a single slice from the fruit of the C.Limon tree.
I must confess, however, that although, at the time, JUICE programming appears to be highly effective, a review the following day indicates that the chosen methodology may be less than optimal.