DEV Community: Idrissa HEMEDY

Mon parcours de stage à KADEA Academy Goma

Idrissa HEMEDY — Wed, 19 Feb 2025 05:26:50 +0000

Introduction

Le processus d'apprentissage dans le système LMD au Congo Kinshasa demande aux étudiants universitaires de compléter leur cursus de licence par un stage académique avant de passer au cycle suivant.
C'est la raison première de mon stage à KADEA Academy.

Plus encore, étant du domaine Informatique, un stage en milieu professionnel est une opportunité excellente pour mettre en pratique les connaissances acquises à la faculté, les évaluer et acquérir d'autres connaissances. Celle-ci est la deuxième raison de mon stage sans pour autant être moindre.

Parcours

I. Période de stage

Mon stage est allé du 12 Aout au 21 Septembre 2024, une période de 6 semaines en travaillant du lundi au vendredi chaque semaine

II. Organisation du travail

Chaque semaine, j'avais un ensemble de tâches à réaliser pour atteindre les objectif de mon stage.
Le travail est censé commencer chaque jour à partir de 8h30 et prendre fin aux alentours de 16h30.
Pour chaque jour, un Daily Standup doit être établi. Celui-ci reprend les tâches accomplies le jour précèdent, celles à réaliser le jour dont il est question et les éventuels blocages auxquels on a été confronté.

II.1. Objectifs du stage

Pour mon stage, j'ai pour objectif:

Réaliser une version simple d'une application permettant à une organisation de tracker les visites faites dans ses locaux
Faire 2 pull requests sur des projets open source
Animer quelques sessions d'info gratuites offertes sur HTML et CSS
Publier 3 articles, les 2 premiers portant sur des sujets de notre choix et le dernier portant sur mon parcours chez KADEA

II.2. Outils de travail

Voici les outils qu'on a eu à utiliser:

Slack: pour la communication
Git & GitHub: pour la le versioning du code
VS Code: pour l'implémentation du code et le développement
Trello: pour le planning des activités de développement
Figma: pour le design de la plateforme

III. Présentation du projet de stage

Le projet sur lequel nous avons eu a travailler le temps de notre stage est VisiTrack.

Visitrack est une application web qui permet aux entreprises de retracer l’historique des visites qui ont été faites dans leurs locaux. Les utilisateurs, une fois connectés, enregistrent quotidiennement toutes les visites en enregistrant le nom et postnom du visiteur, la raison de sa visite, l’heure d'arrivée et celle de départ.

III.1. Liens

Live: https://visitrack.vercel.app
GitHub: https://https://github.com/e-idrissa/visitrack-app
Figma: https://www.figma.com/design/QyPYvqPlk36AkPClnSn0tV/Visitrack?node-id=0-1&node-type=canvas&t=jqfozwbfVIfoRyKO-0

III.2. Fonctionnement

Pour utiliser VisiTrack, l'utilisateur se rend sur la page web et s'inscrit s'il n'a pas encore de compte ou alors s'authentifie s'il est déjà inscrit.
Une fois connecté, l'utilisateur pourra à on aise créer des visites, les modifier ou les supprimer.

III.3. Améliorations

Ce projet n'étant qu'une première version d'une application possiblement commercialisable, voici les améliorations qu'il est possible de lui apporter:

Ajouter un compte administrateur pour ne pas permettre a tout le monde d'accéder a la plateforme.
Implémenter une application mobile pour une meilleur portabilité

IV. Contributions open source

Les contributions open source que nous avons accomplies, étant aussi les toutes premières que nous ayons eu à faire sont les suivantes :

V. Articles

Mise à part celui-ci, nous avons aussi publié nos deux premiers articles sur dev.to pendant le stage: un article sur la contribution open source et un article sur la gestion des projets en software engineering

Appréciations

Le stage s'est en soit très bien déroulé et dans un environnement convivial, calme et favorisant l'apprentissage.

Les coachs nous ont offert une bonne expérience et un bel aperçu du travail auquel on s'attend en tant qu'informaticien ; la convivialité, la rigueur, la discipline et la flexibilité dans le travail.

Project Management in Software Engineering

Idrissa HEMEDY — Mon, 09 Sep 2024 07:59:17 +0000

Introduction

As developers, we often chase after the next groundbreaking idea or seek opportunities to maximize our earnings through coding 🤑. However, before those dreams become reality, we frequently find ourselves working on team or personal projects. Many of us might not fully realize how crucial it is to properly structure and present these projects.

A well-organized project structure and clear presentation are essential. They not only provide a comprehensive view of what we’re building but also contribute to maintaining clean and efficient code 🧑‍💻.

Achieving a solid project structure and effective presentation is possible with a robust project plan and diligent project management. By focusing on these aspects, we set ourselves up for success, both in realizing our current projects and in reaching our broader career goals.

In this article, we’ll explore the fundamentals of project management in software engineering.

Project management and Project plan

We previously talked about project management and project plan if we want to achieve a solid project structure. What is the difference between them?

What is a project management?

Project management involves leading and directing a project from start to finish. It includes applying knowledge, skills, tools, and techniques to ensure that the project meets its requirements and achieves its goals.

What is project plan?

A project plan is a comprehensive document that outlines the scope, objectives, tasks, timeline, resources, and budget of a project. It serves as a roadmap for the project team, ensuring everyone is aligned and working towards a common goal.

In summary, the project plan is a comprehensive document that outlines the details of a project, while project management is the overall process of planning, executing, and controlling the project to achieve its goals. Both are essential for successful project outcomes.

Project management in Software engineering

Project management in software engineering is a systematic approach to planning, organizing, and controlling the development of software projects. It ensures that projects are completed on time, within budget, and meet the specified quality standards.

Key considerations in software project management include:

Timeliness: Projects must be completed within agreed-upon deadlines to meet customer expectations and avoid delays.
Budget: Projects are allocated a fixed amount of resources, including human, financial, and material resources. Adhering to the budget is crucial to avoid cost overruns.
Quality: Software must meet specific functional and non-functional requirements to deliver value to users. Ensuring quality throughout the development process is essential.

Ignoring any of these three factors can lead to project failures or suboptimal outcomes.

Approach

In software engineering, there are 2 main approaches when it comes to project management:

Agile: This iterative approach emphasizes flexibility, collaboration, and continuous improvement. It involves breaking down the project into smaller increments (sprints) and delivering working software at the end of each sprint.
Waterfall: This traditional approach follows a linear sequence of phases

Choosing the right project management approach depends on the project's characteristics. If the project involves frequent changes, uncertain requirements, or a need for continuous feedback, an Agile approach is often suitable. Else if the project has well-defined requirements, a stable scope, and a predictable timeline, a Waterfall approach might be more appropriate. Waterfall methodologies follow a sequential process, moving from one phase to the next.
It's important to note that hybrid approaches, combining elements of Agile and Waterfall, can also be effective in certain situations.

Project Planning and Scheduling

there are 3 principal alternatives :

Work Breakdown Structure (WBS): Divides the project into smaller, manageable tasks.
Gantt Charts: Visualize the project schedule, showing task dependencies and deadlines.
Critical Path Method (CPM): Identifies the longest path through the project network and highlights critical tasks that must be completed on time to avoid delays.

Risk management

This process involves three key steps:

Risk Identification: Identifying potential threats or challenges that could negatively impact the project's success.
Risk Assessment: Evaluating the likelihood and severity of each identified risk.
Risk Mitigation: Developing strategies to reduce or eliminate the identified risks, or to create contingency plans to address them if they occur.

Quality Assurance and Testing

Quality assurance (QA) and testing are crucial for ensuring software works as expected. Here's a breakdown:

Unit Testing: Check individual parts of the software.
Integration Testing: See how different parts work together.
System Testing: Test the whole software to make sure it works.
Acceptance Testing: Make sure the software meets the customer's needs. By doing these tests, software teams can find and fix problems early, making the software better.

Configuration Management

Version Control: Keep track of changes to the software's code and documentation. This helps you see what has been changed and when, making it easier to collaborate and manage different versions.
Change Management: Manage changes to the project's goals, what it needs to do, or how it's designed. This ensures that everyone is on the same page and that changes are made systematically.

Communication and Collaboration

Stakeholder Management: Make sure everyone understands what's expected and communicates clearly. This includes customers, developers, and managers.
Team Collaboration: Encourage teamwork and open communication within the development team. This helps everyone work together effectively and solve problems.

Project Monitoring and Control

Progress Tracking: Check how the project is going compared to the plan and budget.
Issue Tracking: Look for any issues that might slow down the project and fix them.
Performance Evaluation: See how the team is working and make changes if needed.

Tools and Technologies

Project Management Software: Use tools like Jira, Trello, or Asana to manage tasks, track progress, and work together.
Version Control Systems: Use Git, SVN, or Mercurial to keep track of changes to the software's code.
Issue Tracking Tools: Use Bugzilla or GitHub Issues to find and fix problems.

Main Activities

Software project management involves a wide range of activities, such as:

Initiation: Define what the project is about, its goals, and if it's possible to do.
Planning: Create a detailed plan for the project, including all the important parts.
Executing: Follow the plan and do the work needed for the project.
Monitoring and Controlling: Watch how the project is going, find any problems, and fix them.
Closing: Complete the project, deliver the final product, and see how well it went.

Conclusion

Effective project management is the key to successful software development. By implementing a comprehensive project plan and utilizing the right tools and strategies, you can streamline your development process, mitigate risks, and deliver high-quality software on time and within budget. The techniques outlined in this article, including project planning, risk management, communication, and quality assurance, provide a solid foundation for achieving project success. Remember, a well-structured project and effective leadership are essential for delivering exceptional results.

Open source Contribution, First Pull Request

Idrissa HEMEDY — Mon, 09 Sep 2024 07:55:07 +0000

Introduction

As newcomers to web development, we often believe that the only way to improve our skills is by working on our own projects. But what happens when you run out of project ideas or don't have a team to collaborate with? Should you close your code editor and put your ambitions on hold? This is where Open Source Contributions can make a significant difference. By contributing to open source, you not only hone your coding skills but also become part of a global community that builds and maintains software used by millions. Whether it's your first pull request or your hundredth, open source offers endless opportunities for learning, collaboration, and growth.

What is an Open source Contribution?

An open source contribution refers to the act of participating in the development or improvement of open source software. Open source software is software that is freely available for anyone to use, modify, and distribute.

Open source contributions are typically made through platforms like GitHub, where developers can submit changes via pull requests that are reviewed and potentially merged into the main project by the maintainers.

What can I contribute on?

Contributions can come in various forms, including:

Code Contributions: Writing new features, fixing bugs, or improving existing code.
Documentation: Creating or improving documentation to help others understand how to use the software, how it works, or how to contribute.
Design: Contributing to the visual design, user interface, or user experience of the project.
Testing: Writing tests, reporting bugs, or helping to ensure the software works as intended across different environments.
Translation: Translating the software and its documentation into different languages to make it accessible to a broader audience.
Community Support: Helping other users and contributors by answering questions, providing guidance, or reviewing pull requests.

Open source project ideas

Here is some beginner friendly open source projects you can look on:

Pull Request

As discussed earlier, pull requests (PRs) are the primary method developers use to submit their changes to open source projects. When a developer opens a PR, it signals to the project maintainers that new code is ready for review. The maintainers carefully evaluate the PR, ensuring that the changes contribute value to the project without introducing any issues or breaking existing functionality. If the PR meets these criteria, it is merged into the main codebase, becoming part of the official project.

Step by Step guide to your First PR

We assume that you are already familiar with Git and GitHub, and have them set up on your machine. If not, refer to this article on how to install Git on Windows and How to set it up.

Once you have everything set up and have chosen the project you want to contribute to, follow these steps to make your first PR

1. Create a copy of the repository

A repository, or "repo," is essentially the main folder where a project is stored on GitHub. To start working on an open-source project, you first need to create your own copy of the repository. This process involves forking the repository to create a copy under your GitHub account and then cloning it to your local machine, giving you a working version of the project that you can modify and experiment with.

a. Forking
When you’re on the main page for the repository, a Fork button will be displayed on your upper right-hand side of the page, underneath your user icon:

Follow the process and end with the forking.

b. Cloning
You can copy the URL by using the green “⤓ Code” button from your repository page that you forked from the original repository page. Once you click the button, you’ll be able to copy the URL by clicking the clipboard button next to the URL. Open your terminal. navigate to the folder you want to clone the project to and clone it using this Git command:

git clone --copied-link

After that, navigate to the cloned folder by taping:

cd cloned-project

2. Create new branch and start modifications

Before you begin working on the code and making changes, it's important to create a new branch. This branch will serve as a separate workspace for your code modifications, keeping them isolated from the main codebase. Your changes will be saved and reviewed on this branch before they are potentially merged into the project. To create a new branch and switch to it, open your terminal and enter the following command:

git checkout -b --your-branch-name

🎉 You're done. You can now make changes and save them.

3. Save local changes and commit

After working on your changes, you'll need to save them locally by doing:

git add -A

And then commit your changes:

git commit -m "Custom commit message"

4. Update local repository

When working on a project with other contributors, it’s crucial to keep your local repository up-to-date to avoid conflicts when making a pull request. To do this, you need to sync changes regularly.

First, we'll cover how to configure a remote for your fork, then how to sync it with the original repository

a. Configure a remote
Let’s first check which remote servers you have configured. From the directory of the repository in our terminal window, let’s use the git remote command along with the -v flag to display the URLs that Git has stored along with the relevant remote

git remote -v

Next, we’ll specify a new remote upstream repository for us to sync with the fork. This will be the original repository that we forked from. We’ll do this with the git remote add command

git remote add upstream --original-repo-link

We can verify that our remote pointer to the upstream repository was properly added by using the git remote -v command again from the repository directory.

b. Sync the fork
To sync our fork, from the directory of our local repository in a terminal window, we’ll use the git fetch command. Since we used the shortname “upstream” to refer to the upstream repository, we’ll pass that to the command:

git fetch upstream

Now, commits to the main branch will be stored in a local branch called upstream/main.

Let’s switch to the local main branch of our repository:

git checkout main

And merge our changes:

git merge upstream/main

Your fork’s main branch is now in sync with the upstream repository, and any local changes you made were not lost.

5. Create a PR

At this point, you are ready to make a pull request to the original repository.

You should navigate to your forked repository, and press the New pull request button on your left-hand side of the page.

Follow the steps and there we go, your first Open source Contribution is live and you achieve your first PR.
🎉🎉 Congratulations.

Conclusion

Contributing to open source through your first pull request is a rewarding experience that accelerates your growth as a developer. It’s not just about improving your coding skills, but also about collaborating with a global community, learning best practices, and making a meaningful impact. By following these steps, you’re not just submitting code—you’re joining a movement that powers countless projects around the world. Dive in, contribute, and watch your skills and confidence soar.

Open source Contribution, First Pull Request

Idrissa HEMEDY — Tue, 03 Sep 2024 11:34:33 +0000

Introduction

What is an Open source Contribution?

What can I contribute on?

Contributions can come in various forms, including:

Code Contributions: Writing new features, fixing bugs, or improving existing code.
Documentation: Creating or improving documentation to help others understand how to use the software, how it works, or how to contribute.
Design: Contributing to the visual design, user interface, or user experience of the project.
Testing: Writing tests, reporting bugs, or helping to ensure the software works as intended across different environments.
Translation: Translating the software and its documentation into different languages to make it accessible to a broader audience.
Community Support: Helping other users and contributors by answering questions, providing guidance, or reviewing pull requests.

Open source project ideas

Here is some beginner friendly open source projects you can look on:

Pull Request

Step by Step guide to your First PR

We assume that you are already familiar with Git and GitHub, and have them set up on your machine. If not, refer to this article on how to install Git on Windows and How to set it up.

Once you have everything set up and have chosen the project you want to contribute to, follow these steps to make your first PR

1. Create a copy of the repository

a. Forking
When you’re on the main page for the repository, a Fork button will be displayed on your upper right-hand side of the page, underneath your user icon:

Follow the process and end with the forking.

git clone --copied-link

After that, navigate to the cloned folder by taping:

cd cloned-project

2. Create new branch and start modifications

git checkout -b --your-branch-name

🎉 You're done. You can now make changes and save them.

3. Save local changes and commit

After working on your changes, you'll need to save them locally by doing:

git add -A

And then commit your changes:

git commit -m "Custom commit message"

4. Update local repository

First, we'll cover how to configure a remote for your fork, then how to sync it with the original repository

git remote -v

Next, we’ll specify a new remote upstream repository for us to sync with the fork. This will be the original repository that we forked from. We’ll do this with the git remote add command

git remote add upstream --original-repo-link

We can verify that our remote pointer to the upstream repository was properly added by using the git remote -v command again from the repository directory.

git fetch upstream

Now, commits to the main branch will be stored in a local branch called upstream/main.

Let’s switch to the local main branch of our repository:

git checkout main

And merge our changes:

git merge upstream/main

Your fork’s main branch is now in sync with the upstream repository, and any local changes you made were not lost.

5. Create a PR

At this point, you are ready to make a pull request to the original repository.

You should navigate to your forked repository, and press the New pull request button on your left-hand side of the page.

Follow the steps and there we go, your first Open source Contribution is live and you achieve your first PR.
🎉🎉 Congratulations.

Conclusion

Project Management in Software Engineering

Idrissa HEMEDY — Fri, 23 Aug 2024 14:04:01 +0000

Introduction

In this article, we’ll explore the fundamentals of project management in software engineering.

Project management and Project plan

We previously talked about project management and project plan if we want to achieve a solid project structure. What is the difference between them?

What is a project management?

What is project plan?

Project management in Software engineering

Key considerations in software project management include:

Timeliness: Projects must be completed within agreed-upon deadlines to meet customer expectations and avoid delays.
Budget: Projects are allocated a fixed amount of resources, including human, financial, and material resources. Adhering to the budget is crucial to avoid cost overruns.
Quality: Software must meet specific functional and non-functional requirements to deliver value to users. Ensuring quality throughout the development process is essential.

Ignoring any of these three factors can lead to project failures or suboptimal outcomes.

Approach

In software engineering, there are 2 main approaches when it comes to project management:

Agile: This iterative approach emphasizes flexibility, collaboration, and continuous improvement. It involves breaking down the project into smaller increments (sprints) and delivering working software at the end of each sprint.
Waterfall: This traditional approach follows a linear sequence of phases

Project Planning and Scheduling

there are 3 principal alternatives :

Work Breakdown Structure (WBS): Divides the project into smaller, manageable tasks.
Gantt Charts: Visualize the project schedule, showing task dependencies and deadlines.
Critical Path Method (CPM): Identifies the longest path through the project network and highlights critical tasks that must be completed on time to avoid delays.

Risk management

This process involves three key steps:

Risk Identification: Identifying potential threats or challenges that could negatively impact the project's success.
Risk Assessment: Evaluating the likelihood and severity of each identified risk.
Risk Mitigation: Developing strategies to reduce or eliminate the identified risks, or to create contingency plans to address them if they occur.

Quality Assurance and Testing

Quality assurance (QA) and testing are crucial for ensuring software works as expected. Here's a breakdown:

Unit Testing: Check individual parts of the software.
Integration Testing: See how different parts work together.
System Testing: Test the whole software to make sure it works.
Acceptance Testing: Make sure the software meets the customer's needs. By doing these tests, software teams can find and fix problems early, making the software better.

Configuration Management

Version Control: Keep track of changes to the software's code and documentation. This helps you see what has been changed and when, making it easier to collaborate and manage different versions.
Change Management: Manage changes to the project's goals, what it needs to do, or how it's designed. This ensures that everyone is on the same page and that changes are made systematically.

Communication and Collaboration

Stakeholder Management: Make sure everyone understands what's expected and communicates clearly. This includes customers, developers, and managers.
Team Collaboration: Encourage teamwork and open communication within the development team. This helps everyone work together effectively and solve problems.

Project Monitoring and Control

Progress Tracking: Check how the project is going compared to the plan and budget.
Issue Tracking: Look for any issues that might slow down the project and fix them.
Performance Evaluation: See how the team is working and make changes if needed.

Tools and Technologies

Project Management Software: Use tools like Jira, Trello, or Asana to manage tasks, track progress, and work together.
Version Control Systems: Use Git, SVN, or Mercurial to keep track of changes to the software's code.
Issue Tracking Tools: Use Bugzilla or GitHub Issues to find and fix problems.

Main Activities

Software project management involves a wide range of activities, such as:

Initiation: Define what the project is about, its goals, and if it's possible to do.
Planning: Create a detailed plan for the project, including all the important parts.
Executing: Follow the plan and do the work needed for the project.
Monitoring and Controlling: Watch how the project is going, find any problems, and fix them.
Closing: Complete the project, deliver the final product, and see how well it went.