Much like Git Workflows, the process to manage your git commits also has a bearing on your team's productivity. What works for one team in one company may not work just as well for other teams or companies. Here's an approach that works best for us.

We all know what favorites are. It lets us find what we are looking for quickly. But, they are often not context-sensitive. This is where our "Relations" feature makes a huge impact. You can create contextual references to your content. Look at them as "scoped" bookmarks.

And even for the rest of us who don't always prefer a Kanban View for everything, there are some scenarios in which we definitely look forward to using Kanban Views.

If you have never created a Facebook Campaign before, and are just getting started, it may take a tiny bit of getting used to. Here's how I went about creating my campaigns for our SaaS platform (snowpal.com).

Besides the obvious differences, there are a few reasons why I prefer one over the other, entirely driven by the nature of the problem I am trying to solve.

As we all know, git is a piece of wonder. But, it still takes a little bit of time to arrive at the workflow that works best for you (given that it depends on a variety of factors). Here's one that works for us.

Snowpal Pitch is a powerful SaaS platform that lets you stay organized in all walks of life. Here's a quick 1-minute video on one of the many features (the first one you would encounter after you sign in - "Dashboard").

This is in context of a number of Tamil Short Films I've watched recently. It kindled my curiosity that they offered a "variety" of thanks at the beginning, and I wanted to find out the difference between all of them. I don't think I found the real answer but that didn't stop me from speculating :)

If you want to add or improve your logging or caching layers, you definitely want to consider doing them using Aspect Programming. Those are some common examples but there are numerous scenarios where touching your "core" coding layers (or, tiers or services) is not a good idea. Aspects come in quite handy on those occasions.

To make the best use of your time at work, and/or when you are in front of a machine, it is a good idea to come up with a design (no matter how high level) in mind. This way, you can hit the ground running when you get to your machine. I've seen time and again that this approach works for me.