#JUBLFOOD
Broadening trendlines along with price volume action towards the upside.

Above the price band of 3810-3830; Longs can be placed for a target of 3900 followed by 3980.

#StockMarket #StocksInFocus

THE BATTLE OF SARAIGHAT (1671)

Lachit Borphukan's humiliation of Aurangzeb.

The battle of Saraighat was a naval engagement fought on the Brahmaputra river near Saraighat between the M0ghul empire and Ahom kingdom in 1671.

Guts, resolve and glory!

(Elaborate thread)

Koch was a state situated between the dominions of M0ghuls and Ahoms. For Ahoms, it was a buffer state for keeping M0ghul territorial expansions at bay.(1)

Times changed when the ruler of the Koch kingdom, Nara Narayana passed away in 1587 resulting in Koch being divided into 2. Western Koch was ruled by his son Lakshmi Narayan and the eastern Koch by his nephew, Raghudev.(2)

Lakshmi Narayan formed an alliance with M0ghuls after which he attacked Parikshit, son of Raghudev, in 1602. Parikshit Narayan was defeated while his brother Bali Narayan took refuge in the Ahom Kingdom.(3)

The M0ghuls used it as a pretext to invade Ahom kingdom. The first battle between them took place in 1615 leading to a series of engagements in which both sides had their shares of ups and downs resulting in a stalemate.(4)

Remembering Colonel Anil Kaul, VrC (Retd) on his 3rd Death Anniversary.

“It was October 12, 1987, exactly 5:55 pm as I was… coming out of the cupola of my T-72 tank on a steamy evening in an unknown place called Kokkuvil in the Jaffna district of Northern Sri Lanka.+

I froze in that confined space at what I saw. An LTTE militant stood at 60 meters aiming his rocket-propelled gun at my tank.

In a flash he fired. Probably having lost his nerve he aimed too low. The projectile hit the left mudguard of the tank, but for some inexplicable reason+

did not explode. It then hit the side of the main gun and then exploded on top of the turret, all in a fraction of a second. Before I knew, it seemed I had received a straight right punch so to say to my chin. I saw some blood appear on my left hand and there was a sharp drop in+

my eyesight.

Lt Colonel (now Lt Gen) Dalbir Singh, then Commanding Officer of 10 Para Commando, who was standing on the engine deck said to me, “Yaar what a close shave.”

He suddenly saw me and the look on his face told me that something was very very wrong with me. In that+

fraction of a second, as if it was a rewind of my entire life, thoughts raced through my life as to how and when I had landed myself in such a situation…

I asked my gunner to pull out a first field dressing (FFD) which is standard equipment in a first aid box carried in each+

💬 I often get Q’s like these:

How did you get your first customers for WIP? How did you grow BetaList’s traffic? Etc.

Makers are looking to reverse-engineer success. I see it everywhere.

I don’t think it works that way and the answers to those questions are mostly useless. 💥

I have built dozens of different products over the last couple of years. The vast majority failed. 😭

Surely if I know the answers to these questions, but still fail over and over again, these answers aren’t that useful. 🤷‍♀️

So what’s a better question to ask? 🤔

99.9% of the questions I receive are about the products that did well. In a way that makes sense, because we quickly forget about those that didn’t succeed.

🧠 This is known as survivorship bias.

Focusing on what survived, while ignoring what made it survive in the first place.

The real question, what you really want to know, is this:

What makes @WIP, @BetaList, and to some extent @AllStartupJobs succeed where my countless other attempts failed?

What separates a failed product 👎 from a successful product 👍?

Honestly, I don’t know. I wish I did.

It’s like Steve Jobs said “I’ll know it when I see it.” 👀

Same is true when we make products. We don’t know upfront what will work. But once we see an inkling of a product that does have potential, it’s not that hard to spot.

💬 I often get Q’s like these:

How did you get your first customers for WIP? How did you grow BetaList’s traffic? Etc.

Makers are looking to reverse-engineer success. I see it everywhere.

I don’t think it works that way and the answers to those questions are mostly useless. 💥

I have built dozens of different products over the last couple of years. The vast majority failed. 😭

Surely if I know the answers to these questions, but still fail over and over again, these answers aren’t that useful. 🤷‍♀️

So what’s a better question to ask? 🤔

99.9% of the questions I receive are about the products that did well. In a way that makes sense, because we quickly forget about those that didn’t succeed.

🧠 This is known as survivorship bias.

Focusing on what survived, while ignoring what made it survive in the first place.

The real question, what you really want to know, is this:

What makes @WIP, @BetaList, and to some extent @AllStartupJobs succeed where my countless other attempts failed?

What separates a failed product 👎 from a successful product 👍?

Honestly, I don’t know. I wish I did.

It’s like Steve Jobs said “I’ll know it when I see it.” 👀

Same is true when we make products. We don’t know upfront what will work. But once we see an inkling of a product that does have potential, it’s not that hard to spot.

A thing which I unironically and enthusiastically believe which is unpopular among smart people of my acquaintance: financial engineering has in the recent past and present contributed substantially to human welfare. We should hope to see more of it.

Maybe more geeks need to meet someone who says “My job is teleporting value across time and space.”

Financial engineering is sort of a squishy term. I don’t primarily mean payments infrastructure or financial rails, although both of those involve substantial engineering.

I mean more “We took a thing and performed some alchemy, and now have a new thing.”

Except instead of alchemy it is generally quite a bit of math, a huge amount of contract law and due diligence, often an impressive amount of ops work, and a dusting of technology that web devs would recognize as such.