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

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

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>