First interview of Hiral Chandrana

#MASTEK

Adding 40+ customers every quarter from an year
650+ active clients

Met 150+ customers/partners virtually in last 40days

Focus to accelerate US growth-have strategy in place

960cr cash on books
Looking for organic+inorganic growth

More from Shreenidhi P

Cosmo films
Investor ppt

Splty side:3yr target
Masterbatches-10% rev,20% RoCE
Textile chem-10% rev,25% RoCE
FMCG-Fabricizer launched

30% RoE,22% RoCE-fy21

1% shift in splty adds 5cr EBITDA
Target-62% to 80%

Net d/e 0.5x
D/EBITDA 1x

Petcare-plans 2 demerge in2 seperate entity https://t.co/Iq4VT6tG50

More from Mastek

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

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.