Note that this is P2P lending, and thus isn't 100% risk free. But it has been 6 months for me now, no defaults yet, everyday it increases by Rs. 33
I do like the liquidity though - the app allows me to withdraw entire amount (principal + interest) at any time. I have tried doing it with Rs. 1k first and have seen it works before putting Rs. 1L here.
There are very few investment options that have you guarranted 12% XIRR, with daily credits, and is 100% liquid.
Once you join via my link, you can then invite your friends via your own referral link too. That gives you 10% of their earnings (i.e. 1.2% of their principal ๐ค๐ฑ๐คฏ).
If you product is primarily a mobile app, and you care about giving mobile users a great experience - read on
I have been working/consulting on a bunch of mobile apps, some with over 100M users, and I want to talk about lifecycle management, from a product PoV.
A thread ๐งต๐
Let us start with an important fact - most of your power users will be having 12-15 commonly used apps on their phone.
If your users are heavy mobile users, they will have some form of social media addiction - TikTok, Instagra, Snap or Twitter.
The current state of mobile internet users is that they spend a TON of time on their screens, but they switch apps very fast (EXCEPT for the doomscrolling apps).
Understanding state management is definitely like the final boss of the frontend framework game. It is sometimes to hard to wrap your head around, but it need not be.
In Flutter world, I blame BloC to be have made the thing very convoluted for beginners to understand.
Step 1 of understanding state should be to separate state from UI.
Many over-powered state management frameworks have mechanisms of _constructing UI from state_, which is useful for seasoned devs, but hinders beginners from learning what happens under the hood
Frameworks like Vue or Flutter which have internal mechanism of state inside their components/widgets (i.e. the UI primitives), also has a downside. People start off thinking state as a part of UI primitives, which it isn't at all.
There used to be an internet once full of blogs, informative websites, and was true to the premise of internet being a place to search and get to know about anything.
A small cafe owner writing about recipes they experimented with or a woodworker reviewing varnishes..
Today capitalism has killed that internet. Every venture funded company has a marketing department, and the marketing department has 2 departments, one that puts up ads on Google (called performance marketing) and another that writes blog posts (called organic).
Side note: It is extremely ironic that the meaning of the word "organic" is people coming to your website without you paying to do so (i.e. by showing them ads), but today's organic marketing involves paying as much as Google ads to a whole army of "content writers". How organic.
Something common to be found in large Android codebases is dimens.xml file with contents that look like this
This is a major ๐ฉ๐ฉ๐ฉ๐ฉ
It originates from overzealous developers not wanting to *hardcode pixel/dp in layout XMLs*, but it very counterproductive.
We need not be grammar-nazi like in our approach and go for a hard-rule on never to write android:layout_height=12dp kind of code, because from a readability perspective, there is no advantage of turning fig.1 into fig.2
@dimen/_24dp has to be 24dp right? What is the point?
In fact, now we have opened ourselves to a whole different level of subterfuge in the code in the future.
What if, some day, (by mistake, not deliberately), someone changes these values. Perfectly possible under time-constraint, doing last-minute UI fixes.
200 LeetCode questions in 3rd year of college.
FAANG/BigTech job in placements
2 yrs in India, then move to US (sponsored by that BigTech) 7-8 yrs of laid back 5hrs/day work, with 30-40 leaves a year and slowly climb to L5
That's how majority folks turn millionaires by 30
Doesn't sound sexy or cool. Sounds counterintuitive, that if it is that straightforward, then why aren't more people doing it ?
Well if my estimates are correct, every year at least 10000 (probably 20000) Indian techies are doing exactly that.
Don't mistake this as advice to follow this path. (Hell I didn't, myself).
Don't mistake this as an indication of this being "easy" either
Getting into those jobs is not 'easy'. The path is well known and well trodden, but takes time and effort.