The Big Picture - LIC Lifeline for IDBI

-
RDAI on Friday approved LIC’s plan to buy 51 percent stake in IDBI Bank, as the insurance regulator gave the insurer exemption from the 15 percent investment cap. The Life Insurance Corporation of India is expected to invest Rs 10,000-13,000 crore in tranches in the NPA-mired state-run lender according to media reports.  The insurer will pare its stake in the bank to 15 percent in 5-7 years, according to PTI. The valuation will be decided as per Sebi regulations. Post the deal, the government's stake in the bank will fall below 51 percent. The government currently holds 81 percent stake in the bank and the deal may involve both real estate and non-core entities of IDBI Bank. LIC has a 10.82 percent stake in the state-run lender.


Comments

Post a Comment

Popular posts from this blog

Asking: Advice for a new and inexperienced tech lead?

-
Advice for a new and inexperienced tech lead? Few things I would like to say: It will no longer be about you! It will all be about your team! Make sure you create a great team, nurture them, train them, teach them how to think critically (in doing so yourself). Ask your team to write out everything they plan to do before they actually do it. Reason with them on what they wrote and what approach decisions they plan to take. Teach them to think long term. Writing before actually doing the task helps get a lot of clarity to them and also helps you in assessing what they were planning to build. (It also makes for a great log of what we did and why we did it. This will be the product documentation for your entire product tomorrow.) Treat your team like your family. Do not stress them out with too much work. Be respectful of their time and effort. Give them breaks post completion of major tasks. Every second that you let them rest and breathe is a second you have invested in the f...
Read more

What is the single top-priority software engineering problem?

-
A constantly cycling proliferation of different languages, frameworks, libraries, etc. that all do the same things in a different way and are most often mutually incompatible with each other and have entirely different ecosystems with their own comparative advantages but also major pitfalls. This causes tech workers’ investment in skills to get more out of shallow knowledge and trivia than on deeper concepts, creates silos of employment opportunity based on the trivial knowledge workers have, and hinders the ability for the software engineering field as a whole to have a large pool of shared knowledge and develop and evolve stable, relatively timeless systems and tools of high quality, both as end products and in intermediate tooling toward those ends. I was thinking about the reasons why this happens, and I see two major factors: 1) The tension between abstraction and optimization. To put it shortly, abstraction is about ignoring the details, optimization is about fine-tuning ...
Read more