﻿<?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>Thomas Wagner commented on What should I work on next?</title><description>My vote is for LLBLGen Prof
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment44</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment44</guid><pubDate>Sun, 20 Dec 2009 15:39:33 GMT</pubDate></item><item><title>gvo commented on What should I work on next?</title><description>Production profiling!
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment43</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment43</guid><pubDate>Thu, 17 Dec 2009 13:09:13 GMT</pubDate></item><item><title>Tudor T. commented on What should I work on next?</title><description>For me, a LLBLGen profiler would be very usefull.
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment42</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment42</guid><pubDate>Mon, 14 Dec 2009 10:37:47 GMT</pubDate></item><item><title>Ayende Rahien commented on What should I work on next?</title><description>wcoenen,
  
A project is never actually over, there are always more things to do. But at some point the number of things to do reduce to a level that means that you can more or less put it on a back burner.
  
At that point, you have time to do other stuff
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment41</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment41</guid><pubDate>Sat, 12 Dec 2009 10:14:47 GMT</pubDate></item><item><title>wcoenen commented on What should I work on next?</title><description>It seems that most real IT projects need to be maintained forever. Bugs need to be fixed. Features continue to creep in. More bugs because of the feature creep. Etcetera. And eventually you become walled in by all these old projects that continue to demand attention.
  
  
It must be nice to be able to _finish_ a project and get some closure like that. How do you do it?
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment40</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment40</guid><pubDate>Sat, 12 Dec 2009 00:24:51 GMT</pubDate></item><item><title>User3 commented on What should I work on next?</title><description>What about Lightspeed? It's an interesting OR/M and not some inferior product like L2S or EF. I'd buy it for sure..
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment39</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment39</guid><pubDate>Fri, 11 Dec 2009 22:59:18 GMT</pubDate></item><item><title>Dmitry commented on What should I work on next?</title><description>Macto as aTekpub series would be a great idea.
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment38</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment38</guid><pubDate>Fri, 11 Dec 2009 16:37:02 GMT</pubDate></item><item><title>Simon commented on What should I work on next?</title><description>+1 for Macto :-)
  
  
Maybe to make it worth your while you could publish it as open-source, but give the information in a Tekpub series so you get some money too.
  
  
I'd happily pay $20-30 to see how you develop good software!
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment37</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment37</guid><pubDate>Fri, 11 Dec 2009 14:28:08 GMT</pubDate></item><item><title>Shane Walters commented on What should I work on next?</title><description>+1 for Production Profiling
  
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment36</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment36</guid><pubDate>Fri, 11 Dec 2009 14:12:02 GMT</pubDate></item><item><title>cj commented on What should I work on next?</title><description>what about macto?
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment35</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment35</guid><pubDate>Fri, 11 Dec 2009 13:34:13 GMT</pubDate></item><item><title>Ayende Rahien commented on What should I work on next?</title><description>Nikola,
  
I am aware of this, yes.
  
That is quite an invasive approach, and not something that you would probably want to do.
  
I have a much less invasive approach designed.
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment34</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment34</guid><pubDate>Fri, 11 Dec 2009 12:19:54 GMT</pubDate></item><item><title>Nikola Malovic commented on What should I work on next?</title><description>I'm pretty sure that you are aware of it but still (just in case)...
  
  
Have you seen this?
  
[http://code.msdn.microsoft.com/EFProviderWrappers](http://code.msdn.microsoft.com/EFProviderWrappers)</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment33</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment33</guid><pubDate>Fri, 11 Dec 2009 12:11:03 GMT</pubDate></item><item><title>Joe commented on What should I work on next?</title><description>As well as Production Profiling, I like the idea of products that support your other Rhino offerings, RhinoSecurity and RhinoETL.
  
  
I'm still quite new to NH so the biggest benefit of NHProf for me is the confirmation it gives that NH is set up and being used properly. Having this insight to your other offerings will for me, be a big benefit.
  
  
I appreciate the market must be there to make a business work. 
  
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment32</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment32</guid><pubDate>Fri, 11 Dec 2009 11:07:56 GMT</pubDate></item><item><title>Ayende Rahien commented on What should I work on next?</title><description>Dave,
  
Hm, I completely disagree with you on the desktop apps &amp; OR/M part, you might want to read my MSDN article about this exact topic
  
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment31</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment31</guid><pubDate>Fri, 11 Dec 2009 10:28:16 GMT</pubDate></item><item><title>Ayende Rahien commented on What should I work on next?</title><description>Krzystof,
  
The caching stuff is interesting from pure geeky point of view, but working on EF is because I expect a market there.
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment30</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment30</guid><pubDate>Fri, 11 Dec 2009 10:27:10 GMT</pubDate></item><item><title>Ayende Rahien commented on What should I work on next?</title><description>Jonas,
  
I did, just recently, no one noticed
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment29</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment29</guid><pubDate>Fri, 11 Dec 2009 10:26:25 GMT</pubDate></item><item><title>Ayende Rahien commented on What should I work on next?</title><description>Rafal,
  
That is what DAL Prof is all about.
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment28</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment28</guid><pubDate>Fri, 11 Dec 2009 10:26:02 GMT</pubDate></item><item><title>Dave commented on What should I work on next?</title><description>I would like to see a 'DAL' profiler. ORM libraries that provide lazy loading can't be easily used with desktop applications. Either it downloads big chunks of your database or you need to enclose call's to lazy relations with a session. In WPF that's not that easy. 
  
  
I need lazy loaded entities without the hassle to provide a database context when such related entity is accessed using a binding. So we end up writing our own DAL/ORM. It's very simple and projections are limited. For complex projections we used a iBates like solution. Instead of specifying a table, one can specify a query and map the result to an entity.
  
  
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment27</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment27</guid><pubDate>Fri, 11 Dec 2009 10:01:42 GMT</pubDate></item><item><title>Krzysztof Kozmic commented on What should I work on next?</title><description>@Ayende
  
  
Did you find EF interesting, or just go where big enough market is (or presumably soon will be)?
  
  
  
I don't care about EF, and Production profiling seems like the most reasonable choice from where I stand.
  
  
Alghouth you'll hopefully still have some time left for OSS work ;)
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment26</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment26</guid><pubDate>Fri, 11 Dec 2009 08:29:33 GMT</pubDate></item><item><title>Jonas commented on What should I work on next?</title><description>Ayende,
  
  
How about taking some time off :) U are a lucky guy, love what u do and being the best!
  
  
Keep up the sharing!!!!
  
/Jonas
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment25</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment25</guid><pubDate>Fri, 11 Dec 2009 08:10:18 GMT</pubDate></item><item><title>Donny commented on What should I work on next?</title><description>Production Profiling.
  
  
And the "Sorry, but this comment is a duplicate of another comment. Duplicate comments are not allowed" validation is the only reason why us, the "production profiler sect", did not take control over this post...
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment24</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment24</guid><pubDate>Fri, 11 Dec 2009 07:08:44 GMT</pubDate></item><item><title>Rafal commented on What should I work on next?</title><description>+1 production profiling
  
What if there was an option to write a NH Prof adapter that would allow an application that is using custom ORM/DAL to be profiled with NHProf? Would it be very difficult?
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment23</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment23</guid><pubDate>Fri, 11 Dec 2009 06:30:27 GMT</pubDate></item><item><title>Dhananjay Goyani commented on What should I work on next?</title><description>I go for - Production Profiling. ;-)
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment22</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment22</guid><pubDate>Fri, 11 Dec 2009 05:54:50 GMT</pubDate></item><item><title>HereBeDragon commented on What should I work on next?</title><description>Rhino Security. Somehow there aren't many people using it yet. The question is: why? Maybe you could look into that. 
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment21</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment21</guid><pubDate>Fri, 11 Dec 2009 04:43:51 GMT</pubDate></item><item><title>gunteman commented on What should I work on next?</title><description>EF Caching: Indeed. But only having any cool factor if done as an open source project. Other than that, EF is still largely irrelevant.
  
  
Production profiling:Absolutely.
  
  
LLBLGen Prof: Haven't used it much, but Ayende+Frans is always an interesting combination, and the inevitable discussions could result in real community benefit.
  
  
DAL Prof: A bit abstract
  
  
Other: No. Please don't go there.
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment20</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment20</guid><pubDate>Fri, 11 Dec 2009 01:09:41 GMT</pubDate></item><item><title>Jonathan Vukovich commented on What should I work on next?</title><description>Janus: Check out Ayende's Rhino ETL tool. The guys here at work have been using for a huge data migration task and say it's great.
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment19</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment19</guid><pubDate>Thu, 10 Dec 2009 23:08:31 GMT</pubDate></item><item><title>Ayende Rahien commented on What should I work on next?</title><description>ivos,
  
Because I find myself desirous of compensation for EF work
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment18</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment18</guid><pubDate>Thu, 10 Dec 2009 22:17:28 GMT</pubDate></item><item><title>Michael commented on What should I work on next?</title><description>Production Profiling
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment17</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment17</guid><pubDate>Thu, 10 Dec 2009 21:30:15 GMT</pubDate></item><item><title>Janus Knudsen commented on What should I work on next?</title><description>A nice ETL tool instead of SSIS :)
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment16</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment16</guid><pubDate>Thu, 10 Dec 2009 21:18:10 GMT</pubDate></item><item><title>ivos commented on What should I work on next?</title><description>I like the Caching Layer for Entity Framework. Besides the easy answer, my question is: why don't do it open source? 
</description><link>http://ayende.com/4320/what-should-i-work-on-next#comment15</link><guid>http://ayende.com/4320/what-should-i-work-on-next#comment15</guid><pubDate>Thu, 10 Dec 2009 21:07:01 GMT</pubDate></item></channel></rss>