Oh well, its easy to come up with ideas, making them work is hard. Even harder is making people get over the “but syndrome”.
Multi-agent systems embedded in the social cloud offer more value then ‘Apps’
on an Eclipse project I got this Team error: abort: requirement ‘dotencode’ not supported!
Load configuration files in cascade to simplify and reduce excess data.
Unless you start Eclipse with the “-showLocation” option there is no way to know what the current workspace location is?
Get errors running SSL on Tomcat. Found one solution.
This was not just a test-driven development (TDD) approach, I said. For example, we could use a Command Line Interface until we have the Rich Internet Application framework ready, we could use flat-files until we knew what the data model should be, etc. The “product” was in flux based on potential customer feedback. So, it was really to do the simplest thing that will get the application doing real work as soon as possible.
Interesting research, JOT: Journal of Object Technology – How AspectJ is Used: An Analysis of Eleven AspectJ Programs: Sven Apel, on how an AOP language, specifically AspectJ, is used in a few sample projects. Was it useful, required? The jury is out.