Introduction

After so much belabouring which felt like a paralysis analysis, Monday 10th August 2026 marked my formal leap into the vast space of data. In this article, I will share with you my maiden experience in the initial week leading to my first ever GitHub project while recounting each step along the way. We got introduced to platforms such as Dev.to, Markdown, Git and GitHub, Dbeaver, Visual Studio Code, Windows PowerShell, Zoho Cliq, PostgreSQL, Iven amongst other tools. The instructor stressed that the first week would be laidback, focussing more on the installation of requisite tools than active learning. This helped ease some of the tension from those in attendance as there had been plenty of higi haga stemming from the teething challenges of a new cohort.

Introduction to Dev.to

Dev.to was the first to be installed. This is the tool for writing articles and one must therefore setup an account using their Google credentials. One key feature of dev.to is that it stems what you have written to your profile. It also brings together a community of developers with diverse interests and can therefore act as a repository for harnessing theoretical knowledge. The platform has evolved with time to create job opportunities in the form of Technical Writing. Once logged in, navigating through is pretty simple as the user interface mirrors a blend of and social networks.

DEV Challenges

Occasionally, there are tech challenges in the form of mini Hackathons that provide a fun way of building up experience or showcasing learnt skills to the community and even potential employers.

Reading Lists

This is basically an assorted list of articles under your readership.

DEV++ Rewards

This is an incentive program for participating in DEV challenges.

DEV Education Tracks

Curated learning programs balancing between expertise and hands-on experience to come up with practical solutions.
The Dashboard displays account activities over time.

Markdown Language

Is a simple markup language used for text formatting. It switches between two user interfaces, the Edit page where all the primary writing happens and the Preview page that displays the output.
Rules and formatting techniques include:

1. Titles: Must be short, clear, easily searchable, understandable and properly capitalized.
2. Headings: Use # for the main heading, ## for subheadings & ### for third-level headings
3. Paragraph Length: Keep paragraphs concise, ideally 120-150 words to ensure readability.
4. Styling: Use ** for bold text and _ for italics.
5. Code Documentation: Use single backticks (or single quotes as specified by the platform) for inline code and triple backticks for blocks of code
6. Structuring Content: Introductions should begin with a generic, topic related sentence before narrowing down to the article's specific scope. Conclusions are recommended to summarize the technical process.
7. Other Formatting: Adding cover images (via! and URL links.

PostgreSQL
In day 2, the session started off with downloading and installing PostgreSQL. This is the database management system. A data tools installation guide had been previously shared which eased this process. Alternatively, one can download the tool from their web browser and follow guidelines as stipulated.

Dbeaver
This is an application that allows users to interact with databases more easily. It can therefore be interlinked to various database platforms including PostgreSQL, MySQL, Oracle. etc.
One therefore needs not download all the database platforms but instead can connect them through the cloud using Dbeaver.

Aiven
A cloud data platform through which you can create and manage services including PostgreSQL & MySQL. For our onboarding session, we used the free version which only allows one service to run at a time.

MySQL
Abbreviation for My Structured Query Language, this is a relational database management system that stores, organizes and manages data.

Github
A cloud-based developer platform used to store, manage and share software code. It is advisable to stay professional while setting up your account because it will act as your resume even when seeking opportunities.

Git
A control software system that is designed to manage versions of source code or data. It is capable of handling everything from small to large projects with speed and efficiency. It manages projects on a local host whereas GitHub showcases your projects on a cloud-based environment.

Repository
Sometimes referred to as repo,this is a project being tracked by Git. A GitHub repository is therefore where files and projects are stored with a trail of their historical chronology. Some of the common commands you will come across include:

• COMMITwhich is a saved checkpoint in your project's history, is a command issued to permanently save all the data modifications during an ongoing project.
• PUSH means sending data from a primary producer system into a database or server without waiting for a request. For example, creating a new user profile or Log In entry.
• PULL is the opposite of push and means requesting and retrieving information from a source, such as a database server, an API, or an external file, rather than having that data automatically sent to you. Here, it is the data consumer who initiates the action.
• CLONE means to download an existing data repository to your local computer as a Git repository. It allows users to read, write, modify, query and test data without changing the original source.
• FORK is to tweak a clone by creating an independent point-in-time copy without affecting the production database.

To check if a tool has been installed on Git bash, the following command applies.
git --version then press enter (where git can be replaced with any other applicable tool)

If the result is a defined version, then the tool is installed if the outcome is otherwise, then the tool is yet to be installed.
To configure your identity, Git will require your name and email address.
N/B: Your email address must match the one used to create your GitHub account.

The commands to use are:
git config --global user.name "Your Full Name" for User Name and
git config --global user.email "Your Email Address" for Email Address
To set Main as the branch, you use:
git config --global init.defaultBranch main then enter.

Once done, you need to verify the configuration through the following commands:
git config --global user.name for User Name
git config --global user.email for Email Address
To get a summary of the three, key in the following command
git config --global --list then press enter

Generating An SSH Key

This is to enable the integration of the GitHub and Git for a seamless integration of the two platforms thereby easing way for the exchange of data. By generating an SSH Key, one bypasses the password and authentication restrictions characteristic of a GitHub account.

First to be generated is your private key which is to be stored in your local computer and must remain confidential.
The second is the public key which will be posted on your GitHub account for public consumption. To generate it, you basically add

pub> to the private key.
Run the following command to establish if it has already been generated.
ls ~al ~/.ssh
If not, run the following command.
ssh-keygen -t ed25519 -C "your_email@example.com"
Then create a passphrase that you will easily recall and confirm.
This should generate and save the keys on your local PC.
The key fingerprint and a random art image will also be generated.
Then rerun the command ls ~al ~/.ssh to regenerate the keys.

Conclusion

In summary, the initial week of data onboarding focused on installing essential development tools, configuring Git and GitHub, and setting up database management systems like PostgreSQL and MySQL. Key practices include utilizing Markdown for documentation, managing local and cloud repositories with Git commands, and establishing secure SSH key integration.