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

Javascript: Convert Strings to Binary (and representing in a nerdy way!)

I follow those GoogleDevelopers Videos . Sometime back, in one of the presentations on GoogleIO, there was this interesting string of dots at the bottom of each page of the presentation . They looked like random big and small dots. A similar bunch of dots were also on the T-shirt of a presenter was wearing in another presentation . While it seemed something in the pattern, I could not find what it was. Finally, another presenter cleared the matter that those dots are just binary representation of "GOOGLEIO" (So much for advertizing Google IO, Impressive!). So I wanna do it. Takes me back to days of those DSP classes at school. Nerdy me had to churn some old brain cells. I remember those first programming language classes in Pascal and C when you were asked to do fibonacci series and converting a binary string to ascii codes. That *experience* came handy here: Check it out! Text to Binarize: For those who came to copy the javascript code to convert string to binary,

MySql Copying Table Structures.

Some times you need to copy only table structures across databases. This article describes two ways of doing it. If the whole database schema need to be exported, mysqldump is very effective. A --nodata flag will dump all tables' schema. Like this. mysqldump --nodata -p -u username databaseName But if you want to copy a specific table, individually, you could use "create table like" feature. You could create it even from a different database. However it must be on the same mysqld instance. Like this. create table newtable like oldtable; --Or from a table in other database create table mytable like otherdatabase.tablename;

javascript maxlength for textarea with \r\n breaks in java (esp Firefox)

Textareas allow new lines to enter. These are represented by \n (1) or \r\n (2) characters. But when you save to DB you have a limit to certain length of chars. There is no maxlength attribute in HTML that will stop you from entering data. This is generally acomplished by Javascript. You do a onkeyup hook and stop event or trim after textarea.value.length > maxlength. There are many other solutions out there.. But.. Here is the problem that most of those solutions overlook, How do you deal with the count on \n and \r\n representations. Lets first see how it matters. If the text entered has new lines, the length is calculated differently in Firefox and IE. When you enter a Text like 01234 567890 You expect the textarea.value.length to be 11. (10 chars + new line).On the backend, however, java would recieve it as 12 chars (10 chars + \r\n) (this is irrespective of FF or IE). So you are effectively saving 12 chars to DB. Worse yet, IE seems to figure textarea.value.length as 12 (