“Hello world” Coder

Anwesha Sanyal
3 min readApr 13, 2021

Whoever plans to get started with coding, the first step is to choose a preferred programming language. Now, one has n number of options to opt for one, like c++, python, java even HTML(it’s hyper text though), and whatnot. The most amazing part of any of the programming journey is one always initiates with a program that prints “hello world”. It can just be a 2–5 line code depending upon languages but I just wonder how amazingly it initiates a journey.

So when you’re writing a “hello world” program, it’s quite obvious that you’re not a professional one. Within the past few months, even I’ve started my coding journey, and as well as I’ve seen a few people get started with coding. I enjoy it so much when they post their first step to this journey. It feels like they’ve got some next-level energy and swag as if they have started to talk to the computers and all.

At the very beginning of this journey one keeps wandering how to learn and apply those things as it includes problem solving skill. So it’s quite easy to get overwhelmed when one is just a beginner. I remember when I was learning C, my teacher introduced the word “algorithm” to me. That sounded pretty cool. Then I was asked to write an algorithm to add 2 numbers. I was like “what to write in it? just add! what more?” Sir laughed at first. next he replied, “don’t you think you need numbers to add? then only you’ll sum those up and print right?” Honestly a mind that solves calculus problems and deals with mechanics and gravitation was unable to cut down the problems into such small steps. I guess most of the beginners face this thing(or i don’t know if I’m the only one).

As one gets started with writing the first “Hello World” program for the very first time, one checks whether everything is properly written or not and then hit to compile. Another portion that was till then just a theoretical concept for the coder comes to be real. Error! (that’s the nightmare as well as love for each and every coder) In most of the cases it’s that semicolon or that return 0 statement. Then the next phase comes in, debugging. Initialily it starts with that one semicolon but the reach of it becomes higher day by day. It’s not impossible to have 40 errors in 20 lines of code. One of the craziest thought is, thinking “my system has crashed” while unfortunately running an infinite loop in turbo C++ or any other like that.

It’s amazing to move just a step forward to this phase but these days can make you laugh at any point of time. Seeing those tiny texts on screen at least one of the friends exclaims “Are you a hacker?” but you’re just trying to create a calculator. Isn’t that fun?

As the time goes on we land from tackling syntax errors to debug more and more logical ones. Before compiling we pray that we encounter small number of logical errors. From that if-else to ds-algo things get complexer and we head towards being a programmer from “hello-world coder”. But all the fellow future coders keep learning and moving forward and keep that “hello world coder” in yourself always. It’s that highly enthusiastic part of you that will help you to grow more. So Happy coding :)….

--

--

Anwesha Sanyal

Hey, a astrophile and currently a bibliophile girl this side! I'm recently working on web development and competitive coding. I love to sketch my words.