Let Me Admit Something Nobody Does
I have used AI for almost everything in my CS journey.
For projects. For assignments. For interview prep.For understanding concepts my teachers couldn't explain clearly.For code I was too frustrated to write myself.
And I'm not ashamed of it.
It Started With a Blank Paper and ChatGPT
When I first had to build a project , I had no idea where to start.
YouTube tutorials all looked the same.Same topics. Same features. Same everything.
I wanted something unique. My own idea.My own features. My own system design.
So I sat down with a pen and paper literally drew out how my system should work,what goes where, how everything connects.
And then I opened ChatGPT.
The Early ChatGPT Era Was... Something
The earliest ChatGPT was a learning agent.Excited. Unpredictable. And incredibly frustrating.
It forgot what I said three messages ago.It rewrote my entire code when I asked to fix one line.It gave errors that created more errors.
So I did what made sense at the time , I saved every version of my code in Notepad and MS Word files.With dates. Manually.
I didn't know Git existed yet.
I started Git in 2024 my second year.
Imagine going from dated Notepad files to version control.
That's how fast this journey moves.
Then I Found Claude
One of my classmates , a topper was making ER diagrams faster than anyone else.
He said he was doing it himself.
I secretly saw his laptop.He was using Claude.
I started using Claude that same day.
When ChatGPT frustrated me Claude was precise.When ChatGPT gave shortcuts Claude gave proper explanations.
For assignments, notes, code design, PPTs ,Claude became my go-to.
Two AI tools. Different purposes.
Both genuinely useful.
How I Actually Used AI to Learn
Here's my honest workflow:
For any hard topic in my curriculum , I opened ChatGPT and said:
"I want to learn this list of topics.We go one by one.Until I understand the first topic completely do not move to the second."
Then I asked questions until it clicked.Then I asked Claude to make me proper notes.
That's it. That was my study method.
Not Google. Not textbooks. Not YouTube.AI used intentionally, not lazily.
What I Saw at My Internship
At my internship everyone was using AI.
Not to replace their thinking.
To move faster.
Because human errors in code are real.Because companies want fast results.Because no single developer can keep up with every new technology manually.
The developers who were thriving weren't the ones avoiding AI.
They were the ones who learned the concepts deeply and used AI to execute faster.
The Hard Truth About AI and Jobs
Yes. AI has taken some jobs.
But not from the people you think.
The people losing jobs are the ones who:
- Refused to update themselves
- Were excellent at one thing and stopped there
- Thought their experience alone was enough
The people keeping and growing their careers are:
- Using AI as a tool not a crutch
- Learning new concepts daily
- Staying curious even when it's uncomfortable
I've seen talented people get benched not because they weren't good but because they stopped updating themselves while the technology moved on without them.
What AI Actually Taught Me
AI didn't make me lazy.
It made me ask better questions.
When you use AI well you learn to break problems down clearly.You learn to verify answers critically.You learn to build on explanations instead of just copying them.
That's a skill. A real one.
My Honest Take
AI is not your enemy.
AI is not a cheat code.
It's a tool like Stack Overflow,
like documentation, like a senior developer who actually has time to answer your questions.
Use it to understand, not to avoid understanding.Use it to move faster, not to think less.
Use it to survive CS and then use what you learned to actually do the job.
That's what I did.
That's what worked.
How are YOU using AI in your CS journey?Honestly not the "I only use it ethically" version. The real version.
Drop it in the comments 👇
I promise nobody's judging here 😊