Point Element

Its the discovery of the decade. Apparently I've found out that I'm too good for this world and so my life sucks! Well the thing is that I'm a jack of all trades and my parents were too good for me. Which led to them teaching me to be accepting and patient and lots of other such non-interesting things. And so right now in my two and half year of career I've ended up working on following things: 1. Windows administration - system assembly, setup and is installation and troubleshooting. In fact my windows skills are almost power user level. 2 Same power user level with Linux: yeah I started with slackware but that was when I was 16. Its 9 yrs now and i have seen and uses a number of Linux distros. I can handle basic troubleshooting and almost all tweaking of a new installation. 3 .net development: Right after my engineering in 2k8 I did a course in .net, so I can code in both C# as well as VB.NET . Also I have done couple of projects in ASP.net. 4 Oracle: It was my ...

Open import_database.dat and change the path to dmp file. Save it and run it! C:\import_database.bat sqlplus sys/sys as sysdba @C:\SqlRefresh.sql imp m1/m1@m1 fromuser=m1 touser=m1 ignore=y file=c:\cat.DMP C:\SqlRefresh.sql connect sys/sys as sysdba; drop user m1 cascade; create user m1 identified by m1; grant dba to m1; exit; Working: import_database.bat logs user in as sys and deletes user m1 so that his database is deleted along with him. Then it creates the same user and grants him dba privileges. All this is done in file SqlRefresh.sql. Next we import the new dump with the help of imp command.

When your KRA* is not defined, you had to suffer a lot of things like Documentation, testing and training the users on field (Why would a dev would want and need to go to field??? God knows!!! ). Well, unfortunately when your 90% of time is spent in these activities you actually can't complain!!! *KRA: KRA means Key Responsibility Area, these are the responsibilities that form the core of your work and define your role in the organization.

So another week past and another period of time is committed to history. I have learnt a few things. First is however prepared you may be sometimes you just fall on your face and you can't do anything about it. Second thing was you can try your best and still you may not be able to stop yourself from falling on your face when the situation is just so. I was on field enjoying a paid vacation in the middle of nowhere and things crapped a bit to conspire the falling on the face. There was only one positive thing about this, the screw up was not at my end and whatever didn't work, I didn't have anything to do with it. Some people would call it saving own skin but I don't think so. In fact because of this thing only I was able to enjoy the time. Thankfully I had internet access via the trusty old GPRS. It wasn't fantastic but it did crawl along. And the ample amount of songs on this phone and my adorable Zen Mozaic kept me entertained. The games on this phone also ...

Having a smartphone and using it regularly as a Smart phone for about a month now, I have come to some conclusions. 1. A smart phone needs Internet. Without Internet it's maybe only 30% smart. 2. Also we each have our specified tasks and we need Apps for that. Without appropriate Apps the smart phone loses its usability. 3. Ease of use is another parameter which determines the usability of a smart phone. If all functions are easily accessible and easily manipulated then the user can exploit it fully. 4. The UI performance is also another important factor and it influences the usability greatly. Fluid animations and clear interface contribute to greater user experience.

1. Chart necessities     When you start with existing code then usually it's well bloated. There are half formed, half-implemented ideas, constructs remaining from discarded ideas as well as code that's lying in comments. We need to remove all of this and add new code so that the new software ends up being slicker and easier to manage than old software. Code management is a complex job, and it's almost akin to file management on your personal computer or Laptop. Often you horde up files and what not together and when you start on cleaning you come to understad that half of the stuff is junk. So is with code. In any application which doesn't have quality people looking after it, there's a lot of junk code lying around. It's often in the form of unimplemented ideas coded partially which end up in comments. Or structures that are not used anywhere. Or header files that are not included anywhere. 2. Start with barebone infracture     We start with an empty project...

I really wish every Sunday was like this. Actually I have taken a break from the Internet, just visit the net to check out the mails on Gmail and check out the 2-3 websites that I frequent for news. Well anyway as for the Sunday, I woke up at right time in the morning, had my favorite breakfast then some work followed by lunch with my favorite veggies. After couple hours of sleep and an evening stroll ending with a glass of cold coffee. Then some more work and now dinner - that was probably the best egg biryani I've eaten till date. Just wish I had someone to share this with, but no worry. That problem will be solved in due time. Anyway so here ends the Sunday and maybe it wasn't that interesting for you but the good part is the one coming below. So windows phone! For a guy who's been messing with Linux since his late teens, ending up with windows phone is a surprise. Well how I did end up with the Samsung Omnia W is not what I'm going to talk about now. We are g...