﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Marcel Popescu commented on Zones of Quality</title><description>I'm with RG... my customer / boss has a fixation with good design (which I don't do anyway, someone else is responsible for that). Nothing matters in the application until he likes the design. It's annoying.
</description><link>http://ayende.com/3674/zones-of-quality#comment6</link><guid>http://ayende.com/3674/zones-of-quality#comment6</guid><pubDate>Mon, 01 Dec 2008 14:14:24 GMT</pubDate></item><item><title>Bahador commented on Zones of Quality</title><description>Ommm... I'm not sure... the problem is in many shops it is really hard to justify going back to a working "quick &amp; dirty" code, and replace it with "production ready" code.
  
Sometimes the developers won't do it, if they want to do it, the PM won't let them, and if they want, the "business guys" won't like it and they will demand more new features.
  
  
Bottom line: I think it works in special scenarios that you have the necessary discipline AND authority to do this
</description><link>http://ayende.com/3674/zones-of-quality#comment5</link><guid>http://ayende.com/3674/zones-of-quality#comment5</guid><pubDate>Sat, 08 Nov 2008 09:29:21 GMT</pubDate></item><item><title>RG commented on Zones of Quality</title><description>Ayende, I think it might work as you say, but not in every situation. For most 'businesses' i know the only thing that has value is what they see, I mean the user interface. And no matter what is the system architecture, end users don't see any value in its internals, don't understand it and concentrate only on what's visible for them. If I were leading the project in this 'Onion' methodology, almost every customer would have thrown it away after seeing frist GUI prototype, or at least they would be very disappointed.
  
This remark applies also to some managers. 
  
</description><link>http://ayende.com/3674/zones-of-quality#comment4</link><guid>http://ayende.com/3674/zones-of-quality#comment4</guid><pubDate>Thu, 06 Nov 2008 09:21:18 GMT</pubDate></item><item><title>Chad Myers commented on Zones of Quality</title><description>@Ayende: I was joking, man. :)
  
  
Good post, though.
</description><link>http://ayende.com/3674/zones-of-quality#comment3</link><guid>http://ayende.com/3674/zones-of-quality#comment3</guid><pubDate>Thu, 06 Nov 2008 00:37:44 GMT</pubDate></item><item><title>Ayende Rahien commented on Zones of Quality</title><description>No, because the focus is different.
  
The most important part of my current application is reports, for example.
  
Domain model looks like hell, and the logic is disgusting. But the reports model is very well crafted.
</description><link>http://ayende.com/3674/zones-of-quality#comment2</link><guid>http://ayende.com/3674/zones-of-quality#comment2</guid><pubDate>Wed, 05 Nov 2008 23:49:54 GMT</pubDate></item><item><title>Chad Myers commented on Zones of Quality</title><description>Is this kinda like the Onion Architecture? :)
</description><link>http://ayende.com/3674/zones-of-quality#comment1</link><guid>http://ayende.com/3674/zones-of-quality#comment1</guid><pubDate>Wed, 05 Nov 2008 22:41:41 GMT</pubDate></item></channel></rss>