From: Quentin Crain Date: 2002-01-03T13:19:55+09:00 Subject: [ruby-talk:30107] Re: Ruby/Python: Software Engineering Matz/All: Embedded: At 11:17 AM 1/3/2002 +0900, Yukihiro Matsumoto wrote: >Hi, > >In message "[ruby-talk:30073] Re: Ruby/Python: Software Engineering" > on 02/01/03, noone writes: > >|> I feel like methodologies belongs diffrent level of abstraction. >|> Languages (and their features) are tools, and software engineering and >|> methodologies are how to use tools. >|> >| >|When this is said, I hear that a separation exists ("different level >|of abstraction"). > >I guess it's easy for you to distinguish a "kitchen knife" and "how to >use a kitchen knife". The former is a concrete tool, the latter is >abstract "how-to". And would changing the design of the knife change the "how-to"? And does the "how-to" suggest one design of the knife over another? >|To what degree are they separate? Are languages interchangable without >|affecting how I do my work (the process)? > >Some methodologies are targeted toward specific tools, so that you >have to modify / customize them to adopt different tools. In that >sense, they are NOT "interchangable without affecting how you work". >But I guess methodologies still remain same methodologies after >customize, for example XP is XP even using C++. Agreed. And given the need to customize the methodology (XP) for the tool (C++), might there be other tools (Ruby) which works "better" (less customization, closer adherence to philosophy) with the/a methodology (XP)? > matz. thanks!! <