DEV Community: PETER IREGI

Coder, Programmer, and Software Developer: Understanding the Journey

PETER IREGI — Sat, 13 Jun 2026 22:13:20 +0000

Many people use the terms coder, programmer, and software developer interchangeably. While they overlap, they represent different levels of responsibility and understanding in the software creation process.

Understanding these differences can help beginners identify where they are today and what skills they need to acquire to move forward.

A coder focuses primarily on writing code. At this stage the main concern is translating instructions into a programming language. A coder understands syntax, variables, loops, functions, conditionals, and basic data structures. A coder can write the necessary code to complete the task.

However, coders often rely heavily on detailed instructions. They may know how to implement a feature but struggle to determine what should be built, how different components interact, or how the entire system should be structured.

A programmer goes beyond writing code and focuses on solving problems. Programmers think in terms of logic, algorithms, efficiency, and system behavior. They can break larger problems into smaller parts and create programs that satisfy requirements. A programmer is not just translating instructions into code. They are designing solutions.

A software developer focuses on building complete software systems. Developers write code and solve problems but they also understand how software is planned, designed, tested, deployed, maintained, and improved.

Software development involves much more than coding. It includes architecture, teamwork, version control, documentation, testing, deployment, and user experience.

Imagine building a house. A coder is like a worker who knows how to lay bricks, a programmer is like a skilled builder who knows where each brick should go and why and a software developer is like the architect and project manager who understands the entire project—from planning and design to construction and maintenance. All three roles are important, but each involves a broader level of responsibility.

As a beginner, I believed that learning a programming language would make me a software developer. Later I discovered that knowing how to write code is only one part of the journey. I could write functions and small programs, but I struggled to answer bigger questions: What files should the project contain? How should the database be structured? How should different components communicate? How should the application be deployed?

This realization showed me that software development is not merely writing code. It is the process of transforming an idea into a working product that people can use.

Every software developer starts as a coder by learning problem-solving, building projects, understanding system design, and gaining real-world experience they gradually becomes a programmer and eventually a software developer.

The transition is not defined by how many programming languages you know. It is defined by how much responsibility you can take for turning an idea into working software.

Framework Limbo

PETER IREGI — Tue, 02 Jun 2026 19:42:13 +0000

Learning a programming language feels amazing at first. You start with variables, then loops, then functions, then a few days later you are writing small programs and feel unstoppable.
You watch a few tutorials, solve a few exercises and you start thinking programming isn't as hard as people said it would be.

Then your next opponent steps into the ring .You decide to build something real and that is when frameworks arrive. When I first started learning programming everything felt logical. I could look at a piece of code and understand what was happening. Every lesson built naturally on the one before it. Then I finished the beginner tutorials and made the mistake of searching for how to build a real application and after three hours of configuring things you realize you haven't built anything.
A few days ago you could explain what a function was now the code doesn't look like the language you learnt, nothing makes sense. You start wondering whether you ever understood the language at all.
It is at this moment you realize that learning a language and building a software are two different things. One teaches you the syntax the other teaches you how entire systems communicate. It is like learning English and then being handed a law textbook. Technically its the same language but it certainly doesn't feel like it.

When Does the Information Overload Stop?

PETER IREGI — Sun, 31 May 2026 21:06:55 +0000

Every time I sit down to learn something, I find myself trapped in the same cycle. I start with a tutorial. Halfway through, someone says there's a better tutorial. I switch. Then I discover a book that supposedly explains the topic better than the tutorial. Then a YouTube video claims the book is outdated. Then a developer on social media recommends an entirely different resource. Before I know it, I've spent three hours researching how to learn instead of actually learning.
Does the information overload stop or will there always be another resource, another course, another book, another video, another roadmap, another expert with a different opinion.
The internet has made knowledge abundant, but abundance creates a paradox of choice. One person says to learn JavaScript from documentation, another says build projects immediately, another recommends a paid course, someone else insists that free resources are better. Every recommendation sounds convincing. Every path seems important. The result is paralysis. Instead of moving forward, I keep searching, instead of building I keep comparing, instead of learning I keep consuming. finished teaches more than a hundred bookmarked tutorials.
At some point, every learner must accept a difficult truth that the goal is not to find the best resource it is to become better. Those are not the same thing. A person can spend months researching the perfect learning path and never write a meaningful line of code while another person can pick a decent resource, make mistakes, build projects, and improve every day. The second person wins not because they found better information but because they used the information they already had.
I've started realizing that learning is a lot like fitness. At some point, reading about exercise becomes a form of avoiding exercise. The same thing happens in programming. Reading about coding becomes a way to avoid coding. Researching becomes a substitute for practice. The search for the perfect resource becomes a comfortable excuse for not doing the difficult work.
The truth is that no single tutorial, book, course, or mentor will teach you everything. Learning is not about consuming every resource available. It is about extracting value from the resources you already have. There will always be a better book, a better course, a better video, a better explanation but there will never be a substitute for time spent doing the work. So for now, I've made a simple rule for myself, When I catch myself searching for a better resource, I ask a question, "Have I fully used the one I'm already learning from?" That's my signal to close the browser tabs, stop searching, and get back to building.
Progress rarely comes from finding the perfect resource. It comes from staying with a good enough one long enough to grow.

Will Learning Programming Still Pay Off, or Will AI Replace Me Before I Get There?

PETER IREGI — Sun, 31 May 2026 20:19:10 +0000

I am a beginner programmer.

Right now, I'm learning Go and JavaScript. Some days I feel excited about the possibilities ahead. Other days I open social media and see headlines saying that AI can write code, build websites, create apps, and replace software developers.

Naturally, a question starts creeping into my mind Am I wasting my time learning to code?

When I first started learning programming, I imagined a future where software developers would always be in demand. Then AI tools became incredibly powerful. Looking at all this, it's easy to assume that programming careers are disappearing. The biggest misconception is that programmers are paid simply to write code. They're not.

Developers are paid to solve problems. Code is just the tool used to build the solution. AI can generate code, but it doesn't fully understand a company's goals, customers, budget constraints, legal requirements, security risks, or long-term strategy. Humans still make those decisions.

Ironically, AI may increase the value of people who understand programming. If everyone has access to an AI coding assistant, the people who benefit most will be those who can read code, verify AI-generated solutions, debug mistakes and much more. In other words, the people who know programming. Someone who doesn't understand programming often has no way to know whether the AI's output is correct.

Will AI change software development? Absolutely. Will some programming tasks become automated? Without question. Will developers disappear? Highly unlikely. Software is becoming more important in every industry, not less. As long as businesses have problems that need solving, there will be a need for people who understand technology deeply enough to build solutions.

As a beginner learning Go and JavaScript, I've decided that worrying about being replaced is less productive than becoming skilled. AI may write some of the code but someone still needs to understand the problem, guide the solution, verify the results, and take responsibility for the outcome. For now, that's the developer and that's why I'm continuing to learn.

Complaining professionally

PETER IREGI — Wed, 15 Apr 2026 06:27:20 +0000

Since I started I have come to the realization that I have taken on a new habit. complaining I have become adept at the art of complaining.
The subject could be different but the complaining is a constant . I know going out of your comfort zone is well to say the least not pleasant but the fact that complaining has become like second nature every time the opportunity arises is more than frustrating.
The fact that even this post is complaining that I cant stop complaining, making the monster even bigger, feeding into the habit even more.
I don't know how to stop.But I want to, although it doesn't make me avoid doing the task at hand but starting the task, whatever it might be with, a negative attitude or doing it with a bias formed about the difficulty doesn't make it easier.
I would like to learn how to not complain on how not doing it would be inconvenient or how it could be easier to do it in a less than satisfactory manner without putting as much effort.
It is a bad habit that I want to stop but am finding that starting was way easier than stopping and its a slippery slope after starting.

Is it just me ?

PETER IREGI — Wed, 11 Mar 2026 07:02:28 +0000

Since I started my journey in learning Go, I have met some challenges along the way. Once in a while a topic will have me confused forcing me to read about it from multiple sources and still end up where I was initially if not worse than I was.
I know that in order to learn you have to accept that you will feel stupid at times but, "I have been reading the contents of this page for the last hour and a half and still don't understand error handling in Go.", "should I take a break and try it again later or just give it a rest and hope it comes to me someday". These are some of the thoughts that go through my mind most of the time. Always stuck in the loop of deciding to reread the material to see if the 13th time is the charm and I will understand it after that or giving it a rest and leaving it all up to the fates.
Hopefully it gets better and the documentation stops feeling like Greek every once in a while. I don't know if it gets easier but my fingers are crossed in the hopes that it gets better, or I get better at it?

Testing, is it the egg or the chicken?

PETER IREGI — Sun, 22 Feb 2026 18:07:55 +0000

As I had mentioned I am a beginner, with zero experience. Starting my journey with Golang and I got some advice that I should try learning TDD from the jump and since it came from someone I look up to I gave it a try. I was confused from the jump as some one who knows absolutely nothing I was thrown deep into the waters seeing thing that I didn't know the meaning of and how they worked or why the worked how they worked but after a while of learning how to write in Go by starting with the tests for my programs the pieces are starting to come together now, not all of them but just enough for me to see some progress from where I started to where I am now and it is a bit exciting can't wait to learn more and piece more together it is always fun to find out why a certain thing works they way it does especially after having used it for sometime without knowing, It gives you that aha! moment when it all comes together and makes a lot more sense now.

Where to start?

PETER IREGI — Mon, 09 Feb 2026 11:30:46 +0000

As a beginner I have seen more than one article on what I where I should start what I should learn first in the year 2026. It is all good advice till you have seen ten articles each offering arguments that make the last one you went through seem like some bad advice from a mad person.
You can find advice from different people on the same topic but each has been modified by their experience and is not necessarily what is best for you.
What could have worked for one person is not guaranteed to work for every one.what one person wished they could have done when they were starting out is not what every person should do when starting out.It is advised that we learn from the mistakes of those who came before us to save us the struggle but at times the struggle is needed for the journey to have meaning.
Instead of reading more articles just decide on one path stick to it and if along the way you have a change of heart or perspective you are always free to re-strategist and pick an new path that aligns with your intentions. The most important thing is that you start and don't get stuck in an infinite loop of research.