Skip to main content

The right programing language ?

This question is frequently asked by the guys that start diving in the programming world.
And the answer to it is the same as the answer of the many other questions that contain “Which is the right … “.

         It depends on what you want to achieve!

It is absolutely true answer – everything depends on the goals.
But the thing that always is important is the communication language.
Yes, team working is communication. No matter how good are the developers, they can’t do big thing alone - they need work in team and one team is good when the communication language is right.
And I don’t write this hoping some of my managers will read it  – no. I have tested it by myself.

Good communication with the colleagues and perfect English are the most important in the daily team work. Speaking, writing email, discussing approaches or giving suggestions for something – it's all communication.
And I’ll give you two real examples that make me really believe that perfect English is one of the most important thing.

The words “hesitate” and “guys” change the way I’m writing emails.

This week my colleague who is also a project manager on the SharePoint projects has a day off. On the next day when he back, he came to me and asked – Why have you written this ?
                       !!!????? No idea what he was talking about !
And he showed me my email masterpiece. The previous day, I had sent email to our scrum master (who is also our SharePoint consultant )  asking him for some information and I had written:

        " ... Can we get from the gays in the  XXX (one department)  the information about …"

Until this moment, I have never known that gay and guy are different words – really, I don’t know this. I didn’t believe I had written something wrong and after I checked in Google Translator the difference between gay and guy I understood what I have done.
Fortunately, the man in Norway  has seen this and forward only my questions on the guys in this department, so nothing happen.

I have also had similar situation when I worked in Telerik.
As a junior developer, main part of my job was to be a support on one web control. In an email to our customer I have forgot one word in the pattern for replaying and thanks to the man who approved the tickets, my version of the mail didn’t reach the customers.

The word “hesitated” was some how difficult to me and I always leave the difficult words in my email for the end – when I reread the email and fix the mistakes.Very very bad approached.  I have written:


     Thank you for contacting us.

          ( some explanation of the issue )

     If you have any question or need further assistance, don’t      contact me again.

     Best wishes,

So my opinion is that the perfect communication language is the best programming language.



Popular posts from this blog

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed.
The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before.
There is a new control called ClientPeoplePicker.

How to use it:
1.Add this references

<%@RegisterTagPrefix="wssawc"Namespace="Microsoft.SharePoint.WebControls"Assembly="Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>
2.Add the following control declaration

      <wssawc:ClientPeoplePicker Required="true" ValidationEnabled="true" ID="peoplePicker" runat="server" InitialHelpText="<%$Resources:wss,aclinv_PickerIntialHelperText%>" VisibleSuggestions="3" Rows="1" AllowMultipleEntities="false" CssClass

The column name that you entered is already in use or reserved. Choose another name.

The problem: 
You want to create column with a specific name in SharePoint but SharePoint gives you the message "The column name that you entered is already in use or reserved. Choose another name."

Why this is a problem?
Because you need to create custom columns and content types using the default SharePoint interface.
And the business users have to see properly named columns - for example "Description", not "My Description".

It is important to know something technical about SharePoint (versions Office 365, 2013, 2010):
 - it supports columns with same Display Names.
 - you can’t have columns with same Internal names

Let’s implement the following common scenario:
You are creating a SharePoint customization and you need the following column:
   Type: Multiple lines of text
   Internal Name: MyProjectDescription
   Display Name: Description

 Here is the correct way to achieve it:
1. Create the column MyProjectDescription.
This will create column with I…

Office 365 Migration API: how to migrate the taxonomy metadata

If you wander whether the Office 365 Migration API supports migration of taxonomy metadata, the answer is YES. The API supports it but there isn't good documentation about how to modify your xml files after the command ConvertTo-SPOMigrationTargetedPackage.

In this post, I'm going to show you the approach. I assume that you have base knowledge of how to use the Migration API.

The scenario I'm going to use is simple - migrate single Document library with single document.
The document has one taxonomy column (MyTaxonomy) and three versions:

Here are the steps:

Step 1: Export the document library

Export-SPWeb "" ` -ItemUrl "/Shared Documents" ` -Path "\\cos-dev-03\export1\Export" ` -NoFileCompr -IncludeVersions 4
This command will export the document library and will create the initial package.
The command is not part of the Migration API. It is well know since SharePoint 2010 and is part of the server side obje…