Biubiu wrote:
电脑的要求比人的要求低多了。所以大多数人做的事情是让电脑happy。真正会抽象的人是把编程作为艺术在做的人，即时科学家又是艺术家，少之又少。

menzy wrote:
现在缺少的还是有创作能力的人
浅尝辄止，国人肤浅

cxp108 wrote:
其实也不一定要到“艺术”的这种程度，但我觉得抽象是很基本的代码重用技巧。
可是我从业至今真的很少看到有这种能力的程序员。很多程序员都是只懂得一种
程序结构...不管在那个程序里都是DAO,service,action等等...而对真正需要抽象
的业务逻辑，却完全不与理睬，对于一个新的需求，就是进行新的编码，而不是考虑
如何更好的重用现有代码。

Biubiu wrote:
殊不知应用是“壳”，业务是”核“。

wes109 wrote:
牢骚贴，鉴定完毕！

Biubiu wrote:
经过几次折腾才会知道啥叫重用。很多从业人员都是跟风性质的，所以领头羊很重要。Spring、Hibernate都是应该框架，大多数人把业务逻辑散落在这些应用框架中。殊不知应用是“壳”，业务是”核“。

JiafanZhou wrote:
I believe that Java has its own cons and pros.

JiafanZhou wrote:
I believe that Java has its own cons and pros.

cxp108 wrote:
java具有众多高级语言的优点当然也继承了缺点，不过实践也证明
它是人类驾驭计算机来完成任务的好帮手。

for f in jiafanz/*; do
  "$f" &
done

handleException()
{
...
}

method1()
{
    try
   {
   
   }
   catch (Exception ex)
   {
       handleException()  
   }
}

method2()...

method3()...

methodX()...

floater wrote:
Example 1: You can make a smaill class to seal the details so that you code is similar to shell scripts, I suspect there are already code on the internet to do this.

floater wrote:
Example 2: If there are hundreds of methods that need this, the AOP is really arguable. Because if there are hundreds of methods, then the code base is pretty large, likely to be maintained by several different teams, with AOP weaving, it's hard to track the code, think about debugging. I am having this problem now, scratch my hair and have no clue. Somewhere somehow one of the places the code doesn't catch the exception(forgot to weave), it bombs out everyday, don't know where, don't know how. There are 21 million of calculations and only a dozen errors, very hard to find where it happened. Damn it.

floater wrote:
Example 3: using reflection we can make java more like scripting, but it's hard to track down where what is used. Strong typing makes tracking a lot easier. So depending on where we use the language, it's hard to compare java/c++ with scripting languages. It's more like a balanced choice.

wes109 wrote:
牢骚贴，鉴定完毕！

robin wrote:
同意！