﻿<?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>Kyle Szklenski commented on NH Prof: Architectural Overview</title><description>Cool. To me, that implies to the untrained eye that it's highly coupled - "You shouldn't have to change every single layer in order to display new data!" In my view, though, that seems like a really stupid statement. I've never seen a single program where that senseless platitude worked out. I've seen people try, and it became so complicated that they themselves could not make a change when it was necessary, though!
  
  
I didn't have any other place to write this right now, but it's not terribly on topic. What is the point of an abstraction if there is nothing abstract about it, or in other words an object that does not have any functions which can be overridden?
</description><link>http://ayende.com/4059/nh-prof-architectural-overview#comment6</link><guid>http://ayende.com/4059/nh-prof-architectural-overview#comment6</guid><pubDate>Wed, 24 Jun 2009 15:17:37 GMT</pubDate></item><item><title>Ayende Rahien commented on NH Prof: Architectural Overview</title><description>Kyle,
  
A good example of that would be changing the way that we are showing query duration, instead of just showing overall duration, we want to show time in db and time processed by NH.
  
That means that we have to read the new data from the profiled application, attach them to the right place in the model, and actually change both the backend model and presentation model to contain both data items.
</description><link>http://ayende.com/4059/nh-prof-architectural-overview#comment5</link><guid>http://ayende.com/4059/nh-prof-architectural-overview#comment5</guid><pubDate>Tue, 23 Jun 2009 18:00:44 GMT</pubDate></item><item><title>Kyle Szklenski commented on NH Prof: Architectural Overview</title><description>One question I would ask: Can you give an example of a "vertical slice" as you put it, and why, when making said vertical slice, you don't have jagged lines reaching out? I'm assuming that's what you mean, but could have taken the metaphor incorrectly, so correct me if I'm wrong.
  
  
I imagine something like that would be a new feature that you want to define which the UI and the model do not necessarily support.
</description><link>http://ayende.com/4059/nh-prof-architectural-overview#comment4</link><guid>http://ayende.com/4059/nh-prof-architectural-overview#comment4</guid><pubDate>Tue, 23 Jun 2009 13:02:19 GMT</pubDate></item><item><title>cowgaR commented on NH Prof: Architectural Overview</title><description>ah, it was a joke ;p
  
  
never try to "escape" your highly technical role?
</description><link>http://ayende.com/4059/nh-prof-architectural-overview#comment3</link><guid>http://ayende.com/4059/nh-prof-architectural-overview#comment3</guid><pubDate>Tue, 23 Jun 2009 08:30:11 GMT</pubDate></item><item><title>Ayende Rahien commented on NH Prof: Architectural Overview</title><description>cowgaR,
  
That is because low level message processing have a very important role in the overall architecture.
  
Low level msg processing simply means the part that process the raw data from NHibernate
</description><link>http://ayende.com/4059/nh-prof-architectural-overview#comment2</link><guid>http://ayende.com/4059/nh-prof-architectural-overview#comment2</guid><pubDate>Tue, 23 Jun 2009 08:16:32 GMT</pubDate></item><item><title>cowgaR commented on NH Prof: Architectural Overview</title><description>Oren, I can't get something...
  
  
at _very_ high level you have _low_ level messages processor...
  
something must have been architected real baaaad =)
</description><link>http://ayende.com/4059/nh-prof-architectural-overview#comment1</link><guid>http://ayende.com/4059/nh-prof-architectural-overview#comment1</guid><pubDate>Tue, 23 Jun 2009 07:52:02 GMT</pubDate></item></channel></rss>