Why I decided to create this blog

I decided to create this blog because I want to build a digital presence and share some of what I have learned over the years.

I have been a software developer since 2008. I have worked on different products and spent years learning how software is designed, built, deployed and maintained. Much of that experience has stayed inside the companies and projects where I worked. I never really shared it publicly.

I also want to create new opportunities for myself. That might mean building tools, creating websites, writing technical content or eventually working as a freelancer. I have never worked as a freelancer before, but I would like to try it.

Extra income would be welcome too. Everyone needs money. If we have useful knowledge and know how to solve problems, we should be able to create value from it.

I want to use this blog to write about what I am working on, the lessons I have learned and the problems I am still trying to solve. I do not know everything and I do not want to pretend that I do. Technology keeps changing, so I keep learning too.

I started learning programming through object-oriented programming and Java. Java gave me a foundation in data structures and software architecture. It also gave me a base for building enterprise solutions used by thousands of people around the world.

Java was not the main language I used throughout my career. I spent many years working with web technologies such as PHP, JavaScript, HTML and CSS. I have also worked in the Ruby on Rails ecosystem.

That experience is why I consider myself a full-stack developer. To me, that term means more than working on a front end and a back end. A web application can involve infrastructure, databases, cache services, VPSs, VPCs, cloud computing, deployment, monitoring, security and much more. All of these pieces affect the final product.

During my career, I have watched the industry change. When I started, Agile methodologies and frameworks were still becoming common in IT. Today, AI is part of almost every conversation about software development. I see connections between these transitions and want to explore them in a separate article.

I also want to write about the IT job market, the way we use titles such as “software engineer” and what it means to work across the full stack. These subjects come from my own experience, but each one deserves more space than this introduction can provide.

This is why I am starting the blog: I want to share what I know, document what I am learning and create opportunities to do more with my experience.

I will explore those subjects in the following articles:

• From Agile to AI: New words, familiar engineering problems
• The IT job market is changing, but software work is not disappearing
• Software engineer or programmer?
• What full-stack development means to me

Back to notes