Koe

Yes most Linux distros are very stable, way more secure, privacy friendly, and way more customizable. But every institution is built to make technological independence as difficult as possible.

here is a link to many public APIs that you could use in your projects 👩🏻‍💻✨

Day 25 - 33

I was able to complete another SheCodes workshop 🎉🥳

I am so happy and I can’t wait for the next workshop which about Al projects 👩🏻‍💻✨

This was my project (and yes there is a problem with the background but I still don’t know how to fix it 😭 I need to work on that)

@typecastofficial i did this btw :)

here are my spoils :3

these screenshots have a much more toned down text color, compared to how it looks irl. the default linux terminal text is the brightest thing it existence 0_0

and the btrfs drive just shoes up as normal 0_0

Table of content: Part 1: What is GIT? Why should I care?

Part 2: Definitions of terms and concepts

Part 3: How to learn GIT after (or instead of ) this guide.

Part 4: How to use GIT as 1 person

Part 5: How to use GIT as a group.

When it comes to not getting in each other's way, working alone is the simplest (It has a lot of other drawbacks). This is the simplest way to use GIT. You can do it with an external repository as a backup or just locally on your computer. It depends on how important your project is. If your laptop crashes tomorrow, which projects would you have a really hard time losing? Better to have an external backup for that. Github is often used for this (Maybe less now that Github makes machine learning AI’s, and so ARE stealing your code to train their AI on.) but you can also use Bitbucket (Which... may also steal your code...) and there are many many others out there. GIT is often used in certain patterns, called “workflows”. These have you working in more or less rigid ways to make it simple to work together. But since you are working alone, you do not risk others changing your code while you are working, so you can do it the simplest way :D

I will be doing a step by step guide that you can follow along. I will be doing it on a completely empty project and making a tiiiiiny program in C. This is because it is super simple. You do NOT have to know C to follow. You can also follow the steps with your own already existing project.

I PROMISE you, GIT cannot hurt you. Worst case scenario is that you fiddle around and break the repository part. (Meaning the files in the .git folder). But your files will always be safe.

(If you do not have git installed, check out part 3 for that)

First, I make a folder, navigate my shell into it, and call git init:

By the way, you can get used to GIT messages like this that tell you all your options, and explain what GIT has done for you. GIT is very good about giving you as much help and info as possible,

Now I will teach you the most important command in GIT.

It is more important than any other. Ready?

git status

This makes GIT tell you what git thinks is happening right now. What issues there are and what files are tracked, untracked or have been changed. Use this command often, especially while you are new to GIT, run it after every other command. It is how you learn what GIT is doing and thinking :3

Since our repo is empty it tells you what branch you are on (master. The only branch we will need since we are working alone)

and that you have not made any commits.

It also tells you the commands git think you will want to use on files. Since our repository is empty, it tells us to create some files, and then how to add them :3 So let's do that:

I have added my tiny program, as you can see:

Now let us see what GIT thinks we did:

Now, since there have been changes, git shows us them.

Files can be untracked tracked and not changed (In which case, git status does not show them) tracked and changed.

Right now, main.c is untracket. Which basically means GIT have no idea about this file, other than it is in the folder.

Ok, let us commit(save) the file. GIT tells us this is done with git add <File> . So we will write git add main.c

Then we use git status again to see what happened git status

And yeah, our file is now ready to be committed. So lets do it! git commit -m “My first commit!”

The “-m” option is to write the git update explanation directly in the console instead of using an external program to do it. Done You have now committed your code! It is now saved!

git status shows that everything in the working tree is as it was last time we committed (Duh. We JUST committed)

I will now make some changes to the main file:

Git status shows us main.c was changed...but what if we wanted to know what was changed in more detail? How will we get status to do that for us? Let us find out! git help status

git then shows the help page for status And there we can see this part:

So if we write status with 2 -v arguments, we get all the details. Let us try:

And look! It shows us EXACTLY what lines were changed! I stage the changes and commit:

And you have now learning enough about GIT to use it.. You now have all your work saved, in different commits. If you ever want to know all the commits you have made, write git log:

And if you want to know what a specific commit did, you copy the name of the commit, and write git show:

Now, everytime you want to save your work, you

1: Write/change the files you want

2: Add the files you want as part of this commit

3: make the commit These three steps are your workflow.

If you have a remote repository, then you add them steps

4: push to remote repository

To do this step, you can actually just write

git push

Hello, 😊

Today I started a new practical project, the last of from the foundations of "The Odin Project". It consists in building a calculator for the browser.

I didn't do much today, I just build some basic logic from the calculator, created functions for each operation (+, -, *, /) and a basic HTML page with buttons for each number to build the number as we type.

Since you can type a number only between 0-9, to assembly the entire number, I have to multiply the previous typed by 10 and then sum the new typed.

Like, if I want to write "12", I first type "1" and when I type the "2", I need to first multiply the one by 10, now I have "10", and can just sum the "2" to form "12". And I do the same process for every new number typed.

Also, I use the bubbling event, so I don't need to create an event listener to every button. I only create one for a higher level element that the buttons are nested inside, and then check which button was clicked by looking at its id. The bubbling event is so useful!

That's it 😵‍💫. I probably won't post this weekend, because Sunday I have an exam and won't have time to study programming 😭😭.

pltk now has a new api called pltk-basic and it's the first layer of abstraction of pltk. the pltk-basic api will make it so that you don't have to worry about knowing the event device that maps to the pointer or the keyboard. it's the lowest you can go while still being fully platform-independent (api below)

and this is the current state of the pltk-basic subsystem :3

yup, this thing looks like a weird minimal xorg server install, but it's internally structured like a wayland compositor with no vsync :3

sadly, it seems that my input post-processing of the mouse has broken the keyboard input and the mouse buttons, because the original pltk-test grabs keyboard input and the mouse buttons just fine. the most confusing part is that the input post-processsing for pltk-basic-test is an expanded version of the pltk-test variant, and i didn't really change much

Wednesday 13th September 2023

I've officially kicked off the #100DaysOfCode challenge, and I owe my inspiration to @hayaway post about the 110 days left in the year. Working on my skills and the list I made earlier of what I want to study before the year ends sounded too good to pass up. Day 1was me just on the FreeCodeCamp's C# course - I've set a daily goal to complete a section of the course~! Probably take 30 mins a day, which is fine!