Skip to main content

Feeling before of a your project to go live

If you are on an Implementation support, the only thing which you want is code freeze, so that you can relax a bit. Thanks to all us for the hard work we had done in last 6 months, we are close to code freeze. We are congratulated by our peers for the effort before Christmas. Although we are also delighted for making such a huge effort, and planned holidays, much deserved holidays after tiring 6 months. Thank God India Australia series is starting after this, else we would have just read the news, now we can be spectators.

Firstly, I like to congrats ourselves for our terrific effort to bring the software on correct path. Hats off to our dedication, peer support and never say die attitude to make this happened. Its not easy without such an effort from the team that bank (NGP) is ready to GO LIVE on the said date. It proves if we work hard then even “Impossible” will say I’M’POSSIBLE. Three cheers to the team. This can only happen due to dedicated effort of team which is short of sleep. Also the peer support was unbelievable, though there are ups and downs in such a big project. But we have to work hard looking forward in the one direction of success.

I have already mentioned that providing a banking solution is too much complicated, as you have to dealt with one basic fundamental. You have to develop a software in such a way that Customer should always feel satisfied in any chance along with your client, i.e. Bank, who wants to earn money through Customer. Also, in the era where technologies are changing to rapidly, that you cannot guarantee that in coming years your product will meet the challenges or the demands of the clients. But still in the current era and with the given system, if you able to deliver a class product within the given time frame is always a plus point, which not only brings your company to the front foot, but also brings your confidence and your career to a fast path.

To be a part of such a project is every newcomers dream in this industry, and I can see myself living my dream. I started my journey with the start of this project in IT sector. From requirement gathering till implementations support, I am part of this project. Its a long way. though I was not part of requirement gathering, but I can see the changes in the functional documents on which this project is driven through. Its just a start of this project. In the mean time, many people left the organization, many new faces joined the organizations, in the midst of all this, this project shaped very well with time, due to the peers sitting over to monitor every activity of their subordinates.
Not only our company is waiting for this project to go live, but other financial world is watching this project closely. I just started my career, so I don't have much idea, how this project is such important. But, after listening to my seniors I can feel that.
Labels:

Comments

Post a Comment

Popular posts from this blog

Bitmap index

Bitmap index is one of the index types that is supported by oracle. Unlike B*tree index, this is very compressed index. It means if I create a bitmap index on a column, then the generated index table will be smaller when compared the index table which is generated by the binary index on the same column. The reason is, in bitmap index, ROWIDs won’t be stored in the index table, instead index values will be mapped against bitmaps. Bitmap is nothing but it stores either of this values, 1(Match) or 0(No Match). For each distinct values in the column, a separate index record will be created. Unlike b*tree index, bitmap index can accept NULL and it creates separate index entry for this. Bitmap index will work better if number of distinct values are relatively less when compared to the total number of records. Why is it referred as “relatively less”? this index will work fine if table of 1,000,000,000 records contains 5000 distinct values and if table of 1,000 records contains 5 distinct va...
Post a Comment
Read more

Nested Loop Natural Join

When the optimizer tries to finalize the execution plan of a query, it considers a lot of items. It must take the interrelated decisions based on those items. Most important of those items are, Ø   Access path Ø   Join Order Ø   Join Operation Access path tells how the required data is going to be retrieved from a table. So, this tells nothing but which index scan is imposed on that table like index range, index skip scan and so on. Join Order means, to execute a query that joins more than two tables, Oracle joins two of the tables, and then joins the resulting row source to the next table. This process is continued until all tables are joined into the result. It means oracle can join only two tables at most in a time though more than two tables are referred in a query. Oracle always tries to join the small tables first and then joins with the large tables. The reason behind is, it always tries to lower the number of resultant records formed while in the process of jo...
Post a Comment
Read more

Hash Outer Join

As per the definition of hash outer join, the driving (or parent) table whose rows are being preserved is used to build the hash table, and the driven (or child) table is used to probe the hash table. To perform this hash outer join, Oracle follows these steps (assume, child table has to be outer-joined with parent table): 1.      Oracle chooses parent table as the hash table (otherwise called as driving table). Oracle built the hash table in RAM after applying the hash function on the joining column(s) of the driving table. 2.      Oracle chooses child table as the probe table (otherwise called as driven table or probing table). It traverse through all the records of this probe table, applies the same hash function on the joining column(s) [column(s) used to join these two tables] and will hit the corresponding entry in the hash table. 3.      Oracle returns the output if a record from the driving table is already present in...
Post a Comment
Read more