💯 Stepping up your SIPs is one of the easiest hacks to build a larger corpus. Here's why👇

Intertia or status quo bias is the No.1 enemy of investors. It's human nature to prefer inaction over action.

Given a choice between doing something like starting investing or increasing investments regularly & not doing anything, most investors prefer not doing anything. Inertia is one of the biggest reasons why people delay starting their investing journeys.
The best solution to deal with inertia is to automate your investments, and that's why SIPs work brilliantly. But starting your SIPs is just the start. As your careers progress and your incomes rise, you also need to increase your investments, which most people tend to skip.
And the solution to this is to automate increasing your investments periodically. This is why we have Step-up SIPs on Coin. You can set a predefined %, and your investments will increase every year as you grow😀

Here's how to set up a Step-Up SIP👇

https://t.co/jw7P4mtSLp

More from All

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.