s*******k
发帖数: 20 | 1 J2EE asks for layer-wise design. However, in my current work, there are lots
of overlayered objects and application structures.
I'd like to refactor them a bit. However, it is hard to have a neat start.
Any suggestions? Experiences?
Thanks in advance. | m******t
发帖数: 2416 | 2
Well, the whole point of "them" going away is that they are not doing any job,
right? 8-)
【在 s*******k 的大作中提到】
: J2EE asks for layer-wise design. However, in my current work, there are lots
: of overlayered objects and application structures.
: I'd like to refactor them a bit. However, it is hard to have a neat start.
: Any suggestions? Experiences?
: Thanks in advance.
| s*******k
发帖数: 20 | 3 Hehe, thrilling solution. Thanks.
Subsequent question would be: Who is gonna take over the job before they get
off radar? upstream or downstream?
often
【在 m******t 的大作中提到】
:
: Well, the whole point of "them" going away is that they are not doing any job,
: right? 8-)
| m******t
发帖数: 2416 | 4
Have you ever noticed that, when companies start laying off people, they often
start with those mid-level managers who basically don't do much more than
delegating?
I'd say the same strategy would serve as a good start point for your
refactoring, too. 8-)
【在 s*******k 的大作中提到】
: J2EE asks for layer-wise design. However, in my current work, there are lots
: of overlayered objects and application structures.
: I'd like to refactor them a bit. However, it is hard to have a neat start.
: Any suggestions? Experiences?
: Thanks in advance.
| s*******k
发帖数: 20 | 5 Noooo :P, the whole point is that they are not doing much enough job. Say,
some of them carry only one or two method, well, inherited and widely used by
its children classes.
job,
【在 m******t 的大作中提到】
:
: Have you ever noticed that, when companies start laying off people, they often
: start with those mid-level managers who basically don't do much more than
: delegating?
: I'd say the same strategy would serve as a good start point for your
: refactoring, too. 8-)
|
|
