My goals for 2026 are -
> Getting a job as a full stack + ai developer, preferably hybrid.
> Gifting myself a new bike.
> Gifting myself an iPhone.
> 10k+ followers on Twitter.
> Being mentally and physically healthy.
Today is 22nd December 2025, 11 14 PM.
What about you?
my goals for the month of June
- grow my X account to 3k
- share/ distribute the Practa growth marketer challenge
- connect with more girl founders
what are your goals?
๐ ๐๐ต๐ผ๐๐ด๐ต๐ ๐บ๐ผ๐๐ถ๐ป๐ด ๐๐ผ ๐บ๐๐น๐๐ถ-๐๐๐ฒ๐ฟ ๐๐๐ฝ๐ฝ๐ผ๐ฟ๐ ๐ผ๐ป ๐บ๐ ๐ฎ๐ฝ๐ฝ ๐๐ผ๐๐น๐ฑ ๐ท๐๐๐ ๐บ๐ฒ๐ฎ๐ป ๐ฎ๐ฑ๐ฑ๐ถ๐ป๐ด ๐ฎ๐๐๐ต๐ฒ๐ป๐๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป.
Turns out the real challenge was migrating existing production data safely.
My app already had:
โข rewards
โข tasks
โข transactions
โฆbut all of them were modelled to support a single user.
The problem:
I couldnโt lose or break existing data while introducing users.
So hereโs the migration strategy I used:
1. Added a ๐๐๐ฒ๐ฟ๐ table
2. Added nullable ๐๐๐ฒ๐ฟ_๐ถ๐ฑ fields to:
โข rewards
โข tasks
โข transactions
3. Created a system user
4. Wrote a migration script to connect all existing records to that system user
5. Verified relationships and data integrity
6. Only then changed ๐๐๐ฒ๐ฟ_๐ถ๐ฑ from optional -> required
Mistakes I avoided:
โข Making ๐๐๐ฒ๐ฟ_๐ถ๐ฑ required immediately
โข Writing destructive migrations
โข Breaking existing production records
โข Assuming auth alone solves multi-user architecture
This was one of those features that looked simple from the UI side but completely changed the backend architecture.
If you found this useful:
Follow me on ๐ซ - https://t.co/qUlTM5NhtQ
Connect on ๐๐ถ๐ป๐ธ๐ฒ๐ฑ๐๐ป - https://t.co/9Omqj3THIG
Explore my work on ๐๐ถ๐๐๐๐ฏ - https://t.co/OaUA2XIqL6
๐ ๐๐ต๐ผ๐๐ด๐ต๐ ๐บ๐ผ๐๐ถ๐ป๐ด ๐๐ผ ๐บ๐๐น๐๐ถ-๐๐๐ฒ๐ฟ ๐๐๐ฝ๐ฝ๐ผ๐ฟ๐ ๐ผ๐ป ๐บ๐ ๐ฎ๐ฝ๐ฝ ๐๐ผ๐๐น๐ฑ ๐ท๐๐๐ ๐บ๐ฒ๐ฎ๐ป ๐ฎ๐ฑ๐ฑ๐ถ๐ป๐ด ๐ฎ๐๐๐ต๐ฒ๐ป๐๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป.
Turns out the real challenge was migrating existing production data safely.
My app already had:
โข rewards
โข tasks
โข transactions
โฆbut all of them were modelled to support a single user.
The problem:
I couldnโt lose or break existing data while introducing users.
So hereโs the migration strategy I used:
1. Added a ๐๐๐ฒ๐ฟ๐ table
2. Added nullable ๐๐๐ฒ๐ฟ_๐ถ๐ฑ fields to:
โข rewards
โข tasks
โข transactions
3. Created a system user
4. Wrote a migration script to connect all existing records to that system user
5. Verified relationships and data integrity
6. Only then changed ๐๐๐ฒ๐ฟ_๐ถ๐ฑ from optional -> required
Mistakes I avoided:
โข Making ๐๐๐ฒ๐ฟ_๐ถ๐ฑ required immediately
โข Writing destructive migrations
โข Breaking existing production records
โข Assuming auth alone solves multi-user architecture
This was one of those features that looked simple from the UI side but completely changed the backend architecture.
Kirat said shoot your shot. So I did.
Guess I'll never be ready, but that shouldn't stop me.
Time is your scarcest resource.
Opportunity cost >>>>>
Normal People by Sally Rooney.
Beautiful character writing, Story feels more natural and real.
Overall I would give this book 7.8 out of 10...
Looking forward to Intermezzo and Conversations with Friends by the author.
Inaam got an upgrade,
new colour theme,
better components and there consistency,
small bugs and fixes...
looks really better now, looking forward to few other feature such as "bonus points, how to handle repetitive tasks"