We have been chosen by AlwaysOn as one of the AlwaysOn Global 250 winners. Inclusion in the AlwaysOn Global 250 signifies leadership amongst its peers and game-changing approaches and technologies that are likely to disrupt existing markets and entrenched players.
Here is the press release: 500friends Selected by AlwaysOn as an AlwaysOn Global 250 Winner.
A full list of all the AlwaysOn Global 250 winners can be found on the AlwaysOn website:
2012 AlwaysOn Global 250 Top Private Companies.
We are using git-flow for our source code branch management model. If you are not familiar with git-flow, Why aren’t you using git-flow? article provides a nice overview.
Many git users may be familiar with the git merge vs git rebase debate. In essence:
- Merge is simple to use and works great. It creates however lots of merge commits especially when working with a larger team.
- Rebase keeps commit history linear and clean. It is however harder to use and can be potentially destructive.
git merge vs git rebase: Avoiding Rebase Hell article provides a great comparison of both techniques.
The way to get the best of both worlds is to be explicit about when to use one versus the other. For us the simple rules to follow are:
- Rebase feature branches.
- Never rebase develop or master branch. (Always merge into develop and master.)
- Never rebase public branches.
To implement the rules we made a small change to the standard git-flow process:
When implementing enhancements or fixes always start by creating a feature branch:
git flow feature start foo
When done with work:
- pull develop branch from github
- rebase feature branch on top of develop
git rebase develop feature/foo
- finish feature branch
git flow feature finish foo
- push develop to github
To get more details on using rebase with feature branches please go to The magical (and not harmful) rebase article.
With this simple process change, git commit history is easier to follow while risks of making a mistake are kept at bay.
Visitors come from all corners of the world. The top 5 countries are:
- USA – 32% of visitors
- India – 12%
- UK – 6%
- Germany – 4%
- Canada – 4%
I put together a catalog of the key tools we are using:
What tools are you using?
Article first published as And the most in-demand tech skills of 2012 are … on VentureBeat.
One way to find out is by looking at the job posts. I decided to analyze recent craigslist San Francisco Bay Area job ads. It is a good proxy for the local demand. Bay Area is often a trend setter, and technologies which become popular here frequently gain broader adoption. The findings can therefore also be viewed as a leading indicator for other geographies.
Here are the key insights:
- “Mobile” appears in 30% of all ads winning popularity (or hype?) contest.
- Java continues to lead the pack among the development languages followed by Ruby, Python and PHP.
- MySQL is by far the most commonly mentioned relational database.
- NoSQL is featured prominently. Hadoop is first on the list of NoSQL databases followed by Cassandra, Redis and MongoDB.
- Linux has little contest among the operating systems. Ubuntu is mentioned more frequently than CentOS.
- Android is mentioned slightly more often than iOS/iPhone.
- Spring continues to be the most commonly mentioned Java framework.
- git outranks subversion among the source code management systems.
- Selenium is the most frequently mentioned testing tool.
- Drupal is the most often mentioned CMS tool.
I run similar analysis a year ago. For the most part results were similar. There are a few notable differences:
- Demand for mobile skills is accelerating. “Mobile” and “social” had similar mention frequency last year. This year “mobile” mentions are far ahead of “social”.
- NoSQL skills requests increased significantly.
- PHP mentions went down, Ruby went up.
- git overtook subversion.
- Flash/ActionScript mentions went down.
List of the top 50 skills most commonly featured in the job ads is shown below.
Fig 1. Top 50 Technical Skills in Demand
- I run a term frequency analysis on job posts which appeared on craigslist in the SF Bay Area Internet Engineering category between 1st and 31st of January 2012.
- Count reflects number of posts a term appears in. Multiple mentions of the same term in a single post count as one.
Here is Always On announcement:
And here is more information: