The Challenge

Operating Systems exams often require more than just theoretical knowledge; they demand a practical understanding of process management, shell scripting, and resource orchestration. Working on the UTN-FRA_SO_2do_Parcial project allowed us to bridge the gap between classroom concepts and hands-on system administration.

The Approach

Our focus was to streamline repetitive

Automation in system administration is often about reducing repetitive manual execution. Recently, while working on the UTN-FRA_SO_2do_Parcial---Castanheira-Becq-Carola project, the focus shifted toward structuring specific shell-based tasks to ensure reliable execution order.

The Challenge of Sequential Execution

When managing background processes or batch scripts, ensuring that tasks

Setting the Stage for Development

Starting a new project is often the most critical phase in a software lifecycle. It is the moment where decisions about project structure, version control, and initial repository setup define the long-term maintainability of your code. For the UTN-FRA_SO_2do_Parcial---Castanheira-Becq-Carola project, the first step involved initializing a structured

The Problem

Developing a management system for a zoological environment requires a robust way to represent various species, their habitats, and their specific care requirements. Without a clear object-oriented structure, the codebase quickly becomes a disorganized mess of classes, making it difficult to scale as new animals or facility features are added.

The Approach

Automating Service Infrastructure

Manual server configuration is a silent productivity killer. In the UTN-FRA_SO_2do_Parcial project, we focused on streamlining the deployment and management of web services by moving from manual setup to automated configuration management using Ansible.

The Challenge: Consistent Server State

Maintaining a consistent Nginx environment across different

Getting Started

Starting a new project, such as the Parcial1-CastanheiraBecqCarola repository, is the foundational step in any software lifecycle. Proper initialization ensures that your project has a clean, organized base from which to build your features.

The Initialization Process

When you begin a new project, the primary goal is to establish the source of truth for your codebase.

Starting a new project is always an exercise in setting the right tone. Whether you are building a small utility or a complex system, the first commit acts as the foundation upon which every future feature will rest. In the Parcial2-Castanheira-Becq-Carola project, we recently completed the initial project setup, laying the groundwork for our Java-based development environment.

Synchronization between local development environments and remote repositories is the bedrock of collaborative engineering. Recently, while working on the Carola178/Entregable1---Castanheira-Becq project, the necessity of maintaining a unified codebase state became the primary focus.

The Challenge of Divergent Environments

When multiple contributors interact with a shared codebase, the

Collaborating on software projects requires a consistent approach to version control. In the Parcial2-Castanheira-Becq-Carola project, recent activity focused on ensuring that the local codebase remains aligned with the primary source of truth. Keeping a project synchronized is not merely about moving files; it is about maintaining a coherent history that allows teams to integrate changes without

Every technical journey starts with a foundational step. Recently, I began working on the Castanheira_vagrant project, which serves as a configuration repository for managing isolated development environments.

The Philosophy of the Initial Commit

Starting a new project often feels like standing before a blank canvas. The initial commit is more than just the first set of files; it is the