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

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.

Using Equinox CommandProvider to make OSGi console interactive.

After fiddling with the First Bundles that "Hello World"-ed upon Activation, You want to see more interactivity in OSGi. Although Using OSGi for an interactive Command Line Application would be like this one would be, well, a callable over-kill, I am going to start with an example and Expand it in later posts. So, please Welcome CommandProvider. CommandProvider is an EQUINOX specific API for extending the Console. This basic Example illustrates how to get a command from console and do something in java and also gets your feet wet on Service Registry package com.so.examples.commandconsole; import org. eclipse .osgi.framework.console .CommandInterpreter; import org.eclipse.osgi.framework.console.CommandProvider; public class DisplayMessageCommand implements CommandProvider { public void _say(CommandInterpreter ci) { ci.print("You said:" + ci.nextArgument()); } @Override public String getHelp() { return "\tsay - repeats what you say\n"; } }

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour