Skip to main content

Migrating to peace

Yes.. Slowly but peacefully, The Application we are developing (at work) is getting stabler and more release-prone [Trademark :)]. I am getting an hour more in my day for myself.I would like to share some of my personal Lessons-learnt from the last two months.

I would consider we are more Agile a project than the ones I worked in before. However, we don't restrict much to methodology. The first noticeable lesson for me here was - No matter how much you want to avoid bureaucracy, There will be some. Even in the most Agile development. And I feel the easy way to put this situation in control is to standardize this bureaucracy. Leaving the loose ends open to bureaucracy will only keep your Agility down. When ever you see such kind of things, repetitive or inhibitive, wrap it into a standard routine. Bear in mind, don't make it into a process - you will only make it more bureaucratic - be open for changes, but establish a routine.

Terminology and Conventions - of all things, speed is accessed by communicating correctly. If two clever minds are not able to communicate - in code, in practice or in regular talk - they are no better than two not-so-clever minds.

Think about Scalability Early - If we are working on highly scalable apps, that notion needs to be on developers mind from the beginning. And Design has to abide by this hard-and-fast-rule. Look at more scalability principles.

And finally be prepared for change. This I leave this as very vague open point. There are so many places, we restrict ourselves for change. code, process, design. All this would be a lot different at migration time than where we started in design. The key is open-ness and changability.

Popular posts from this blog

One page Stock

Alright.. That was a long absence. The whole last week I dint blog. I dint go away. I was "occupied". I was learning stock trading. Its very fascinating. I have a good weeeked blog for you all. Here is my experience. I can literally hyper-link every word from the following paragraphs, but I am writing it as simple as I can so you can look up the italicised words in wikipedia . I got a paper trading account from a brokerage firm . You need one brokerage account first. Then it can be an Equity account where all your money is yours or a Margin account , where some of the money is lent by the brokerage firm. Then I get Buying power , which is the dollor value of how much stocks you can buy. I can make profit by simple rules. Buy when Price is low. Sell when price is high. There is another more intersting way of earning money. Selling short . Thats when price is not high, per say, but when are confident that the price WILL go down. then buy back when its lowest. This is what

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>