"… In this episode of the Stack Overflow podcast, Joel and Jeff discuss GitHub, the value of formal code documentation, and how to decide what features belong in the next version of your software." http://itc.conversationsnetwork.org/shows/detail4376.html
Also huffduffed as…
After realizing that no overriding methodology existed for the development of open source software, Robert Lefkowitz set about trying to develop one. After looking at various models for general software development, he found that they had similar stages of creation and implementation. And he found that these stages dovetailed nicely with Quintilian’s Institutes of Oratory, a model for persuasive argument.
Using Quintilian’s steps, Lefkowitz discusses how he developed a working model for open source software development that would take into consideration issues specific to it, such as the role of community (trying to get everyone in IT to agree to the steps and to keep them posted on their cubicles), and the need to design programs that can handle exceptions (because there is no development, only maintenance.)
In this way, companies can create exceptional software and embrace a process where errors are not a bad thing.
In this Episode we are happy to talk to Grady Booch. We started off by discussing his Architecture Handbook, how it came into being, the progress, and how it will look like once it’s finished. In this context we also looked at the issue of how to distinguish architecture from design. We then asked him about how "professional" software architecture is these days, as well as about the ubiquity of software product lines in industry. The next couple of minutes looked at the question of whether software development is an engineering discipline, craftsmanship or an art form, and we discussed the key qualifications of software developers. Grady then elaborated on the problems of developing in large teams as well as the potential limits of complexity we can tackle with software.
We then got back to a more technical discussion, where we looked at model-driven development, DSLs, etc. and the role of the UML in that context. Next was a discussion about scripting languages, and the current trend towards new languages. We then looked at component marketplaces and other forms of reuse, as well as the importance of OO these days and the relevance of AO. We concluded with a (small) outlook to the future.
When is an application or design actually done? Dan Benjamin talks with Cameron Moll, Faruk Ates, and Garrett Dimon about design and the software development process, and how it differs when it’s your project vs. client work. We also discuss the way that new devices like the iPad are changing the way we code and design, and more.