Jack is Here, asp.net findings

If you haven’t read the first part of this blog, please follow this link: https://ivoireconsultancy.org/blogs/ivoire_article_view.php?id=55.

1. Things to specify when submitting your Project?

* Qualifications and knowledge Be careful here- There is a tendency to think that the higher the level of academic qualification the better, but often knowledge may be more important. Other sorts of training maybe more relevant for a specific job than a degree. It is important to think about just what is necessary and what is desirable in order to do the job.

* Specific competences, skills, abilities Here you need to specify accurately (and quantify if you can) those factors that are necessary for the successful completion of your project. For example, ‘I need a Freelancer with the ability to communicate in English as well as French- A freelance web designer, programmer with some knowledge of php, java scripts, and able to work under pressure….’

*Experience Carefully specify necessary prior experience and the content within this needs to have been gained, can reduced the number of unsuitable applicants. It is important to think about what experience is necessary for success in this particular project. For example, ‘I need a freelance writer with 5 years of work experience in the outsourcing world….’

2. Interviewing Freelancers

* Base your questions on the job requirements * Ask exactly the same questions of each candidate * Avoid asking for opinions, goals and self-evaluations * Rate each answer in the interview and evaluate several scales at the end of each interview

It is important to understand that the interview has the following advantages: * explain the work of your organization * to offer the applicant an opportunity to explore any doubt or uncertainty * Set up the expectations of both parties, including any discussion of potential difficulties in reality * for candidates, in order to to assess whether they want to be the kinds of work * to start building the relationship between the buyer and freelance translators

* Some examples of questions, what was your most satisfying experience of working on your first project as a freelancer? * What did you achieve it explicitly? * Me about a time when you had a project have been completed within a short time. What have you done? * What was the most difficult project that you had been performed in the past? * Me about a project you recently completed. How did you hear that? * How much time do you spend thinking about a task before starting work?

You are not required to ask the same questions of all of them at the same time. However, we believe that these sample interview questions would help you in your selection process.

3. Steps for dealing with underperformance or misunderstanding

*Identify and agree on the problem with the Freelancer

The reason for the poor (in seconds) to establish a *. How buyers, understanding, attitudes, or there is a reason to support freelancers from inadequate capacity and lack of skills or the stem of the problem is?

*Decide and agree on the action required: for example providing more guidance to the Freelancer and allocate more resources if necessary

*Record agreement on steps to be taken

*Monitor and provide feedback.

4. Why is it important to build a long-term relationship with a Service Provider? Reducing the number of Service Providers enables the Buyer to devote much more time and effort to developing relationship with the remaining. So hiring the same Freelancer time and time again could be beneficial for the Buyer in the long term. Buyers can involve Service Providers in planning for the future, enabling Freelancers to invest and build their own capabilities to meet future requirements Service Providers can be involved in new service/product design and development of the Buyer.

Following these simple steps will make your outsourcing experience very pleasant.

I was really surprised when I heard some people saying

?

Fortunately, just a few days later, I have to believe that some people know the job of model enthusiasts. Have a great technical knowledge, they think of the patterns and fingertip writer's name. People, you can speak technobabble for a few hours, but a few days. First of all, I admire them, and knowledgeable people who find their own.

?

Then I found something strange, in addition to all their knowledge they had very few successes and their managememt was not satisfied with their problem solving skills.

?

I had begun to observe the causes of their failure. Mean while I had an architecture for a future enterprise project design. I started by improving and optimizing scaffolding my legacy libraries and frameworks with my team. I asked the people to review my approach to my approach to foolproof.

?

Geeks love technology, so I get a prompt response, and they began to emphasize the weaknesses, I was very happy when I got a chance to improve. But unexpectedly, most of the problems identified are as follows:

?

Geeks: Aren’t you using NHibernate?

?

Me: Nope, I preferred these liberaries because these are recommended by technology vendor and I found them performent for this kind of data driven applications. Another reason is our management don’t want to use NHibernate because we haven’t developed enough experties to use it in an enterprise project that’s why we had faces some serious issues in the last project using NHibernate.

?

Geek: What? Do you know where NHibernate came from, it’s a port of Hibernate, being used in the most powerful language Java. It has nothing to compete with Microsoft.

?

Me: Yes, I accept that all types of controls, and platforms are much more mature, but any language or technology to their own specifications and has some advantages. Our liberaries framework and are optimized with the objects provided. Net. Our wrapper classes to use some new skills in the current version of the. NET.

?

Don’t use ADO objects

?

These objects are mess.

?

Me: Why?

?

Geeks: Because these are not open-sourced

?

Me: I admire the benefits of open source but these object are rich, free, built-in, tested and performing well in enterprise applications. I do not very often use them but I found them very useful in such kind of applications

?

Geeks: You incorrectly applied this pattern; let me show you the documentation.

?

Me: This pattern like other patterns have different applications, I am following this approach because it performs well in this scenario. This flexibility is also allowed by some experts.

?

Geek: No, patterns should be followed as is. They are not to be changed for performance or whatever. And remember enterprise applications, built on great technologies like EJB, looks graceful even if they are not enough performant.

?

Geek: Increase your number of layers like we have did in that application. You have not decoupled enough.

?

Me: Yes previously I do have the same number of layers but I found it as an overkill so I modified this framework for medium-sized performance-hungry applications.

?

Geek: And why did you coupled these two major tiers, this is an unacceptable violation of N-Tier Architecture

?

Me: No, these are still two different layers, but I am keeping them in a single project during development as most of the developers are working on both layers. They still can be deployed on different servers.

?

Geek: I’m still not satisfied, it is not recommended by our gurus and we follow them because we know they are the best.

?

Me: They might have recommended it for some different type of project and this approach may be suitable in that particular scenario.

?

Geek: We found their practices the best in all type and size of projects, whatever, it’s not that simple you think it is, you have to add a lot more.

… And finally, I got the answer to my question

?

?