c*r
2 楼
最近在看,昨天看到其中的一个故事,晚餐谋杀案,还不错。
I*o
3 楼
Some people say: as long as it does the job, it is good......
Issues I can think of:
scalable
make good use of proven framework/libs
easy to read by other team members
Issues I can think of:
scalable
make good use of proven framework/libs
easy to read by other team members
c*t
5 楼
Don't think too much. If you are a programmer, that's not
your job. Your job is to do what you need to do to get things
done. Patterns, good coding styles etc ultimately is to serve
this purpose, and pass the code review.
【在 I*******o 的大作中提到】![](/moin_static193/solenoid/img/up.png)
: Some people say: as long as it does the job, it is good......
: Issues I can think of:
: scalable
: make good use of proven framework/libs
: easy to read by other team members
your job. Your job is to do what you need to do to get things
done. Patterns, good coding styles etc ultimately is to serve
this purpose, and pass the code review.
【在 I*******o 的大作中提到】
![](/moin_static193/solenoid/img/up.png)
: Some people say: as long as it does the job, it is good......
: Issues I can think of:
: scalable
: make good use of proven framework/libs
: easy to read by other team members
g*y
7 楼
Easy to change -- that's my only rule.
I don't read a lot of good code, but I do read a lot of bad code, all of
them share the same problem: 牵一发动全身
BTW, make good use of framework/lib doesn't mean anything. If someone use
tools skillfully, he could be a craftsman, that doesn't mean he makes art.
【在 I*******o 的大作中提到】![](/moin_static193/solenoid/img/up.png)
: Some people say: as long as it does the job, it is good......
: Issues I can think of:
: scalable
: make good use of proven framework/libs
: easy to read by other team members
I don't read a lot of good code, but I do read a lot of bad code, all of
them share the same problem: 牵一发动全身
BTW, make good use of framework/lib doesn't mean anything. If someone use
tools skillfully, he could be a craftsman, that doesn't mean he makes art.
【在 I*******o 的大作中提到】
![](/moin_static193/solenoid/img/up.png)
: Some people say: as long as it does the job, it is good......
: Issues I can think of:
: scalable
: make good use of proven framework/libs
: easy to read by other team members
g*g
9 楼
Good framework makes a dumb developer's damage under control.
e.g. Any decent web framework struts, spring mvc etc. have a
solid pattern how you layout your MVC classes. As long as you follow
it, you can screw one page but hardly more.
There was one time a developer push every variable into application
scope though, and I had to make him fired and rewrite it. There's simply
no way you can right the ship for dumb minds like that.
【在 g**********y 的大作中提到】![](/moin_static193/solenoid/img/up.png)
: Easy to change -- that's my only rule.
: I don't read a lot of good code, but I do read a lot of bad code, all of
: them share the same problem: 牵一发动全身
: BTW, make good use of framework/lib doesn't mean anything. If someone use
: tools skillfully, he could be a craftsman, that doesn't mean he makes art.
e.g. Any decent web framework struts, spring mvc etc. have a
solid pattern how you layout your MVC classes. As long as you follow
it, you can screw one page but hardly more.
There was one time a developer push every variable into application
scope though, and I had to make him fired and rewrite it. There's simply
no way you can right the ship for dumb minds like that.
【在 g**********y 的大作中提到】
![](/moin_static193/solenoid/img/up.png)
: Easy to change -- that's my only rule.
: I don't read a lot of good code, but I do read a lot of bad code, all of
: them share the same problem: 牵一发动全身
: BTW, make good use of framework/lib doesn't mean anything. If someone use
: tools skillfully, he could be a craftsman, that doesn't mean he makes art.
r*l
11 楼
Modulize your design, not too fine-grined, not too coarse
Layer the modules
Remove circular dependency
Commonize shared modules
Make aggregated,sense-making API
Seperate code and configuration
And more I cannot think of right now.
A lot of people nowadays praise ruby on rails, which violates
the above rules :)
【在 I*******o 的大作中提到】![](/moin_static193/solenoid/img/up.png)
: Some people say: as long as it does the job, it is good......
: Issues I can think of:
: scalable
: make good use of proven framework/libs
: easy to read by other team members
Layer the modules
Remove circular dependency
Commonize shared modules
Make aggregated,sense-making API
Seperate code and configuration
And more I cannot think of right now.
A lot of people nowadays praise ruby on rails, which violates
the above rules :)
【在 I*******o 的大作中提到】
![](/moin_static193/solenoid/img/up.png)
: Some people say: as long as it does the job, it is good......
: Issues I can think of:
: scalable
: make good use of proven framework/libs
: easy to read by other team members
相关阅读
JSP技术简介 [fwd]Re: 有谁调过ACE/TAO吗?Re: about jsp and servlet使用JAVA的一则经验和教训ctrl + gSpecial Thanks to TARCryptoquivalence Classes水母关于jsp的讨论Re: 如何Debug 在JNI 里调用的DLL? (急)Re: 有感于《一个最近完成的JAVA项目的反思》Java's performance mythto Water, other future programmersMore information about Java Plug-in SPECIFICATIONldap exampleRe: java class decompileRe: question about interface.(也许是答案)Re: file permissions when using java creating filesstable release of JFTP 0.0.5 availableRe: new problem, using browser to run java appletRe: Help! JDBC-ODBC in servlet. Thanks.