Introduction
Welcome to LearningSea. This blog is my personal space, dedicated to documenting my learning journey in software development.
For me, this first post is equivalent to the hello world of programming, since I don’t yet have the habit of writing publicly.
The proposal is challenging: to write about concepts that I am still consolidating. But that is precisely the goal—to consolidate and document my learning.
A bit about me
My name is Leonardo, and I am a web developer focused on backend and APIs.
I am currently in the final semester of my degree in Systems Analysis and Development.
I have been studying programming and software engineering for approximately two and a half years, and during this time I have followed a mostly self-taught path.
Why a blog?
The main motivations for creating this project were:
- To develop and maintain my first production software
- To chronologically document my learning and consolidate it deeply, including experiments as a developer
Brief context on what led to the creation of this blog
Developing software is an interdisciplinary activity full of nuances. The more I learn and build, the more I realize that behind one giant mountain there is always a bigger one.
Over time, through practice, I realized the need and importance of documenting what I learn, as writing forces me to revisit concepts and explain them objectively. Additionally, it compels me to revisit points that I still cannot explain clearly.
What the name LearningSea represents
"Learning" represents the process of learning, which is the main focus when writing posts. "Sea" symbolizes the depth and complexity of the software development field.
Programming is a field full of abstractions, and the sea also evokes the idea of exploring a topic at different levels—from the most superficial to the deepest levels of abstraction.
It can also be seen as an analogy for navigating the software development field while new concepts are explored.
What to expect from future posts
I intend to write about software development, covering ideas, implementations, and records that may be useful.
I also want to share post-mortems of real problems I encounter, including the decisions made during development, as well as mistakes and lessons learned along the way.
The idea is to document not only what works, but also what goes wrong and what I learn in the process.