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?

I would recommend chur chur naan to all 🤌

IT WORKED. Can't believe I'm using Minimax M3 in Codex App for free

exploring Indiranagar

Daily water filling ritual at the office...

The Fifa 2026 theme is grooving dude....

Tweeting from office

VCT LONDON WATCH PARTY IS GOING CRAZY...

I wonder where I got this laptop from... what you guys think?

Be the Answer. Rank Across Google & AI. "SEOitis" is live SEO is no longer just about ranking on Google. ChatGPT, Claude, Gemini, Perplexity, and Grok are answering your customers questions - with or without you. We built SEOitis to fix that. > Track how AI engines talk about your brand > Find the gaps > Research, write, and publish - one pipeline 🔗 seoitis.com/

good night chat

my goals for the month of June - grow on X by posting my day to day stuff - connect with more real people

the more time you spend learning, the harder it gets to get a job.

Don't waste 1-1.5y on learning in 2026

90% people don't take action, just because of the fear they carry everywhere.

𝗜 𝘁𝗵𝗼𝘂𝗴𝗵𝘁 𝗺𝗼𝘃𝗶𝗻𝗴 𝘁𝗼 𝗺𝘂𝗹𝘁𝗶-𝘂𝘀𝗲𝗿 𝘀𝘂𝗽𝗽𝗼𝗿𝘁 𝗼𝗻 𝗺𝘆 𝗮𝗽𝗽 𝘄𝗼𝘂𝗹𝗱 𝗷𝘂𝘀𝘁 𝗺𝗲𝗮𝗻 𝗮𝗱𝗱𝗶𝗻𝗴 𝗮𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻. 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.