Comments on: “Those who coded, also coded” http://almaer.com/blog/those-who-coded-also-coded blogging about life, the universe, and everything tech Sat, 08 Sep 2012 07:06:53 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Laird Nelson http://almaer.com/blog/those-who-coded-also-coded/comment-page-1#comment-20225 Laird Nelson Fri, 25 Feb 2005 15:10:11 +0000 http://almaer.com/blog2/those-who-coded-also-coded#comment-20225 Neat idea. Although the tool is quite deficient in other ways, ArgoUML had something a little bit like this in the last version I used. Various "advisers" would crop up to let you know if you were falling into design traps. They weren't, as far as I know, collaborative in any way, but the idea was a good one. Neat idea. Although the tool is quite deficient in other ways, ArgoUML had something a little bit like this in the last version I used. Various “advisers” would crop up to let you know if you were falling into design traps. They weren’t, as far as I know, collaborative in any way, but the idea was a good one.

]]> By: Laird Nelson http://almaer.com/blog/those-who-coded-also-coded/comment-page-1#comment-20226 Laird Nelson Fri, 25 Feb 2005 15:10:11 +0000 http://almaer.com/blog2/those-who-coded-also-coded#comment-20226 Neat idea. Although the tool is quite deficient in other ways, ArgoUML had something a little bit like this in the last version I used. Various "advisers" would crop up to let you know if you were falling into design traps. They weren't, as far as I know, collaborative in any way, but the idea was a good one. Neat idea. Although the tool is quite deficient in other ways, ArgoUML had something a little bit like this in the last version I used. Various “advisers” would crop up to let you know if you were falling into design traps. They weren’t, as far as I know, collaborative in any way, but the idea was a good one.

]]> By: Alan Green http://almaer.com/blog/those-who-coded-also-coded/comment-page-1#comment-20223 Alan Green Fri, 25 Feb 2005 03:16:00 +0000 http://almaer.com/blog2/those-who-coded-also-coded#comment-20223 Let's see... version 12.5, up from Eclipse 3 and IDEA 4.5, let's call it 8 versions at 18 months each, so your vision was twelve years into the future. What language were you coding in? :) (PS: Brilliant idea! Go get a patent! Ooops, too late - you already told the world) Let’s see… version 12.5, up from Eclipse 3 and IDEA 4.5, let’s call it 8 versions at 18 months each, so your vision was twelve years into the future. What language were you coding in? :)

(PS: Brilliant idea! Go get a patent! Ooops, too late – you already told the world)

]]> By: Alan Green http://almaer.com/blog/those-who-coded-also-coded/comment-page-1#comment-20224 Alan Green Fri, 25 Feb 2005 03:16:00 +0000 http://almaer.com/blog2/those-who-coded-also-coded#comment-20224 Let's see... version 12.5, up from Eclipse 3 and IDEA 4.5, let's call it 8 versions at 18 months each, so your vision was twelve years into the future. What language were you coding in? :) (PS: Brilliant idea! Go get a patent! Ooops, too late - you already told the world) Let’s see… version 12.5, up from Eclipse 3 and IDEA 4.5, let’s call it 8 versions at 18 months each, so your vision was twelve years into the future. What language were you coding in? :)

(PS: Brilliant idea! Go get a patent! Ooops, too late – you already told the world)

]]> By: Nick http://almaer.com/blog/those-who-coded-also-coded/comment-page-1#comment-20221 Nick Thu, 24 Feb 2005 20:00:09 +0000 http://almaer.com/blog2/those-who-coded-also-coded#comment-20221 I hope tools like that never exist. Think of what they'll do to hourly rates! :) I hope tools like that never exist. Think of what they’ll do to hourly rates! :)

]]> By: Nick http://almaer.com/blog/those-who-coded-also-coded/comment-page-1#comment-20222 Nick Thu, 24 Feb 2005 20:00:09 +0000 http://almaer.com/blog2/those-who-coded-also-coded#comment-20222 I hope tools like that never exist. Think of what they'll do to hourly rates! :) I hope tools like that never exist. Think of what they’ll do to hourly rates! :)

]]> By: Emmanuel Pirsch http://almaer.com/blog/those-who-coded-also-coded/comment-page-1#comment-20219 Emmanuel Pirsch Thu, 24 Feb 2005 17:19:11 +0000 http://almaer.com/blog2/those-who-coded-also-coded#comment-20219 This is a cool idea... However, I don't know how one could implement this. The plugin would have to "understand" the context in which the API is being used. It would also have to be able to delimit exactly what is the pattern. Which is not as easy as it is to know that someone who bought a book also bought books X, Y and Z. The same idea could be useful event if it's not shared... There is always some coding patterns that this kind of plugin could detect... A bit like codesense but with auto-learning. It is certainly something that would be interesting to explore. One problem I could see with that is that what makes a pattern useful is the documentation and "rule" for when it is applicable. A plugin could "easily" learn what is done, but not why it is done. But then we could all get sued by Amazon or Microsoft (clippy anyone) ;-) This is a cool idea…

However, I don’t know how one could implement this. The plugin would have to “understand” the context in which the API is being used. It would also have to be able to delimit exactly what is the pattern. Which is not as easy as it is to know that someone who bought a book also bought books X, Y and Z.

The same idea could be useful event if it’s not shared… There is always some coding patterns that this kind of plugin could detect… A bit like codesense but with auto-learning.

It is certainly something that would be interesting to explore.

One problem I could see with that is that what makes a pattern useful is the documentation and “rule” for when it is applicable. A plugin could “easily” learn what is done, but not why it is done.

But then we could all get sued by Amazon or Microsoft (clippy anyone) ;-)

]]> By: Emmanuel Pirsch http://almaer.com/blog/those-who-coded-also-coded/comment-page-1#comment-20220 Emmanuel Pirsch Thu, 24 Feb 2005 17:19:11 +0000 http://almaer.com/blog2/those-who-coded-also-coded#comment-20220 This is a cool idea... However, I don't know how one could implement this. The plugin would have to "understand" the context in which the API is being used. It would also have to be able to delimit exactly what is the pattern. Which is not as easy as it is to know that someone who bought a book also bought books X, Y and Z. The same idea could be useful event if it's not shared... There is always some coding patterns that this kind of plugin could detect... A bit like codesense but with auto-learning. It is certainly something that would be interesting to explore. One problem I could see with that is that what makes a pattern useful is the documentation and "rule" for when it is applicable. A plugin could "easily" learn what is done, but not why it is done. But then we could all get sued by Amazon or Microsoft (clippy anyone) ;-) This is a cool idea…

However, I don’t know how one could implement this. The plugin would have to “understand” the context in which the API is being used. It would also have to be able to delimit exactly what is the pattern. Which is not as easy as it is to know that someone who bought a book also bought books X, Y and Z.

The same idea could be useful event if it’s not shared… There is always some coding patterns that this kind of plugin could detect… A bit like codesense but with auto-learning.

It is certainly something that would be interesting to explore.

One problem I could see with that is that what makes a pattern useful is the documentation and “rule” for when it is applicable. A plugin could “easily” learn what is done, but not why it is done.

But then we could all get sued by Amazon or Microsoft (clippy anyone) ;-)

]]>