If you follow ‘Mobile world’ news like I do, you might have already heard about partnership between Nokia and Microsoft, and Google’s trash-talk in response – “Two Turkeys do not make an Eagle”.
Cut to one year back – when android itself was a Turkey, however, they pretty much turned themselves into an Eagle. If you trust in Gartner’s figures, Android market share has risen from 3.5% in 2009 to 17% in 2010 and it is on its way to 22% this year. See - http://www.gartner.com/it/page.jsp?id=1434613 .
Nokia’s Symbian has highest share so far and having seen a world (e.g. India) completely dominated by Nokia phones, I believe they will put up a pretty serious fight for Apple and Google.
What does this mean to us in Insurance industry, who are developing mobile business apps? I think, these developments make a clear case for ‘cross-platform’ development. Rather than, making an application specifically for iPhone or Android, it’s time to seriously consider cross platform development platforms. A hybrid approach with combination of common ‘Portable’ code and some sexier ‘Native’ features appears as a good balance that provides functionality with oomph.
Brain Dump of an Insurance Technologist
Underwriting - The term is derived from Lloyd's of london insurance market, where insurers will literally write their names under the risk information slips. The term indicates careful evaluation and ownership.
Showing posts with label Microsoft Certification. Show all posts
Showing posts with label Microsoft Certification. Show all posts
Monday, February 14, 2011
Wednesday, November 14, 2007
Microsoft Certified Architect - Is it worth it?
Since I pass my MCA certification (solution architect) last year, I keep getting many questions from peers about MCA. Given the cost and efforts involved in getting certified, many wonder if it is worth getting certified.
I think, it definitely is. Here is why -
1) First, it is pretty hard to get through. That is what makes in more valuable. It is recognized highly in the industry. You may be surprise to know how many CIOs are aware of this certification. I am personally benefited from the MCA title at numerous occasions.
2) It is not only the Technology certification. It stresses equally on many other aspects such as Leadership, Communication, Organizational Dynamics, Strategy, and Processes along with technology (breadth and depth). You will not be able to get through if you are too operational OR too hands-off.
(Contrary to popular belief it is nothing to do with Microsoft technology. I presented case study based on J2EE technologies.)
3) It certifies the experience and not the knowledge alone. In the interview, all the questions are targeted for judging what you have done (rather than what you know). The questions are pretty deep. It is almost impossible to bluff in front of 4 experienced senior architects.
4) It is a great experience of going through the certification process - the mentoring, preparations and appearing in front of the board for interviews. You learn a lot in the process. You don't lose much even if you happen to fail.
5) Finally, though it is tough, if you have experience of architecting systems and if you put right efforts preparing your case studies and presentations, it is something achievable. It is definitely worth trying if you want to make career as an architect.
If you are not aware of Microsoft certification process, refer to - http://www.microsoft.com/learning/mcp/architect/solutions/default.mspx
I found a very interesting blog that describes the architecture process in a much lucid way - http://blogs.dirteam.com/blogs/natashamocke/archive/2007/09/02/microsoft-certified-architect-certification-process.aspx
I will be happy to assist if you are preparing for the certification.
I think, it definitely is. Here is why -
1) First, it is pretty hard to get through. That is what makes in more valuable. It is recognized highly in the industry. You may be surprise to know how many CIOs are aware of this certification. I am personally benefited from the MCA title at numerous occasions.
2) It is not only the Technology certification. It stresses equally on many other aspects such as Leadership, Communication, Organizational Dynamics, Strategy, and Processes along with technology (breadth and depth). You will not be able to get through if you are too operational OR too hands-off.
(Contrary to popular belief it is nothing to do with Microsoft technology. I presented case study based on J2EE technologies.)
3) It certifies the experience and not the knowledge alone. In the interview, all the questions are targeted for judging what you have done (rather than what you know). The questions are pretty deep. It is almost impossible to bluff in front of 4 experienced senior architects.
4) It is a great experience of going through the certification process - the mentoring, preparations and appearing in front of the board for interviews. You learn a lot in the process. You don't lose much even if you happen to fail.
5) Finally, though it is tough, if you have experience of architecting systems and if you put right efforts preparing your case studies and presentations, it is something achievable. It is definitely worth trying if you want to make career as an architect.
If you are not aware of Microsoft certification process, refer to - http://www.microsoft.com/learning/mcp/architect/solutions/default.mspx
I found a very interesting blog that describes the architecture process in a much lucid way - http://blogs.dirteam.com/blogs/natashamocke/archive/2007/09/02/microsoft-certified-architect-certification-process.aspx
I will be happy to assist if you are preparing for the certification.
Subscribe to:
Posts (Atom)