When making a strategic cloud decision, organizations can follow either one of two ideologies: open or closed.

In the past, major software technologies have been widely accepted because an emerging market leader simplified the initial adoption.  After a technology comes of age, the industry spawns open alternatives that provide choice and flexibility, and the result is an open alternative that quickly gains traction and most often outstrips the capabilities of its proprietary predecessor.

After an organization invests significantly in a technology, the complexity and effort required steering a given workload onto a new system or platform is, in most cases, significant. Switching outlays, shifting to updated or new software/hardware platforms, and the accompanying risks may lead to the ubiquitousness of large, monolithic and complex ERP systems – reason not being that they offer the best value for an organization, but rather because shifting to anything else is simply – unthinkable.

There’s no denying that these are critical considerations today since a substantial number of organizations are making their first jump into the cloud and making preparations for the upsetting shift in how IT is delivered to both internal and external clientele. Early adopters are aware of the fact that the innovation brought about by open technologies can bring dramatic change, and hence are realizing how crucial it is to be able to chart their own destiny.

One of the biggest challenges faced by senior IT professionals in organizations is the choice of the right software vendor. In the highly competitive enterprise software industry, there are lot of vendors who claim to offer the best software for the problem and it can be really daunting to narrow down the best choice. Additionally, enterprise software costs can often run into millions of dollars thereby leaving very little margin of error. The real cost of choosing a wrong software can often result into losses much more than the cost of the software itself as highlighted by software disasters experienced by leading companies like HP, Nike etc. In such a scenario, senior IT professionals despite years of expertise can find it very difficult to choose the right business software vendor for their organization.

Here are some of the proven ways of short-listing and selecting the right business software vendor for your organization,

·         Understand and Define The Exact Need First: Before embarking on a journey to select the software vendor, it is critical to understand and define the exact problem you want the software to solve. The paramount question to be asked is what business objective does the software need to solve. Is the software required to “reduce costs” or is it to “improve productivity”? Extracting and defining this fundamental question is the bare minimum but necessary step to go searching for the right vendor. It will then form the basis of comparing multiple vendors on this very need that your organization has and will help drive the selection process going forward. The detailed approach involves creating a set of parameters that the software needs to meet in order to be considered. In fact, consider categorizing these parameters further in “must-haves”, “good to have” etc. which will help you assign relevant weights to these parameter and how the software’s fare on each of these parameters

·         Building The List of Vendors Who Meet The Need: Once you have defined your need and distilled that need into various parameters, it’s time to built the list of vendors who you think will meet the need. This is akin to a lead generation model wherein you want to identify a large enough pool and then filters your list down to the best ones. There are multiple ways of building a list of vendors and more often than not, you must use a combination of these methods to build a good enough list.

o   Use Industry Reports: We discussed the IT intelligence offered by leading industry firms Gartner and Forrester in How To Keep On Top Of Latest Trends In Information Technology. These firms based on their access to leading software vendors and CIO network publish vendor comparison research reports across specific verticals as well as specific technologies. Gartner’s Magic Quadrant and Forrester’s Wave are a very good starting point to get an insight into the best software vendors. For example, if you were looking for a CRM solution, you could look for Gartner’s Magic Quadrant for CRM and look at the vendors that make the list. These reports can be pricey but well worth the money if you are going to invest hundreds of thousands in the software. Having said that, you don’t have to trust these report blindly because how these firms define the best software may not match how you define the best software for your organization

o   Competitive Intelligence: If you are a smart professional, you are already keeping tabs of your competition. Chances are that if you are a big organization, you might see a Press Release either from your competitor or their vendor announcing the implementation of new software. Extrapolate that across 5-10 key competitors of yours and you might discover the vendors that your competitors are choosing. This gives you a good indicator that the vendors used by your competitors must be offering something right.

In the ever changing landscape of software programming, it is not surprising that developers and employees have a different set of preferences for desired skills.  However the number one language that developers want to learn according to a survey of developers by technical recruiter, Hacker Rank is Python. This is not a surprise considering that Python has been in demand for several years and programmers tend to really enjoy this language for clear syntax, good OOP support and great shortcuts. Python, named “the language of the year” in 2007 and 2010 in the TIOBE Index and has climbed to #4 status in May of 2018.

According to the study, employers want developers who:

-  Have problem-solving skills, such as the ability to break down large, complex problems.
- Are proficient in their programming language and debugging.
- Can design systems.
- Can optimize performance.
- Have experience in reviewing and testing code.
- Are proficient in database design

Surprisingly, formal education is not the deciding factor when it comes to what companies care about the most. People with computer degrees or certifications on a resume are not necessarily a first choice for hiring managers. Others that have years of experience even if those individuals are partially self-taught in the field stand to be taken seriously in the field.   For those individuals with a passion to learn and master a skill, there are ample opportunities with smaller to mid-sized companies.

Some interesting FAQ’s from the study:

    On average, developers know 4 languages, and they aspire to learn 4 more.
    Younger developers between 18 and 24 plan to learn 6 languages.
    Folks older than 35 only plan to learn and additional 3 languages.
    The top languages developers said they will learn were, Go, Python, Scala, Kotlin, and Ruby.
    There is a large gap between employers seeking developers that know React than there are folks that can do it.

So, Why Learn Python?
It is now the most popular introductory teaching language in U.S. universities.  Python is easy to use, powerful, and versatile, making it a great choice for beginners and experts alike. It allows you to think like a programmer and not waste time understanding difficult syntax that other programming languages can command. And, because of its rapid growth, many developers contribute to the Python community and share Python libraries making creativity that much more a reality

Jeff Nelson, a former Googler and inventor of Chromebook says on Quora, “One habit I've clung to is writing small prototypes when I'm trying to learn new concepts.
For example, I'll sit down with a book or a web page, and over the course of a few hours, write 30 or 40 programs all of them only a few dozen lines long.  Each program intended to demonstrate some simple concept. This prototyping makes it very easy to try out many concepts in a short period of time.”

Miguel Paraz, Software Engineering Student habit is to “keep a log in a text file or document on my work computer. Before trying to solve a problem, I write it down first. And then I describe the details as they happen.”