|
I have considered what it is that XP and Scrum do that is fundamentally different, and I believe that it is essentially that the developers are enforced to be social instead of doing individual development. Social with each other, social with the customers, etc etc etc. This allows knowledge to be distributed more than when you have a single key developer with everything in his head.
Thanks Thorbjørn! I already found http://www.rpgunit.org/ which is sort of like JUnit, but more for RPG. I have been spending a lot of time on various XP and Scrum mailing lists so I'm familiar with TDD.
I don't know if a discussion of TDD with RPG is on topic for this list exactly, but I will say that TDD has much more merit in greenfield (brand new) development. When one has a monolithic application of the 'load, sort, print' paradigm, it is very difficult to isolate code to do TDD because one database input record will fire many separate pieces of the monolith.
Perhaps if WDSC had a refactoring tool that could operate on RPG, we might see more TDD in the RPG community. SOmething to think about working on in my not so copious spare time :-)The reason why Eclipse does so well with refactoring (haven't tried IntelliJ but it should be better) is that the frameworks UNDERSTANDS that you write in Java instead of just working with plain text files. This requires a built-in compiler which can provide information to the IDE so that it knows where i.e. a variable definition starts and ends.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.