Software Engineer II (Frontend) @Uber | Views my own & not of my employer

Bengaluru
Joined December 2013
I am genuinely stunned that hardly anyone has shown any intent to protest against the flawed reservation system or even raise their voice against it. Unfortunately, there’s no funding for such causes. I am all for reservation based on financial need, to help people uplift themselves. But reservation for people living in bungalows? 🤦🏼‍♂️
308
1,321
110
9,483
226,638
– at Murudeshwara, India
1
48
🧵 How DISCOM negligence is hurting PM Surya Ghar Yojana consumers
1
32
PM Surya Ghar Yojana will succeed only if - Net metering is configured on time - Export and import data is verified - Billing corrections are automatic - DISCOMs are accountable Otherwise rooftop solar adoption will slow down.
1
32
This is not about one bill. It is about governance accountability and system readiness. DISCOM reforms are essential for energy transition credibility. @mvvnlbudaun @CMOfficeUP @myogioffice @PMOIndia @UPPCLLKO @MinOfPower
18
The skill that compounds in the AI era isn’t prompting. It’s knowing what not to build.
31
AI reduces effort. It doesn’t reduce responsibility. If anything, you need stronger judgment because mistakes are easier to produce.
28
AI is great at generating answers. It’s not great at: • asking clarifying questions • understanding business constraints • predicting long-term impact That part is still our job.
27
The biggest candidate mistake I notice: Trying to prove they’re smart instead of trying to understand the problem. Interviews reward collaboration, not just performance.
32
Most interviews are really testing how you think when you’re uncertain.
21
My debugging got faster when I stopped reading code first and started reproducing the issue carefully. Understanding the conditions is usually harder than fixing the bug.
26
Biggest resume mistake I made while preparing for interviews: I described technology. Interviewers cared about impact.
38
Frontend habits that reduced my bugs significantly: • debug with breakpoints, not guesses • keep state close to the component that uses it • name things so comments become unnecessary Most issues were architecture, not logic.
34
Most interview prep advice focuses on adding skills. My progress accelerated when I did the opposite: I reduced surface area and went deep enough to defend every decision I wrote on my resume.
2
1
52
Also, interviewers rarely care about how many technologies you know in most cases. They care whether you understand consequences of using them.
36