Episode 38: Interview James Noble

Topics covered
Popular Clips
Episode Highlights
Postmodernism Defined
In the realm of software development, postmodernism challenges traditional methodologies by embracing flexibility and diversity. explains that postmodern software development involves considering multiple small stories or perspectives when making decisions, akin to the agile approach. This method values the merits of each story, ensuring no single narrative dominates the decision-making process 1. Noble highlights how postmodernism in software is not about rigid structures but about adapting to the context and needs of the project 2.
Postmodern software practice simultaneously replaces the software engineering, modern software engineering that went before while simultaneously fulfilling it.
---
Language Choices
Programming languages play a crucial role in postmodern software development, with advocating for languages like Perl, which he describes as the first postmodern programming language. This perspective emphasizes the importance of embracing diverse concerns and avoiding a single dominant narrative in software design 3. Noble argues that decisions about programming languages should consider various factors, including team dynamics and the broader context of the project 4.
The idea there is that software needs to be made up of a whole lot of different concerns.
---
Agile Connections
Agile development practices share similarities with postmodern principles, as both prioritize adaptability and the consideration of multiple perspectives. notes that agile methodologies, like XP, align with postmodernism by valuing small stories and iterative decision-making processes 1. This approach contrasts with traditional methods that often impose a singular way of working. Noble emphasizes that postmodernism in software development encourages local decision-making and flexibility, allowing teams to tailor their processes to specific project needs 2.
Some parts of this approach seem to be taking a postmodern thing.
---
Related Episodes


Episode 36: Interview Guy Steele
Answers 383 questions

Episode 47: Interview Grady Booch
Answers 383 questions

Episode 96: Interview Krzysztof Czarnecki
Answers 383 questions

Episode 97: Interview Anders Hejlsberg
Answers 383 questions

Episode 79: Small Memory Software with Weir and Noble
Answers 383 questions

Episode 86: Interview Dave Thomas
Answers 383 questions

Episode 20: Interview Michael Stal
Answers 383 questions

Episode 112: Roles in Software Engineering II
Answers 383 questions

Episode 143: API Design with Jim des Rivieres
Answers 383 questions
Episode 172: Feature-Oriented Software Development with Sven Apel – Pt 1
Answers 383 questions

Episode 81: Interview Erich Gamma
Answers 383 questions

Episode 110: Roles in Software Engineering I
Answers 383 questions
Episode 173: Feature-Oriented Software Development with Sven Apel – Pt 2
Answers 383 questions

Episode 39: Interview Steve Vinoski
Answers 383 questions

Episode 150: Software Craftsmanship with Bob Martin
Answers 383 questions






