If your suggestions keep getting ignored by product or ops, you're probably explaining code instead of explaining outcomes. Learned this the hard way, worth learning early.
Consistency beats intensity, most of the time. I've kept the same routine for years instead of burning out every quarter chasing extra hours. Boring works.
Not spending 100% of what I earn. Not saving 100% either. Found a balance that lets me live well now and still plan for later. Extremes make for good posts, not good decisions.
Half the 'senior mobile engineer' interviews I've seen focus entirely on widget trivia. The actual job is architecture, security, and knowing when NOT to add a dependency.
Every mobile engineer has a horror story about a state bug that only shows up on real devices, never emulators. Mine cost three days and one very confused stakeholder demo.
Excel told me where my money went. Kharch just made it painless to actually log it. Sometimes the win isn't a new insight - it's removing the friction to get one.
https://t.co/bMSWCgtcqE