Skip to main content

What is coding?

Image
By
The below is a chapter from my second book Learning to code again


I had to explain what coding is to someone in layman terms and this is what the conversation looked like

Me : Coding is speaking to the computer in a language that the computer understands. When we click on the reply button on this forum, there is code that runs that tells the forum software what to do.

Person : So, what exactly is software?

Me (with the help of Bard) : Software is a set of instructions that tells a computer what to do. It is like a recipe that tells the computer how to perform a task. Software is essential for our computers to function, and it helps us to do everything from browsing the internet to playing games to working on our jobs.

Me : We use code and coding to create the software.

Person : So, software is like AI or a form of it?

Me : Yes, AI is a type of software. AI is created with code to mimic human intelligence.

Person : Thank you for answering my questions so thoughtfully.

I asked my friend Bard to help me explain the difference between coding and programming:

Coding and programming are often used interchangeably, but there is a subtle difference between the two terms. Coding is the act of writing code, which is a set of instructions that tells a computer what to do. Coding is the technical skill of writing code in a specific programming language. Programming is the process of designing, writing, and testing code to create a software program. Programming is a broader term that encompasses coding, as well as the other steps involved in creating a software program, such as planning, debugging, and testing. Here are some other terms that are often used in the context of coding and programming:

Software development is the process of creating software programs. Software engineer is a professional who designs, develops, and maintains software programs. Computer Science is the academic discipline that studies the theory, design, and application of computer systems.

Ultimately, the difference between coding and programming is one of scope. Coding is the technical skill of writing code, while programming is the broader process of designing, writing, and testing code to create a software program.

While I will explore many things related to all of these, my focus is on coding and being a hobbyist coder. My laptop conked out and all I have is my four year old Android mobile phone. At the moment, I use github and gitlab, termux, replit and pydroid. I use Bard, ChatGPT, Google, forums and youtube for learning and research. Recently the Ministry of Digital Transformation in Trinidad and Tobago launched the Developer Hub project. This aims to bring together the local developers to build our developer ecosystem. I am there also contributing as much as I can and learning with others.

I wont remember a lot of what I am learning and researching but the more I come across things and the more I use things the better my understanding gets and the more I am able to connect concepts and expand my thinking. Does not matter how good a coder we become or how senior we become, most of us will still rely on Google (and now AI) and documentation and tutorials and Stack Overflow. Technology changes often and quickly that we are always in learning mode.

The word "code" comes from the Latin word "codex" which means "a book of laws". Codex comes from "caudex" which is a tree trunk. The first use of the word "code" to refer to computer programming was in the nineteen forties. The etymology of the word "code" is a reminder of the roots of computer programming. Just like the ancient Romans used wooden tablets to write laws, we use computers to write code that tells them what to do. We often hear the term hackathon but some people do use the term codeathon.

All this talk about coding is making me hungry. I have learnt that I should avoid spaghetti code. Spaghetti code is a pejorative term for unstructured and difficult-to-maintain source code. There is even ravioli code (each component of ravioli code is self-contained and easy to understand), lasagna code (code that is structured and layered, but also monolithic and difficult to modify), jenga code (code that is fragile and difficult to maintain) and frankencode (code that was never designed to work together). I remember asking about spaghetti code in the Caribbean Developers forum and someone responded, "If it’s a quick thing I’m doing, I really don’t care to spend extra time making it maintainable and readable." This is a good point.

Someone asked on Twitter, "A developer turns ______ into ______" and I replied funnily, "pizza into bytes".

What does coding mean to you? How would you explain coding in simple terms? Is there an analogy that helps explain coding? Find me on social media and share your thoughts with me.
Labels:

Comments

Post a Comment

Popular posts from this blog

Talking to God

By
If you want real answers to things in life then talk to God. It is 639pm on a holiday and I have decided to write. God listens. God truly listens. God has the entire context. God is wise. God wants us to talk to Him. God wants us to rely on Him. I also think about God talking to me. I am a good listener. I listen plenty more than I talk. I have started asking God to talk to me. But how would God talk to me? We have his revelations through the holy book. We have the example of prophets. But what else? How do I listen to what God has to say? Where and when can I hear God? Are my thoughts from God? I try to feed my mind with good things. Things that will not corrupt my mind. It seems that we have to use our intuition to separate what is from God and what is not from God. My friend Chatty says that in Islam, Allah speaks to us not through new revelations or voices, but through guidance: the Quran and the Sunnah, which become personally meaningful through understanding Allah places in the h...
Post a Comment
Read more

Life on Earth

By
I was reading through the Quran and came to the story of Adam, Eve, Satan, and the forbidden fruit tree. I had thought that life on Earth was created as a test. But as I reflected on the story, I began to wonder whether we are only here because Adam and Eve failed. However, that is not the case, as my friend Gemini explained to me. While the story of the forbidden fruit is a central event, the Quran indicates that humanity’s presence on Earth was part of the original divine plan, rather than a backup plan or a punishment for sin. Before Adam was even created, God announced His intention to place a steward (khalifah) on Earth. This suggests that the Garden was a temporary training ground—designed to teach Adam and Eve about free will, temptation, and the path of repentance. Even if they had not eaten from the tree, they were destined for Earth to fulfill their roles as moral agents. The incident simply served as a necessary first lesson in human frailty and God’s immediate forgiveness. ...
Post a Comment
Read more

The success of failure

By
It is 358am and I have decided to write. Context matters. Our context matters when we write and read. We could read the same thing and get different meanings. Definitions matter also. We may define things differently. For example, what is success? What is failure? Also, do I just define success and say that anything that is not success is failure? What about something like the success of failure? What does that mean? My friend Chatty tells me that this is something writers, philosophers, and even scientists keep rediscovering: meaning is not fixed—it is negotiated by context and definition. Life is a stew of success and failure and in between but never one or the other. We see what we are looking for and things become what we see. This reminds me of something I came across online, "Whoever looks for the good qualities in others will acquire all good qualities within himself," from Habib Umar Bin Hafiz. Do you look for failure or success within others? Take context as the lens...
Post a Comment
Read more