Search This Blog

Pages

Posts

I attended a couple of interviews during my
5+ year career and and the experience of my friends circle, especially for getting the first opportunity in the UK and came across various types of interviews. Based on
that limited knowledge I can categorize the interviewers into 4 categories 1-
Technically
well sounded interviewer 2-
Interviewer
who has taken a list of questions and asking only those questions 3- Interviewer
have no idea about technology they are recruiting for but know about the kind
of business the company is doing 4-
An
interviewer who speaks more about the problems they faced with during the ex-
colleagues Category-1 technically well soundedinterviewer I came across
25-30%of technically sounded interviewers. They had clear idea about what they
are recruiting for. Manipulating such an interviewer is a big issue. For all
interviews basic thing we need to keep is try to be honest for 100% . But in
front of a technically sounded person and who know what he is doin…

There are lots ways available to write the secure Mvc application. In my experience I came across lots of secure application in public facing. I want to tell about some of the mechanism I followed.
1- encrypting the URL Parameters and preserving id's encrypted on the client side
1- I always make sure if I pass Id or any sensitive data into the view always make sure it's encrypted. By doing so make sure if we forced to use HTML.hidden or HTML.hidden for have the encrypted values, in action link if I pass any parameters from the client side (eg:- edit or create or navigating between different actions we can make sure that all the values are encrypted)
During the design of the actions results if it's http get I usually encrypt the sensitive data
[httpget]
Public actionresult display()
{
TestModel testModel=new TestModel();
testModel.id= encrypt(id);
Return View(testModel);
}
[httppost]
Public ActionResult Display(string id)
{
Guid d_id= new Guid(decrypt(id));
// do operati…

Last 2 months I was not updating my blog because I was busy with some interesting opportunities in my career. Today I am writing this blog on the eve of a project release. Even though I have been involved in a lot of projects for more than 4 years, this is the project that went through all the process estimation, planning, design, implementation, uat and release happened as perfectly as planned. So I thought of sharing my wonderful experience with all my readers.
This is the project my organization decided to outsource. But I am showing in my interest to manage this project to our commercial director. Finally lots of management level meeting finally it came to me, but with strict deadlines. On August first week commercial director given green signal for this project and given a business analyst to discuss the business needs. Myself will manage the project in terms of the technical side and the product side business analyst will help to get the requirement. I already worked with this…

Recently read about agile manifesto. So thought to sharing it. More stories can be found at the agile manifest website, that is at the end.

1-Our highest priority is to
satisfy the customer
through early and continuous delivery
of valuable software. 2-Welcome changing requirements,
even late in
development. Agile processes harness change for
the customer's competitive advantage. 3-Deliver working software
frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale. 4-Business
people and developers must work
together daily throughout the project. 5-Build
projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done. 6-The most
efficient and effective method of
conveying information to and within a development
team is face-to-face conversation. 7-Working
software is the primary measure of progress. 8-Agile
processes promote sustainable development. The sponsors, developers, and …

Most of the small or medium IT firms are using the Entity framework for the Data Access layer (DAL). If we write a complex linq to Entity queries performance will always be an issue. But with the Compiled Query Performance can be improved. This below definitions are from MSDN and more details can be found on the MSDN Link that is at the end of this post

When
you have an application that executes structurally similar queries many times
in the Entity Framework, you can frequently increase performance by compiling
the query one time and executing it several times with different parameters.
For example, an application might have to retrieve all the QuoteRevision for a
particular quotelineStatus, the quotelinestatus is specified at runtime. LINQ
to Entities supports using compiled queries for this purpose.

The compiled query class
provides compilation and caching of queries for reuse.
Conceptually, this class contains aCompiledQuery'sCompilemethod with several ove…

It interview structure- a review
Interview is a process to select the right candidates for the right positions. The reason for this article is the way nowadays interviews are arranged by some IT related companies in London. Usually there are different levels of screening now companies are putting to select the right candidates. First round will be a cv screening round, followed by a telephonic interview ( mainly telling as technical discussion). If you pass all this round you will be selected for a face to face interview. Most companies follows one or more face to face interview and interaction session with the co- workers. If you are successful on all this rounds then only you will be offered the job.
Especially in London a lot opportunities are available and can find a lot competitive candidates from different countries. So the level of competition are very high on this cosmopolitan city. All this above interview round should guarantee a right candidate? Or a person with raw tal…

More than last 12 months I am a great sponsor of the test driven development. But how i become a great devotee of TDD is very much interesting. I was given task to restructure the existing system. This is one of the most important features in our system. When i seen the existing code it was in a malicious situation. Lots of unwanted, complex complicated loops. So before starting the reconstructing the whole team sit together and decided we are going to start something new. It might slow down the process initially but will produce the quality work. Before witting the method we identified the feature's specification and requirements and exception handling phases. Thentest cases are written based on the requirement. Then started working on the methods based on the test cases. First the entire test will fail because the method is written afterward. Test method example publicvoid MethodWeAretesting_DescriptionOfInput_ReturnValueAndExpectedBehavior(){// Prepare test environment (i.e.: cr…

About Me

Born and brought up in a small village in Trivandrum District Kerala, India. After My Schooling (10 STD) thought of finishing my studies (Because fed up with studies) .After One year my dad bring me back to college for Pre-Degree (A-Level). Then I did B.Tech Computer Science and Engineering from Mount Zion College of Engineering Kerala. During the final semesters (2005) one thought came to my mind want to do higher studies abroad. So I left India (Going first time out of my state Kerala) for my Masters degree in Jan 10, 2006.I started MS in 2006 January 17 at Staffordshire University. In 2007 September 5, I was awarded with MS degree.
For all these things, I am thankful to my father (He was a teacher by profession). I can blindly tell one thing his foresight is leading my life.
I love you - dad and mom, my ever sweet sis and loving wife bhagi