I*******o
发帖数: 53 | 1 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 | c*****t
发帖数: 1879 | 2 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 的大作中提到】
: 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
发帖数: 14569 | 3 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 的大作中提到】
: 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
发帖数: 34805 | 4 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 的大作中提到】
: 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
发帖数: 2859 | 5 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 的大作中提到】
: 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
|
|
