u/Neat_Dragonfruit6792

Rishta issue: Cousin sister earns well, guys don't even earn half. Need advice

Salam everyone. Wanted some genuine advice on a situation our family is dealing with regarding my cousin sister's marriage.
Her family is settled outside Kashmir in a big metro city. She’s at the age where we are looking for rishtas, and obviously, the preference is strictly a Koshur groom. The "problem" is that she is doing really well in her career and makes around 1.5 to 2 Lakhs a month.
Finding a guy from Kashmir who makes even half of that has been pretty much impossible. We understand that the local economy and job market back home are completely different compared to tier-1 cities, but it's causing a lot of stress for her parents right now.
They are really worried about her financial security. Plus, let's be real, knowing how our society and traditional mindsets usually work, if the wife is out-earning the husband by double or triple, it almost always leads to ego clashes, taunts, or weird dynamics later on. We really don't want her to end up in a toxic situation.
Has anyone dealt with something like this with their own sisters or cousins? How do families usually navigate this? Should we just limit our search to guys who are also working outside in metros or abroad? Or are guys actually becoming more open-minded about their wives earning way more than them?
Would really appreciate any honest thoughts or similar experiences. Thanks.

reddit.com
u/Neat_Dragonfruit6792 — 3 days ago
▲ 1 r/developersDesi+1 crossposts

Does switching from C++ to Python for DSA look like taking the "easy way out" to FAANG recruiters?

Hi everyone,
I’m currently a CSE student (graduating in 2029) and I am trying to lock in my strategy for internship prep.
Right now, I am learning DSA and building my foundation in C++. However, the syntax can be incredibly heavy when I'm just trying to focus on core logic and problem-solving. I recently received advice from a senior to just switch to Python—they mentioned the cleaner syntax makes interview rounds much easier and that it has massive industry demand anyway.
The switch is definitely tempting, but I have no idea how this actually looks to recruiters and hiring managers.
My biggest fear is that I have a bad habit of jumping from one shiny object to another. I’ve already bounced around a bit between full-stack web dev, different tools, and now C++. I'm worried that dropping C++ for Python right now is just me running away from hard concepts instead of finally building discipline.
My questions for the recruiters and engineers here:

  1. What do FAANG/top-tier companies actually expect from freshers? Does the language I use for OA's and interviews matter to you?
  2. Is it better to just suffer through C++ to build a hardcore, low-level logic foundation, or is Python completely fine (and maybe even optimal) for passing the bar and landing internships in the current market?
    Any harsh truths or industry insights would be really appreciated. Thanks!
reddit.com
u/Neat_Dragonfruit6792 — 3 days ago

I’ve been stuck in "Tutorial Hell" for weeks. Today, I finally wrote a working C++ program completely from scratch. Here is the one rule that fixed my brain.

I need to share this because I have been feeling incredibly stupid lately, and I know I’m not the only one.
For the past few weeks, I’ve been trapped in the classic Tutorial Loop. I would watch a video on for loops or if statements, nod along, and think, "Yep, makes total sense." But the exact second I closed the video and opened a blank VS Code file to solve a problem... my brain would just flatline.
I couldn't even translate basic math into code. For example, today I was trying to write a simple function to find the sum of all even numbers up to n. Instead of checking if my loop counter i was even, I wrote if (sum % 2 == 0). I was checking the total instead of the number in my hand. I stared at the screen for an hour, totally lost in a sea of curly brackets, having no idea why my code was broken.
Then, I tried a new rule today: Do not touch the keyboard.
Instead of trying to type C++ immediately, I forced myself to use a 3-step method:

  1. The Human Translation (Pen & Paper): I wrote out exactly what I would do if I had physical numbers on a table. ("I will look at numbers 1 through 10. If the number divides by 2 cleanly, I throw it in a bucket.")
  2. The Blueprint (Pseudo-code): I translated the human words into programming tools on paper. ("Need a for loop for the counting. Need an if bouncer with % 2 == 0. Need sum += i for the bucket.")
  3. The Execution: Only then did I open my IDE and type the syntax.
    It felt like literal magic. Because I wasn't trying to solve the logic and remember the C++ syntax at the same exact time, the code just flowed out. I finally understood the difference between a variable scanning the numbers and a variable storing the answer. I finally understood why return is mandatory before the closing bracket.
    It was my first real "Aha!" moment where I felt like an actual programmer, not just a typist copying a YouTube video.
reddit.com
u/Neat_Dragonfruit6792 — 3 days ago
▲ 3 r/developersDesi+6 crossposts

I’ve been stuck in "Tutorial Hell" for weeks. Today, I finally wrote a working C++ program completely from scratch. Here is the one rule that fixed my brain.

I need to share this because I have been feeling incredibly stupid lately, and I know I’m not the only one.
For the past few weeks, I’ve been trapped in the classic Tutorial Loop. I would watch a video on for loops or if statements, nod along, and think, "Yep, makes total sense." But the exact second I closed the video and opened a blank VS Code file to solve a problem... my brain would just flatline.
I couldn't even translate basic math into code. For example, today I was trying to write a simple function to find the sum of all even numbers up to n. Instead of checking if my loop counter i was even, I wrote if (sum % 2 == 0). I was checking the total instead of the number in my hand. I stared at the screen for an hour, totally lost in a sea of curly brackets, having no idea why my code was broken.
Then, I tried a new rule today: Do not touch the keyboard.
Instead of trying to type C++ immediately, I forced myself to use a 3-step method:

  1. The Human Translation (Pen & Paper): I wrote out exactly what I would do if I had physical numbers on a table. ("I will look at numbers 1 through 10. If the number divides by 2 cleanly, I throw it in a bucket.")
  2. The Blueprint (Pseudo-code): I translated the human words into programming tools on paper. ("Need a for loop for the counting. Need an if bouncer with % 2 == 0. Need sum += i for the bucket.")
  3. The Execution: Only then did I open my IDE and type the syntax.
    It felt like literal magic. Because I wasn't trying to solve the logic and remember the C++ syntax at the same exact time, the code just flowed out. I finally understood the difference between a variable scanning the numbers and a variable storing the answer. I finally understood why return is mandatory before the closing bracket.
    It was my first real "Aha!" moment where I felt like an actual programmer, not just a typist copying a YouTube video.
reddit.com
u/Neat_Dragonfruit6792 — 3 days ago

Stuck in tutorial hell and logic building is killing me. How do I actually get good at this? Need advice.

Hey everyone. Just wanted to vent a bit and ask for some advice from seniors or anyone who has crossed this stage, because I feel incredibly dumb right now.
I recently started learning C++ and I'm currently on loops and basic functions. My biggest issue is that I am completely stuck in the "tutorial trap". I’ll watch a video or read a solution, the logic makes 100% sense to me, I nod along... but the moment I close the tab and stare at a blank IDE, my brain just flatlines.
I struggle hard to translate my thoughts into actual syntax. Like today, I was trying to write a basic "sum of even numbers" function. Instead of checking if my loop counter i was even, I checked if my total sum variable was even (sum % 2 == 0). Small logic traps like that completely derail me. I also constantly get lost in curly brackets or forget how to pass variables back and forth to main().
I had a small breakthrough today when I forced myself to stop typing and just write the exact physical steps on a piece of paper first, before touching C++. It actually worked and I wrote a working code from scratch.
But honestly, the process feels so slow and overwhelming. I look at people grinding graph DP on Leetcode and I can't even fathom getting there.
For the folks here who made it past this phase:

  1. How did you guys truly break out of tutorial hell?
  2. How do you train your brain to build logic for brand new problems without panicking and running to YouTube?
  3. Are there any specific habits I should adopt right now at this beginner stage so I don't get crushed when I start actual DSA?
    Any harsh truths, roadmaps, or advice would be really appreciated. Thanks!
    🙏
reddit.com
u/Neat_Dragonfruit6792 — 3 days ago