c*****t
发帖数: 1879 | 1 selected method/variable highlight.
This thing is so damn useful. Sigh, IDEA 6.0 doesn't have it...
It helps tremendously in code reading and copying/pasting.
This is another feature that makes Eclipse attractive, along with
compile-on-save + well managed problem list.
I wonder why IntelliJ IDEA are so slow to adapt some of Eclipse's
most useful features. |
o***g
发帖数: 2784 | 2 我现在也被compile on save给带坏了，好像程序不需要编译就可以运行了一样。
去VS或者什么的还要build，特不习惯了
【在 c*****t 的大作中提到】
: selected method/variable highlight.
: This thing is so damn useful. Sigh, IDEA 6.0 doesn't have it...
: It helps tremendously in code reading and copying/pasting.
: This is another feature that makes Eclipse attractive, along with
: compile-on-save + well managed problem list.
: I wonder why IntelliJ IDEA are so slow to adapt some of Eclipse's
: most useful features.
|
h**d
发帖数: 474 | 3 Frankly speaking, if you do TDD, I don't think this feature is so useful
Ant is my baby:)
【在 o***g 的大作中提到】
: 我现在也被compile on save给带坏了，好像程序不需要编译就可以运行了一样。
: 去VS或者什么的还要build，特不习惯了
|
o***g
发帖数: 2784 | 4 what's TDD?
【在 h**d 的大作中提到】
: Frankly speaking, if you do TDD, I don't think this feature is so useful
: Ant is my baby:)
|
h**d
发帖数: 474 | 5 test driven development
【在 o***g 的大作中提到】
: what's TDD?
|
m******t
发帖数: 2416 | 6
I always run full test suites outside eclipse, in ant. Although I do find
eclipse's on the fly building extremely helpful, especially for the warning
messages - I usually turn on most of them.
【在 h**d 的大作中提到】
: Frankly speaking, if you do TDD, I don't think this feature is so useful
: Ant is my baby:)
|
g*****g
发帖数: 34805 | 7 How do you take care of legacy codes not written by you?
I realize if I turn on many warnings, I'd have tons of them
there already.
warning
【在 m******t 的大作中提到】
:
: I always run full test suites outside eclipse, in ant. Although I do find
: eclipse's on the fly building extremely helpful, especially for the warning
: messages - I usually turn on most of them.
|
m******t
发帖数: 2416 | 8
Oh, of course I have to lower the standards when working on code I didn't
write. What I always try to do is cleaning up the easy bits as I can while I
'm at it. Most warnings are things like unused imports, unused local
variables, unnecessary casts, etc. which are usually easy to fix.
【在 g*****g 的大作中提到】
: How do you take care of legacy codes not written by you?
: I realize if I turn on many warnings, I'd have tons of them
: there already.
:
: warning
|
h**d
发帖数: 474 | 9 The most difficult thing is legacy code without tests:(
Also it's difficult to write tests for this kind of code when you modify
them,
since the design is generally bad
I
【在 m******t 的大作中提到】
:
: Oh, of course I have to lower the standards when working on code I didn't
: write. What I always try to do is cleaning up the easy bits as I can while I
: 'm at it. Most warnings are things like unused imports, unused local
: variables, unnecessary casts, etc. which are usually easy to fix.
|
m******t
发帖数: 2416 | 10
Oh man, tell _me_ about it. My daily job these days is to deal with that
kind of code - don't you sometimes just have the feeling that you wish you
could reach inside the monitor, grab the crap, and tear it into pieces?
【在 h**d 的大作中提到】
: The most difficult thing is legacy code without tests:(
: Also it's difficult to write tests for this kind of code when you modify
: them,
: since the design is generally bad
:
: I
|
|
|
h**d
发帖数: 474 | 11 haha...sometimes, rewrite is easier than refactoring:)
For that kind of code, I normally treat them as blackbox.
If I have to modify them, I just write kind of integration(instead of unit)
tests for the piece which I had to touch. Anyway, it's nightmare
【在 m******t 的大作中提到】
:
: Oh man, tell _me_ about it. My daily job these days is to deal with that
: kind of code - don't you sometimes just have the feeling that you wish you
: could reach inside the monitor, grab the crap, and tear it into pieces?
|
g*****g
发帖数: 34805 | 12 Unless I am sure this system will be fully re-tested,
I wouldn't do that, any change to the code, however simple,
may introduce bugs. Usually I would only clean up
source file I changed, which will certainly be tested anyway.
I
【在 m******t 的大作中提到】
:
: Oh man, tell _me_ about it. My daily job these days is to deal with that
: kind of code - don't you sometimes just have the feeling that you wish you
: could reach inside the monitor, grab the crap, and tear it into pieces?
|
s******e
发帖数: 493 | 13 My $0.02.
I would say the most difficult thing about legacy code is performance
related issues. Such as open up too many connection pools, object is long
gone but listeners still around, etc. These problems usually won't be found
if the app doesn't run long enough or the system is not under heavy load. |
c*****t
发帖数: 1879 | 14
Just found out from IDEA forum that ctrl-shift-F7 can do that.
Multiple variables can be highlighted. Slightly less convenient than
Eclipse, but the functionality is there. I feel so much more
comfortable reading/writing code now :)
【在 c*****t 的大作中提到】
: selected method/variable highlight.
: This thing is so damn useful. Sigh, IDEA 6.0 doesn't have it...
: It helps tremendously in code reading and copying/pasting.
: This is another feature that makes Eclipse attractive, along with
: compile-on-save + well managed problem list.
: I wonder why IntelliJ IDEA are so slow to adapt some of Eclipse's
: most useful features.
|
c*m
发帖数: 836 | 15 我对legacy code的态度是只加不改，不行就加个branch，原来的还留着原封不动，看
subversion里的code history, 大多数人都是这么干的，除非上面真的给批时间，不然
哪儿有功夫给他彻底清理啊。
都不敢想象3年以后这个code会变成什么样，嘿嘿。
found
【在 s******e 的大作中提到】
: My $0.02.
: I would say the most difficult thing about legacy code is performance
: related issues. Such as open up too many connection pools, object is long
: gone but listeners still around, etc. These problems usually won't be found
: if the app doesn't run long enough or the system is not under heavy load.
|
m******t
发帖数: 2416 | 16
I absolutely agree - that's what I meant by "while I'm at it." 8-)
【在 g*****g 的大作中提到】
: Unless I am sure this system will be fully re-tested,
: I wouldn't do that, any change to the code, however simple,
: may introduce bugs. Usually I would only clean up
: source file I changed, which will certainly be tested anyway.
:
: I
|
g******e
发帖数: 3760 | 17
~~~~~~~~~~ Sorry not so familar with Eclipse. what exactly is it? Looks like
Idea has this stuff.
【在 c*****t 的大作中提到】
: selected method/variable highlight.
: This thing is so damn useful. Sigh, IDEA 6.0 doesn't have it...
: It helps tremendously in code reading and copying/pasting.
: This is another feature that makes Eclipse attractive, along with
: compile-on-save + well managed problem list.
: I wonder why IntelliJ IDEA are so slow to adapt some of Eclipse's
: most useful features.
|
g******e
发帖数: 3760 | 18
Just saw this post. I used this function everyday. :-P
【在 c*****t 的大作中提到】
:
: Just found out from IDEA forum that ctrl-shift-F7 can do that.
: Multiple variables can be highlighted. Slightly less convenient than
: Eclipse, but the functionality is there. I feel so much more
: comfortable reading/writing code now :)
|
c*****t
发帖数: 1879 | 19 I prefer mouse selection though. A lot easier.
【在 g******e 的大作中提到】
:
: Just saw this post. I used this function everyday. :-P
|
g******e
发帖数: 3760 | 20 It is indeed a very useful function. The other one I found very useful is
the "find usage" function in IDEA. It makes changing legacy code (like
discussed in previous posts) much more safer.
【在 c*****t 的大作中提到】
: I prefer mouse selection though. A lot easier.
|
|
|
c*****t
发帖数: 1879 | 21 I think that every ide that has refactor engine comes with this feature.
【在 g******e 的大作中提到】
: It is indeed a very useful function. The other one I found very useful is
: the "find usage" function in IDEA. It makes changing legacy code (like
: discussed in previous posts) much more safer.
|
s******e
发帖数: 493 | 22 What eclipse attracts me is that there are so many plugins for your
different needs. With these plugins, you can run tomcat inside eclipse, you
can configure your spring projects so easily, you can read ur db schema and
automatically generate all the vos, daos, and mapping without a single line
of code, etc. |
g******e
发帖数: 3760 | 23 That's true. But each ide has slightly different implementation of this
function. Sometimes it is a matter of how familar with the IDE and personal
preference, like the war of vi and emacs. When I first touch VisualAge I was
impressed by the compile-on-the-fly but later found out it is not so useful
in the real life.
【在 c*****t 的大作中提到】
: I think that every ide that has refactor engine comes with this feature.
|
s**o
发帖数: 584 | 24 it's been in JDEV for a couple of years already. Recenlty, PL/SQL
developer finally put it in 7.0 upon my request :)
【在 c*****t 的大作中提到】
: selected method/variable highlight.
: This thing is so damn useful. Sigh, IDEA 6.0 doesn't have it...
: It helps tremendously in code reading and copying/pasting.
: This is another feature that makes Eclipse attractive, along with
: compile-on-save + well managed problem list.
: I wonder why IntelliJ IDEA are so slow to adapt some of Eclipse's
: most useful features.
|
B******N
发帖数: 445 | 25 never like ant. thought i wrote quite a lot. i am a big ide fan.
unless sometimes i have to.
【在 h**d 的大作中提到】
: Frankly speaking, if you do TDD, I don't think this feature is so useful
: Ant is my baby:)
|
h**d
发帖数: 474 | 26 I'm a big continuous integration fan, hehe
Just a quick question, do you write unit tests?
【在 B******N 的大作中提到】
: never like ant. thought i wrote quite a lot. i am a big ide fan.
: unless sometimes i have to.
|
m******t
发帖数: 2416 | 27 IDE works great for individual developers. On the other hand, it's hard to
automate and standardize a build process in IDE. In a TDD process, you can't
really rely on IDE for team-level integration.
【在 B******N 的大作中提到】
: never like ant. thought i wrote quite a lot. i am a big ide fan.
: unless sometimes i have to.
|
B******N
发帖数: 445 | 28 i wrote the first version of continuous integration ant build with clover
coverage report for unit test in company. Once it's done, you don't
frequently change them. But for unit test during development, i like it run
from my ide, instead of invoking ant build which is slower and not handly at
all.
【在 h**d 的大作中提到】
: I'm a big continuous integration fan, hehe
: Just a quick question, do you write unit tests?
|
h**d
发帖数: 474 | 29 I agree when you ant scripts reach certain stage, you don't change them very
often. But you have to run them all the time, or how do you make sure you
did not break other people's tests before you checkin?
run
at
【在 B******N 的大作中提到】
: i wrote the first version of continuous integration ant build with clover
: coverage report for unit test in company. Once it's done, you don't
: frequently change them. But for unit test during development, i like it run
: from my ide, instead of invoking ant build which is slower and not handly at
: all.
|
m******t
发帖数: 2416 | 30
run
at
Running unit tests from IDE and from a build script both make sense - in
different contexts. It's convenient to run a unit test in IDE for debugging.
But it's not repeatable, which is the key for continuous integration, and
can only be achieved through build scripts (of course not necessarily ant).
【在 B******N 的大作中提到】
: i wrote the first version of continuous integration ant build with clover
: coverage report for unit test in company. Once it's done, you don't
: frequently change them. But for unit test during development, i like it run
: from my ide, instead of invoking ant build which is slower and not handly at
: all.
|
|
|
h**d
发帖数: 474 | 31 nod nod nod
debugging.
【在 m******t 的大作中提到】
:
: run
: at
: Running unit tests from IDE and from a build script both make sense - in
: different contexts. It's convenient to run a unit test in IDE for debugging.
: But it's not repeatable, which is the key for continuous integration, and
: can only be achieved through build scripts (of course not necessarily ant).
|
h******a
发帖数: 46 | 32 I think the "killer feature" of eclipse is it's free :)
【在 c*****t 的大作中提到】
: selected method/variable highlight.
: This thing is so damn useful. Sigh, IDEA 6.0 doesn't have it...
: It helps tremendously in code reading and copying/pasting.
: This is another feature that makes Eclipse attractive, along with
: compile-on-save + well managed problem list.
: I wonder why IntelliJ IDEA are so slow to adapt some of Eclipse's
: most useful features.
|
