Skip to main content

What is coding?

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.

Comments

Popular posts from this blog

Coffee and a prayer

It is 245am and I have decided to write. I have no topic and no idea what to write. I am thankful for another day. I see the beauty that surrounds us. I choose to be happy. We are in the last ten nights of Ramadan. Tonight is the 23rd night. It could possibly be the night of power. I wonder if it will rain. Maybe it rained when I was sleeping. I got up and bathed and drank a strong cup of coffee. Today is also Friday the 13th. I keep thinking. Life is beautiful. Life is simple. No need to complicate things. No need to be extravagant. Believe in God. Trust in God. Be guided by God. Imagine we can pray for anything. We can ask God for anything. God is always listening. God wants to hear from us. Maybe I can turn this blog post into a prayer. My God I pray that everyone gets their prayers answered. I pray that everyone gets what they need. I pray that you light our path towards you. Guide us with what you intend for us. Keep us close to you. Soften our hearts. Keep us balanced, consistent...

Belief is a part of life

I watched this video and I quite like it as a good starting point for this blog post https://youtu.be/t44PFI_V4LE We cannot know everything. We do not have the capacity to know everything. I make plans for tomorrow because I believe there is a tomorrow not because I know that there is a tomorrow. We cannot decide today to say we will only act on things that we know for sure. This would be impractical. As my friend Chatty puts it, to live life, we must believe in things that cannot always be proven with certainty. For example, we believe that the future exists, that our actions matter, and that other people can be trusted. We also tend to believe life has meaning and that things can improve. These beliefs help us make decisions, keep hope, and move forward. Given that belief is a part of life, it is reasonable to have people believe in a God and a particular religion. My point is this. Life cannot happen without belief because we cannot know everything (unless we are God like). Belief i...

God of direction

It is 323am and I have decided to write. I am thinking that I am a bucket of paint. A beautiful shade of blue. That God uses to paint the sky. How could I turn this into something worth writing about? My friend Chatty tells me that I could develop the idea by exploring the metaphor of myself as a bucket of blue paint and God as the painter using it to color the sky. The meaning comes from reflecting on what it feels like to be "used"—losing some of myself while helping create something beautiful. The paint may not see the whole picture and might fear being emptied, but its purpose is fulfilled when it becomes part of the sky. The piece can reflect on purpose, trust, surrender, and the idea that giving of yourself is how beauty is created. It is now 423am and I cannot think of a way to continue this writing. The sky is silent is what comes to my mind. How do I ask the sky to speak to me? I look through my window and I see patches of clouds against a dark sky. Maybe the night s...