software

Thoughts And Articles On Pricing | Software Indie Nice roundup of articles of software pricing.

Camels and Rubber Duckies – Joel on Software The answer is really complicated. I’m going to start with a little economic theory, then I’m going to tear the theory to bits, and when I’m finished, you’ll know a lot more about pricing and you still won’t know how much to charge for your software, but that’s just the nature of pricing.

via The Clean Architecture | 8th Light by “Uncle” Bob Martin The outer circles are mechanisms. The inner circles are policies. The overriding rule that makes this architecture work is The Dependency Rule . This rule says that source code dependencies can only point inwards . Entities Use Cases Adapters (Controllers, Gateways, Presenters) Frameworks Only Four Circles? No, the circles are schematic. You may find that you need more than just these four....

The MVC and 3-Tier architectures combined (via The Future of Web Development « mvalente.eu/mv.* )

Interactive Application Architecture Patterns The Model-View-Controller , Model-View-Presenter , and Presentation-Abstraction-Control patterns are similar in many ways, but have each evolved to address slightly different concerns. This article discusses each pattern along with its history and design motivations to encourage the correct understanding and application of these patterns.

Keynote: Architecture the Lost Years by Robert Martin @ Ruby Midwest 2011 (also on YouTube … and a few weeks later, without slides , on The “A” word. A Discussion About Architecture in a Software Craftsmanship conference ) Images clipped together from… The “Presenter” and “View Model” at 35:28 “The whole Enchilada!” at 37:50 “The Database is a Detail!” at 42:26 Elements summary: Entities — Generic application agnostic data and business rules (e....

A good architecture allows major decisions to be deferred! Robert Cecil Martin Or putting it in another way… A good architecture maximizes the number of decisions NOT made.

Yours, Mine and Ours I claim here that there are three categories of software: MeWare : The developer creates software. The developer uses it. Nobody else does. ThemWare : The developer creates software. Other people use it. The developer does not. UsWare : The developer creates software. Other people use it. The developer uses it too. For completeness, I suppose I should probably mention the obvious fourth category: NobodyWare : The developer creates software....

The software is wrong, not the people. Matt Mullenweg (vai Joe Flood )

Shut up and ship! Jeremy Zawodny in Shut Up and Ship!