Getting started with Polymer

In my interest to understand the material design concepts I was trying to put my hands on to it and working with it. Here are my initial challenges in doing so also this post would be useful for beginners and Web designers to understand the skills required.

Best way to get started is to have to go through the youtube videos available on search on the youtube for Google I/O 2014 material design or Google Design channel.  You will be able to get very intriguing insights on why we should adopt such material design concepts.

When I try to work on it I want to hit the ground very fast I was following Polymer Getting started guide . You need to heavily depend upon two things for get things going one is nodejs and another is git.

It uses packages like Bower, Gulp, etc., for you to use the Polymer start kit which will help you start with an App with ease. Make sure you know how to setup environment variables and stuff like that. If you have sublime editor to edit the files its easy you can get the app going within an hour without much hassles.

My quick result on localhost with gulp serve:

Material Design Approach

Give a try and give your feedback. 🙂


When Continous integeration is most needed?

Do we need to adopt continuous integration everywhere when we do development ? or Where its most applicable? This post is an attempt to find a answer to that question.

According to ThoughtWorks “Continuous integration is a development practice that helps developers to adopt several check-ins to the code they have developed multiple times in a day”. 3 important benefits stated for Continuous integration:

  1. Help detect defects and  remove them early
  2. Avoid last minutes integration failures
  3. Eliminate waiting time to check if your code will work post-integration without any problems

Now coming back to the question, following could be the reasons:

  1. Whenever you are into agile projects features has to be delivered at ease and fast.
  2. When there are distributed teams involved in development
  3. Multiple components are to be integrated to  a single product or solution
  4. Whenever there is need to build the entire source whenever someone check-in the code
  5. Provides transparency across developers on the build process and its outcomes. Helps to improve the overall ability to fix issues as it occurs.

Top 5 reasons to adopt cloud strategy

You have developed innovative products for Client/Server or Platform Specific. Still not moved to cloud ? There are very high chances that you are already silo’ed in the market out or your product is still  going strong with existing market. Must you can find the top 5 reasons why your product development must adopt cloud strategy.

1. Product to suit ubiquitous computing

The product development can be made to suit different devices and still can tap wide market. Makes selling easier.

2. Quicker upgrades to product

Same set of features available to all the customer on single deployment. Means less support headaches.

3. Staying ahead with technology

Since the product is on cloud, you are forced to stay ahead or in alignment with technology. Less technical debt.

4. Scale as your customers grow

No upfront investments. Scale the product and its capability as your grow. Growth at will. Dev ops will help.

5. Make money based on want and needs

Modular your product and deploy in cloud. Give what the customers want not what you have. More ways to make money.