Has it occurred to you(the reader) that you came across something and you like to comment on it?
Be it a feedback/improvement/suggestion/Aha moment or something you recall, simply said, how something that you see or read related to you?
If this could happen, you got another encyclopedia of stories of people and their experience getting ready to be scripted.
What would be unique to this movement is everyone takes the role of an author and a reader!
1/ How to track different people commenting at different times!
2/ How to keep it consistent with varying media on which comment is to be made?
3/ We have become thick, we use the desktop, and our applications sit on top of them, How to bring it to the desktop?
Now its becoming interesting!
It has been long time I have been wanting to get rid of hard disk failures at home.
For this, the only solution that hit me was use a wireless network storage (WNS) system at home and things would be fine.
That still would need to be dependent on power from the same place where I use the WNS, so not quite a scalable solution.
So here I announce the search for such a service, where ,
1/ I remotely login
2/ I can setup my desktop environment
3/ I can checkout/clone any public-ally hosted project.
4/ I can test-develop-deploy the complete application
5/ I can host the application for the world to enjoy!
Any service providers you come across, please so share here.
For Model is optional/and possibly an impediment, unless asked for.
The following picture depicts my understanding of what piece of technology resides where when writing the code from a UI->Business->DB.
When doing TDD<->Code, there are very short and quick feedback cycles due to which there is good paced development.
When doing it with modeling involved as the short feedback cycles turns into a painstakingly long , and hence looses the pace that could have been achieved with no MDA at all.
Even with MDA as a choice, is it beneficial to extract technical details from the model or derive the model from the interface?
The interfaces act as the point of inflection of choosing whether to MDA or not.
I am not very much into Big-Upfront-Design camp,maybe due to lack of experience but as I understand every software solution in the writing has its own characteristics that are better dealt with when dealt with no big designs that over-shadow its actual requirement.
With features like reverse engineering from code-to-UML, although the cycle could be shortened, but only to load the design with something conceptual at a high level, even with a high probability that the same understanding could be useless or simply a cause of not being able to implement an elegant solution.
The fact that MDA is dependent on the interfaces to proceed and TDD creates those interfaces, not by thinking-out the complete system, but on a case-by-case basis, so the two approaches can exist, but in true agile spirit?
I don’t think so.
This morning an idea just hit me of enabling/disabling features of an application/system remotely.
If we add(already have?) a way where a module(per-say feature) has an attribute of whether it is alive or not, we can control the way a feature is available at runtime for that application/product.
We do layering, we would need to put the feature On_OFF switch withing that layering so that would need a standard of packaging/module-ring an application.
Is this possible and how would that be advantageous?
Came across an interesting scenario.
Had a pre-running test case. And then removed the @Test annotation from it, and voila!
It seems JUnit developers really thought of this scenario where a developer un-annotates a test method and they gave an appropriate exception!
Well this seems to be an eclipse bug.It occured when I copied a window eclipse shared project and tried to run it.
I could not overcome this error till date, using following resolutions:
1/ Exclude junit3.3(NA)
2/Remove extension from TestCase.(NA)
3/Remove duplicate junit jar from the project.(NA)
Did not think this would be so quick for creation of this blog!
I needed to display the agile manifesto and had to include the notice, did some html and a little bit of copy-paste and here it is:
Thought it would be useful for someone!
Please go ahead and use it.