One segment I have been absolutely upbeat is IT/Tech. Tech has always been the hidden moat for many companies - AP/BFL to name a few. Tech is no longer a vertical in market. It has become horizontal that cuts across every single vertical.
More from Ameya
Almost every 6 year, Chennai Petro falls to 80 odd level, rises to 460-480 and falls again to touch same level. It happened in 2009, happened in 2015, 2020 it just reversed from 80 and result also to assist!! Can we see cycle playing out again?
— Ameya (@Finstor85) July 25, 2020
This is line chart based arc I plotted a few days ago to see where does the target of 2nd arc completes. We got ~9200(+/- 100/-) Switch to candles. See rejection area. Arc on candles is not really ideal but on line it is. No view above 9200! MAs need to catch up. #TATAELXSI pic.twitter.com/WNJRZZedrj
— Ameya (@Finstor85) March 30, 2022
So I have been studying this entire communication layer as its relevance is ever growing with more devices coming online, staying connected, and relying on real-time communication. Not that this domain under penetrated, but there is a change underway.
— Ameya (@Finstor85) February 10, 2021
This thread is inspired by one of the articles I read on the-ken about #postman API & how they are transforming & expediting software product delivery & consumption, leading to enhanced developer productivity.
We all know that #Twilio offers host of APIs that can be readily used for faster integration by anyone who wants to have communication capabilities. Before we move ahead, let's get a few things cleared out.
Can anyone build the programming capability to process payments or communication capabilities? Yes, but will they, the answer is NO. Companies prefer to consume APIs offered by likes of #Stripe #twilio #Shopify #razorpay etc.
This offers two benefits - faster time to market, of course that means no need to re-invent the wheel + not worrying of compliance around payment process or communication regulations. This makes entire ecosystem extremely agile
More from Tech
There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.
You’re allowed to think about a desired outcome from the beginning.
It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.
It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.
It’s not BDUF if you help every team member know what success looks like.
Agile is about reducing risk.
It’s not Agile if you increase risk by starting your sprints with complete ignorance.
It’s not Agile if you don’t research.
Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.
It would be a mistake to assume this research should only be done by designers and researchers.
Product management and developers also need to be out with the team, conducting the research.
Shared Understanding is the key objective
I\u2019d recommend that the devs participate directly in the research.
— Jared Spool (@jmspool) November 18, 2018
If the devs go into the first sprint with a thorough understanding of the user\u2019s problems, they are far more likely to solve it well.
Big Design Up Front is a thing to avoid.
Defining all the functionality before coding is BDUF.
Drawing every screen and every pixel is BDUF.
Promising functionality (or delivery dates) to customers before development starts is BDUF.
These things shouldn’t happen in Agile.
You May Also Like
Curated the best tweets from the best traders who are exceptional at managing strangles.
• Positional Strangles
• Intraday Strangles
• Position Sizing
• How to do Adjustments
• Plenty of Examples
• When to avoid
• Exit Criteria
How to sell Strangles in weekly expiry as explained by boss himself. @Mitesh_Engr
• When to sell
• How to do Adjustments
• Exit
1. Let's start option selling learning.
— Mitesh Patel (@Mitesh_Engr) February 10, 2019
Strangle selling. ( I am doing mostly in weekly Bank Nifty)
When to sell? When VIX is below 15
Assume spot is at 27500
Sell 27100 PE & 27900 CE
say premium for both 50-50
If bank nifty will move in narrow range u will get profit from both.
Beautiful explanation on positional option selling by @Mitesh_Engr
Sir on how to sell low premium strangles yourself without paying anyone. This is a free mini course in
Few are selling 20-25 Rs positional option selling course.
— Mitesh Patel (@Mitesh_Engr) November 3, 2019
Nothing big deal in that.
For selling weekly option just identify last week low and high.
Now from that low and high keep 1-1.5% distance from strike.
And sell option on both side.
1/n
1st Live example of managing a strangle by Mitesh Sir. @Mitesh_Engr
• Sold Strangles 20% cap used
• Added 20% cap more when in profit
• Booked profitable leg and rolled up
• Kept rolling up profitable leg
• Booked loss in calls
• Sold only
Sold 29200 put and 30500 call
— Mitesh Patel (@Mitesh_Engr) April 12, 2019
Used 20% capital@44 each
2nd example by @Mitesh_Engr Sir on converting a directional trade into strangles. Option Sellers can use this for consistent profit.
• Identified a reversal and sold puts
• Puts decayed a lot
• When achieved 2% profit through puts then sold
Already giving more than 2% return in a week. Now I will prefer to sell 32500 call at 74 to make it strangle in equal ratio.
— Mitesh Patel (@Mitesh_Engr) February 7, 2020
To all. This is free learning for you. How to play option to make consistent return.
Stay tuned and learn it here free of cost. https://t.co/7J7LC86oW0
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.