Coding is not for the weak. 🤦♂️
It demands a lot from your brain. Attention, patience, logic, all at the same time.
I used to wonder why developers sit in front of their screens for hours, pressing this and that on their keyboards. People calling them "tech bros" and all of that.
But as my training at TechCrush progresses, I'm starting to understand. It's not that they're wasting time. They're doing what is called debugging, hunting down one small thing, hiding somewhere in hundreds of lines of code, that's standing between them and the output they want.
I had my own simpler version of this experience.
I wrote my HTML, linked it to my CSS, gave it instructions, and it refused to respond. VS Code was flagging an error. I kept staring at my screen trying to figure out what was wrong.
Then I found it.
❌ <h3>Greatest of all is God </h3
✅ <h3>Greatest of all is God </h3>
One missing closing bracket. That's all it was. 🤦♂️
And that's not even the only way code decides to misbehave. Incomplete strings will do the same thing:
❌ let message = "God is the greatest;
✅ let message = "God is the greatest";
Notice anything? The closing quotation mark that tells JavaScript "this is a string", nowhere to be found.
Variable declared, but JavaScript is looking at it like, what is this? and refusing to cooperate. Just chaos. 😂
Two small bugs. Whole output – halted.
Humbling. Frustrating. And somehow, still worth it.
Next week we're moving into Arrays, Function Arguments and Objects. Let's see what that brings. 👀
Still learning | Still figuring it out
What is your own version of bugging and debugging experience, dop it in the comment.
#TechCrush #Cohort6 #JavaScript #FrontendDevelopment #NigerianTech #Tech4AfricanScholars #TechJourney
Sometimes terminologies are more harder than question in interviews