Irrational Software R.I.P.
I used to have a secondary weblog titled “Irrational Software,” where I reposted edited and often merged posts from this weblog. I liked doing that, but it eventually took over. So I quit.
As I moved Tesugen to Rails and TextDrive, I shut down Irrational Software and imported the posts here.
Here they are:
- Refactoring, design, architecture
- The Selfish Class
- Emergent design
- Writing tests for legacy code
- Introducing Extreme Programming
- The social life of paper
- Testing in layers
- About feedback
- The illusion of predictability in planning
- About roles
- Why should code be readable?
- Hard-coding stuff
- The need for a coach in XP
- Design in FDD and XP
- Response to The Case Against XP
- Intentional programming
- Extreme Programming Values
- More on Intentional Programming
- Lego Serious Play
- Metaphorical abstraction
- Multifaceted software
- Cooperative games of invention and communication
- Work should be play
- Understanding XP through FDD
- Storytelling and architecture
- A fresh look at patterns
- ””Real-world architecture vs software architecture
- Brooks’s definition of architecture
- Origins of software architecture study
- What’s code?
- Storyboards: a pragmatic tool for coordination
- Slime molds
- Pandemonium
- Programmer ants
- Emergent software projects: genome analogy
- Emergent open-source
- bin Laden networks
- Hierarchical versus networked projects
- Agile culture
- Pattern language, team culture
- On The Cathedral and the Bazaar
- Extreme Programming and culture
- Creative programming
- Re: Joel’s law of leaky abstractions
- Finding a metaphor in Extreme Programming
- To clarify, add detail
- Layering and separation
- The Disney process
- Creative writing and software development
- Creative writing and software development
- Creative writing and software development
- Mary & Tom Poppendieck: Lean Development
- Mary & Tom Poppendieck: Lean Development
- Network science and software