My classmates were sending invoices to clients while I was still searching "how to install Python" and reading three contradictory answers.
I am a naval architecture student in Bangladesh, well past my first year of university, and in my first week of coding I could not make a 5-line program run.
Here is my first month, week by week — the error that ate an evening, the first thing that worked, the week I nearly quit, and what week 4 actually looked like.
Week 1: an error message ate my whole evening
My first program was supposed to print a small table of numbers. Five lines. Maybe six.
It printed nothing. Instead: IndentationError: unexpected indent, in red, like the computer was annoyed at me personally.
I fixed what I thought it meant. The error moved. I fixed it again. The error moved again, like it was renting rooms in my code. I spent one full evening — from after dinner until the hostel quieted down — on the spacing of five lines.
The cause, when I finally found it: I had copied the code from a slide, and my editor had mixed spaces and tabs, and some of my own lines started one lonely space further right than their neighbours. Python, it turns out, treats indentation as grammar. A stray space is not a typo to Python. It is a sentence that makes no sense.
Lesson of week 1, learned at full price: the red text is not the enemy. The red text is the only honest feedback in the room, and it tells you the line number if you slow down enough to read it.
Week 2: something finally ran
In week 2 I wrote a tiny grade calculator. You type in marks for your subjects, it prints your average and a rough GPA.
It is, objectively, a calculator wearing a trench coat. Spreadsheets do it better. Nobody would pay one taka for it.
I ran it maybe 30 times anyway. I typed my real marks. I typed imaginary marks. I typed my roommate's marks, with his permission and then — I admit — twice more without asking, to test the maths. It ran. Every time. I had written instructions, and a machine had followed them, and the answers were right.
People who started coding as teenagers probably don't remember this feeling, because theirs happened at fourteen. Mine happened at my hostel desk at midnight, and I can still remember the exact silence after the output printed, before I whooped quietly enough to not wake anyone.
Week 3: the comparison week (the worst one)
Week 3 is when the class group chat turned into a highlight reel.
One classmate posted a payment screenshot from a freelance job. Another was doing small websites for local shops. A third was editing videos for a client abroad. Meanwhile I was stuck on loops — genuinely stuck, the kind where you understand for when you read it and understand nothing when the editor is blank.
I did the maths every beginner does at 1 a.m.: they started at school, I started now, therefore I am four years behind, therefore the race is over, therefore why bother.
I nearly quit that week. Not dramatically. I just "forgot" to open the editor for four days, which is how quitting usually starts — quietly, with good excuses about exams.
What pulled me back was embarrassingly small: the grade calculator. I opened it to add one feature — printing the highest and lowest subject — because leaving it unfinished bothered me more than the group chat did. Forty minutes later the feature worked. The comparison thoughts did not vanish, but they got quieter, the way they do when your hands are busy.
Week 4: boring, and that is the point
No breakthrough happened in week 4. I want to be clear about that, because beginner stories usually smuggle one in here.
What week 4 looked like: 30 to 45 minutes most days, after classes. I finished a small terminal to-do list — add a task, see the list, remove a task. It forgot everything when it closed, because I did not know how to save to a file yet. I wrote my first functions instead of copying the same lines three times. I started a notebook page titled "Errors I Have Already Met," and the IndentationError is entry number one, underlined.
My classmates were still freelancing. I was still a beginner. Both things were true, and somehow both were fine, because I finally had a month of my own evidence instead of a week of their highlights.
The catch: the race was mostly in my head
Here is what I got wrong about the whole month. The classmates I was measuring myself against were not doing one thing called "freelancing" at some senior level. They were doing small, real, scrappy jobs: a shop's landing page, video edits, data entry with extra steps. Good work, honest work — and work that also started somewhere small, usually years earlier, usually badly.
I was comparing my week 3 to their year 3 and calling the difference talent.
The other thing nobody says: starting at university means starting with a reason. I am not learning to code as a hobby that found me at fourteen. I am learning it on purpose, next to a degree, with limited hours — and limited hours force a honesty that unlimited time doesn't. Every session has to count, so most of them do.
Your turn
If you started "late" — after school, at university, after your first job — I want your version of this.
What did your first month honestly look like?
What nearly made you quit?
And what week are you in right now? One number is fine.
Top comments (0)