• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

The evils of versus

 
author
Posts: 608
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've noticed that several people have been posting "this vs. that" style questions. I suspect that this reflects a black & white mindset, something that I believe people need to abandon. The sixth philosophy of the AD method is "Sweet Spot" which basically says that it isn't a black and white world, for any issue, that instead you need to find the "sweet spot" somewhere in between that works best for you. That sweet spot will be different for different situations.
So, whenever you think to ask a "this vs. that" question perhaps you should step back and instead consider a "how does this and that work together" question. Somthing to think about.
- Scott
 
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

So, whenever you think to ask a "this vs. that" question perhaps you should step back and instead consider a "how does this and that work together" question. Somthing to think about.


I feel it difficult because most of the time we have to choose one of them of the various options .For example which process, app server to go for.
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

For example which process, app server to go for.

Regarding software products, yes, you often must choose one or the other (even though you would change your mind later on and revert your decision), but a software process you should be able to customize every time (it's cheaper than rewriting significant parts of an application server in order to "merge" in some features from the other application server...).
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Lasse Koskela:
a software process you should be able to customize every time


Yes. On the other hand it can be hard or even risky to customize a process before you actually understand how it works by having tried it "as written".
I agree in intent, though. We also have many questions of the form "which one is better" - those questions most often don't make any sense, especially as they are asked without any context.
 
Ranch Hand
Posts: 74
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Scott Ambler:
I've noticed that several people have been posting "this vs. that" style questions. I suspect that this reflects a black & white mindset, something that I believe people need to abandon.
...
- Scott


Well, like they say, there are 10 types of people in the world,
those who understand binary and those who don't.
 
Ranch Hand
Posts: 147
Android Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Scott,
I'm glad you brought this up. I think what makes AD so unique is that it is a different way of thinking, not just a different way of approaching software development....or using the latest buzzwords.
Lots of people do think in black vs. white...Microsoft vs. Sun...us vs. them. I guess that's why we have so much prejudice in the first place.
What I like about your writings is that you advocate seeing the other person's point of view. Users don't see business problems the same way developers do, and DBAs don't see things the same way that developers do.
So, you advocate DBAs learning a little about software development, and developers learning a bit about database admin. This seems to expand the agile idea of not owning code. If only operations people knew how software was developed and visa versa....what a concept.
Thanks,
Glen
 
Ranch Hand
Posts: 81
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I used "vs." in posting not for the intention of seeing things black and white. I just used this bec. it's shorter to use rather than using many words just to get the difference between the two I compare.
 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Scott Ambler:
I've noticed that several people have been posting "this vs. that" style questions. I suspect that this reflects a black & white mindset, something that I believe people need to abandon. The sixth philosophy of the AD method is "Sweet Spot" which basically says that it isn't a black and white world, for any issue, that instead you need to find the "sweet spot" somewhere in between that works best for you. That sweet spot will be different for different situations.
So, whenever you think to ask a "this vs. that" question perhaps you should step back and instead consider a "how does this and that work together" question. Somthing to think about.
- Scott

 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Glen Tanner:
So, you advocate DBAs learning a little about software development, and developers learning a bit about database admin. This seems to expand the agile idea of not owning code. If only operations people knew how software was developed and visa versa....what a concept.


Yes, it's a great concept, which seems to be quite contrary to some corporates culture...
It seems to be more of a variant of the fourth principle of Agile Software Development, though: "Business people and developers must work together daily throughout the project." (see http://agilemanifesto.org/principles.html )
As far as I know, Collective Codeownership is mainly a practice of XP, though it might be implied by the above ASD principle.
[ January 15, 2004: Message edited by: Ilja Preuss ]
 
Ranch Hand
Posts: 398
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I think what he means is not qeustions like WebLogoic vs WebSphere but ones like RUP vs Agile DB design. We can't have both of the servers but we can use best of both processes.

Vasu
 
Joy Jade
Ranch Hand
Posts: 81
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Vasu,
I think maybe this is what he means the most. The posting of :
Anushe Khan
ranch hand
Member # 62942
posted January 13, 2004 02:54 PM
--------------------------------------------------------------------------------
WELCOME!
Who Should Read This Book ?
Do we need some agile programming experience.
Could you please briefly describe agile model-driven development (AMDD).
TDD vs AMDD (which is better)
thanks in advance.
Anushe
SCJP,SCWCD
reply
    Bookmark Topic Watch Topic
  • New Topic