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.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 http://go.microsoft.com/fwlink/?LinkId=260882 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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…