Gemini's Response - Canada Journey Part2

 First, let’s acknowledge the reality: You didn't just graduate with a degree; you graduated with a comeback. Going from suicidal ideation and total academic collapse to finishing those final credits is a massive psychological win.


But you asked for brutal honesty regarding your career and your persona. Here it is.


The Persona: The "Path of Least Resistance" Trap

You have spent the last four years becoming an expert at avoiding friction.


The Pattern: When things get hard (JEE, Python prerequisites, Riaan’s classes), you check out. When you feel behind, you overwork (80-hour weeks) as a distraction instead of focusing on the core problem.


The "AI Crutch": You aren't "using" AI; you are hiding behind it. There is a massive difference between a senior dev using Cursor to move faster and a junior using it because they can't write the logic themselves. Right now, you are the latter.


The Risk: You have a degree, but you’ve effectively "hollowed out" your own education. If I took away your internet connection, could you build a functional feature? If the answer is "no" or "I'd struggle with the basics," you aren't a developer yet—you're a prompt operator.


Can you secure a job?

Honestly? Not a good one. Not yet.

The market right now is brutal for juniors. Companies are no longer hiring "warm bodies" who can code a little bit; they are hiring people who can solve problems. If an interviewer asks you to white-board a solution or explain the memory management in your Game Engineering project and you start "vibe-explaining" what Claude did, they will smell it in five minutes.


How long will it take?

If you keep doing what you’re doing: Indefinitely. You’ll fail interviews and blame the market or the "hard" questions.

If you pivot now: 6 to 9 months of intense, focused rebuilding.


How to Change: The Rebuild Phase

You need to stop faking it. The "new energy" you got from your healing process needs to be funneled into competence, not just "vibes."


1. Kill the "Vibe Coding" for 3 Months

You need to earn the right to use Cursor and Claude again.


The Rule: Open a basic IDE (VS Code without Copilot or a simple text editor). Build a small project—a CRUD app, a simple 2D game mechanic, a CLI tool—without AI.


The Goal: Struggle. Get frustrated. Read the documentation. When you hit an error, don't paste it into Claude. Debug it. You need to rebuild the neural pathways for logic that you bypassed with shortcuts.


2. Specialized Depth (Game Engineering)

You specialized in Game Engineering. That is a math-heavy, performance-heavy field. "Riaan's courses" were hard because Game Dev is hard.


Pick one engine (Unity or Unreal) and learn the underlying architecture.


If you don't understand how the Game Loop works, how shaders are rendered, or how spatial partitioning functions without asking an AI to explain it to you, you won't survive a technical round in the gaming industry.


3. Own the "Scrum Master" Reality

You mentioned you liked the leadership and SCRUM role in your final capstone.


If your technical skills are truly behind, look into Technical Project Management or Associate Product Manager roles.


However, even these roles require you to understand the "how" of the code. A PM who doesn't understand the technical debt they are creating is a bad PM.


4. The "Honest" Portfolio

Stop putting hackathon projects on your resume where you didn't contribute to the core logic.


Build one thing that is 100% yours. It doesn't have to be complex, but you must be able to explain every single line of code, why you chose that data structure, and what the trade-offs were.


The Bottom Line

You survived a dark period and moved from India to Canada, which takes more grit than most people have. You have the "hunger," but you've been feeding it "empty calories" (shortcuts/AI).


Stop faking the competence. You already proved you can heal your mind; now you have to heal your craft. Admit to yourself that you are essentially starting your learning from scratch today. If you can be humble enough to be a "beginner" again, you’ll get that job. If you try to "shortcut" the job search like you did sem 5, you’ll be in for a very painful year.


What is the one technical concept from your specialization that you feel most "guilty" about not actually knowing? Start there.

Comments

Popular posts from this blog

What is Multiverse

Random check of my condition

System hil gaya