What about attacks that *don't* produce extraordinary behavior but might be visible in the logs with the right filter (visualizer?)
Kind of like the shadowy figure snooping through the halls while the security guard dozes at the monitor. The alarms are only going to ring if he lobs a grenade....
This is evocative of william gibson's concept of ICE -- in a massively distributed computing environment with a direct-brain virtual-reality interface as primary, you interact with security systems visually.
They appear as complex crystalline structures with no obvious holes other than the known authentication interfaces.
Those who hack/defeat them are called "icebreakers" and they use software which has its own visual attack signature to distract or deflect(overload/DNS attack) the ice or to find hidden cracks (exploits)
Ouch!
I personally find that test-driven development is a helpful approach to dealing with such legacy behemoths... there is some up-front catch-up work but it's usually possible to
a) keep it focused on the task at hand and
b) make at least some of the code simpler (read: better-factored) than it was.
Or you could just run a java-to-vb cross compiler and replace your entire staff with high school students ^^-)
I thought the reason eclipse didn't support easily collapsing and browsing 100's of line of code had to do with lack of need vs other non-java IDEs.
Why would an effective java programmer generate methods with 100's of lines of code that need summarizing? Such methods are known to be error-prone and hard to read and understand. This is why we refactor complex methods into smaller, more focused methods.
Once this is done, the package explorer and outline views are much more effective than code folding would be, since they allow navigation at the semantic level (assuming you've chosen good method names).
It disturbs me that there is so much demand in the java community for a feature that would be most useful in a language that failed to express the power of OO.
Slashdot Mirror
Q: Should I lock my doors or arrest all the theives?
A: Both, silly!
Kind of like the shadowy figure snooping through the halls while the security guard dozes at the monitor. The alarms are only going to ring if he lobs a grenade....
They appear as complex crystalline structures with no obvious holes other than the known authentication interfaces.
Those who hack/defeat them are called "icebreakers" and they use software which has its own visual attack signature to distract or deflect(overload/DNS attack) the ice or to find hidden cracks (exploits)
Visionary stuff (pun partially intended).
Bill couldn't ask for a better lease on the status quo....
Or you could just run a java-to-vb cross compiler and replace your entire staff with high school students ^^-)
I thought the reason eclipse didn't support easily collapsing and browsing 100's of line of code had to do with lack of need vs other non-java IDEs. Why would an effective java programmer generate methods with 100's of lines of code that need summarizing? Such methods are known to be error-prone and hard to read and understand. This is why we refactor complex methods into smaller, more focused methods. Once this is done, the package explorer and outline views are much more effective than code folding would be, since they allow navigation at the semantic level (assuming you've chosen good method names). It disturbs me that there is so much demand in the java community for a feature that would be most useful in a language that failed to express the power of OO.