Run a second instance of Skype on a Mac

I'm in a process of moving from Windows 8 to a Mac. On my Windows box I run both a personal and work instance of Skype. To have both running on Windows just execute the command "Skype /secondary" and you're done. As it turns out, on a Mac it's not much more difficult. The "secondary" option does not exist; however, there is still a nice way to solve this. Simply run "sudo /Applications/Skype.app/Contents/MacOS/Skype &" in a Mac Terminal (if your Skype is installed in /Applications).

However, if you want a nice application icon in your /Applications or your Dock, you'll have to create a Mac package. It's quite simple, but to save you some time, check out this package in GitHub: https://github.com/vcollak/SkypeSecondaryMac

Building mobile apps - build once, run (almost) anywhere

For those of you who are interested in mobile application development, I would highly encourage taking a look at Sencha. I spent the last two days at their SenchaCon annual developer’s conference and cannot resist being completely impressed by their products as well as people.
During the conference they introduced several updates to their current frameworks including Ext JS, Sencha Touch, and Designer. They also introduced a new cloud offering called Sencha.IO. However, while Ext JS is a great framework and Sencha.IO is a very interesting new cloud offering, the real story here is Sencha Touch.

As everyone knows, mobile development market is fairly defragmented. To build mobile applications for leading platforms such as iOS, Android, and BlackBerry, developers need to build the same application in completely different frameworks and languages. To support all three, developers must literally write the application three times. What a waste of time. To solve this issue, one can use a third party framework. Several months ago I evaluated three leading JavaScript frameworks including Appcelerator , JQuery Mobile  and Sencha Touch . To create complex mobile apps quickly and with the least amount of pain, Sencha Touch was hands down a winner. While the other two have a potential, Appcelerator was simply too buggy and JQuery Mobile while easy to use resulted in UI differences between platforms. What looked great on an iPhone was terrible on Android when built by jQuery. Sencha Touch does not suffer from these limitations. While its learning curve is much steeper than jQuery, I feel that benefits outweigh the downsides.

As a result, Ignite standardized on Sencha Touch and we are building mobile applications in that framework now. Our own findings as well discussions I had with people around SenchaCon reveal that Sencha Touch really is a great framework. As the same time, when building large mobile applications not everything can be solved with it.  For instance, because the framework leverages Webkit browser on the device, developers may need to use something like PhoneGap to access native APIs such as camera, contacts, geolocation and others. Also, some of the developers talked about leveraging PhoneGap to improve speed of the application and moved some of the business logic to it. One other exciting product in their mobile ecosystem is the Sencha Designer. In 2.0 developers be able to build mobile apps using their UI builder. What takes us hours now can take us minutes. The resulting code will be MVC. Something we are very excited about, of course. To be honest it’s not all roses even with Sencha. Multi-platform mobile development is tough and many developers have to deal with workarounds just to support multiple devices within the same app. However, I think Sencha Touch is clearly a leader in this space.

Organizational star performers

Interesting research covered on an HBR podcast:

• It seems to be more productive to develop star performers internally compared to hiring them from the outside. This is because outside stars leave behind them a support structure, which they need to develop at the new pace. It often takes up to 5 years for stars to become productive again. (Vlad: Hmm, I am sure one's mileage varies here, but I guess the point is that star performers are not immediately as productive at the new place as they were at the old.)
• Star performers are less likely to leave employment. In fact, the turnover of stars is half the rate of non stars
• People don't leave companies, they leave managers. If companies change management, expect some turnover
• Stars are less likely to leave if there are other stars around

Generation X and workplace

Interesting podcast about Generation X and their struggle to find their place in corporations. As the podcast explains, Gen Xers grew up in an environment full of corporate layoffs, which caused them to be "light on their feet" so to speak and much more opened to options than other generations. They are entrepreneurial, fed up with Boomers not getting of their way and worried about the new cool Gen Y.

How to kill a great idea

Interesting story about Jonathan Abrams - the inventor of Friendster and how he "created the first online social network and enlisted Silicon Valley's best and brightest to run it. Yet Friendster flamed out spectacularly. What went wrong?"
Link to the article

Ranking Ideas

How many times have you hard someone say: “That’s a great idea. You could make a lot of money with this.” Or on a flip side, I am sure you’ve heard someone say: “That idea is not worth a thing.” Well, how do you know if an idea is worth it? I guess great entrepreneurs just know it in their gut. Well, I am not there yet so if nothing else, I would like to use some kind of a checklist to rank my ideas and then go after the ones that have the most promise. When I listened to the below podcast, I realized that’s exactly what I've been looking for. Here are some notes pretty much verbatim from the podcast. For those who would like to know more, the podcast is called Killer Innovations by Phil McKinney (www.techtrend.com/blog/podcast.xml ).

In this episode Phil asks a fundamental question - how does one choose the best idea among many ideas? The answer is that one needs to answer yes to at least one of these three questions.

1. Does the idea improve the customer expectation or experience?
   1. How? Provide details.
   2. Can you measure the improvement experience? 2 times better? 5 times better?
   3. Will the customer value it? Will they pay premium for it? 

1. Does the idea improve the competitive landscape?
   1. How will the idea reshape the competitive landscape?
   2. What will the competitors do? How will they react?
   3. Does the idea create a sustainable competitive barrier?
   4. What is the current market value chain? Now, how does this idea change the value chain? 

1. Does the idea fundamentally change the structure of the industry?
   1. Can the ecosystem partners play in this new value chain?
   2. Can the existing or new players benefit from the new value chain?

If you cannot answer yes to one of these three questions, the idea is a waste of time. But we are not done yet. Other questions to ask are:

1. Can you actually turn the idea into reality?
2. Do you have expertise and capabilities?
3. Do you have the right knowledge?
4. Do you have a contribution to make?
5. Can the idea generate enough margin?
6. What is the total addressable market that you can go after?
7. Can you price the product to create enough margin? A rule of thumb is that you add up a total R&D cost of a product. Look at the total margin the product can generate. Depending on the industry the new idea should generate 5-10 times the R&D cost at minimum. Some industries are 20,30, even more times the cost.
8. Is there enough sizzle? Can we create the sizzle through a model or a prototype?
9. Will the senior management support it? Can this idea get funded?
10. Can we access the customers’ preferred channel?

Now, for each new idea at the top of your list, rank the ideas based on the above criteria. The results give you the best ideas.

Three Signs of a Miserable job

Patrick Lencioni's latest book discusses the topic of job satisfaction. A summary of this book and an interview with the author can be found on HBR's podcast. According to the author,the key factors for job satisfaction and thus performance are:

Anonymity- Employees are often miserable in their jobs because of anonymity. Quite simply, employees feel that they are transparent and unimportant. If they don't feel a personal connection, if they feel that their managers do not take a personal interest in them, they often do not like their jobs.

Relevance - Employees need to feel their jobs are relevant. If they don't feel they can positively impact others, or that their jobs have some meaning, they are often miserable.

Imeasurement - One's job performance needs to be measurable. Employees need to have some way for them to assess their own performance. In such case they are not dependent on a whim of a manager relative to performance appraisal. This is why salespeople are often happy in their jobs. It is because they have measurable evidence of their performance - sales.