Skip to main content

Current and fake IT position presented by employees

Today post will not be about a technical problem or technology. It will be about IT people and their fake positions (the ones that are presented by them)
More and more often I see a lot of discrepancies between the real passion of a person in a company and the one that they share on LinkedIn, different events and meetings or on mail signature.
Before going deeper let’s see some example:

Current position | “Dream (fake) position”
Junior Developer | Software Consultant
Junior Developer | Solution Provider
Software Developer | Team Lead
Software Developer | Software Architect
Senior Developer | Technical Lead
Senior Developer | Project Manager

This are only a small part of the fake positions that I discover in the last 2-3 months. The list could continue, but you got the idea.
From my perspective, lying in your business card is a pretty big problem, which shows to me how reliable and honest is that person. For this kind of persons, the position is the most important thing for them and usually this dream is destroyed when you start to talk with them and you realize that they don’t have the knowledge and seniority level from their “business card”.
It is good to have a dream, but you need to work to reach it.
Why all of this is so important?
Because when a client see in specific position of a person, they expect to get a person at the level, not a ‘fake copy’. For example if you present yourself as a Team Lead and you start to discuss with clients about how you need kick off a project and organize the team, it is pretty clear that the client will be disappointed. He will realize that you are a junior and have the sensation that the company is selling untrained people.
Another example is when a junior say that he is a technical consultant, but without knowledge related to this position. The client end up with the same image: people from that company are not well train, WTF.

As we already saw, the biggest problem will not be on the people themselves. The company image will suffer. And because we live in a small world, you can imagine how fast other companies will know about that. The funny part of this story is that the company itself was no fault. This was made without
their knowledge or agreement.

Is better to have an extremely good junior than a mediocre (moron) senior in the end.


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.