FINALLY Got Done With The Beginners Guide To GIT

FINALLY got done with the Beginners guide to GIT

So a long time ago I made a poll to help me make a Begginers guide to GIT because a lot of people seem to have trouble with it. https://www.tumblr.com/moose-mousse/722172571753365504/going-to-make-a-getting-started-with-git-post?source=share

And I know for a fact that my University taught it horribly. (Or rather... did not teach it at all)

I REALLY tried making this guide as short as I possibly could. Explaining only what you need to know, while trying to clarify what most people find confusing. But it still is too long for a single post. So, I have split it into 5. The post each links to each other, so you should be able to go back and forth easily.

This guide is going to be pure GIT done via the command line. 2 reasons for this:

1: GIT GUI’s are really handy, but they abstracts away a lot of the newbie help GIT is trying to give you. Bitbucket, Github, Jira, and other services use GIT but usually add extra bits that are specific to them. So to know how they are different, it is smartest to learn pure GIT first. And since they are 99% GIT, you will be able to use them with no/little trouble.

2: Because I use the command line, it is easy to build your own automation tools. Simply have a program write git commands to the shell and/or read outputs from git commands and use them to visualize whatever you want, however you want. That way you can have whatever shiney graphics your heart can code up. All the tools you can find (Like Github desktop or gitk) are simply doing this. (incidentally, if any of you make a pretty visualization of GIT? Show me! I wanna see a dog themed GIT graph! I wanna see pink log outputs! Make it yours!)

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

Part 2: Definitions of terms and concepts

Tumblr

A beginners guide to GIT: Part 2 - Concepts and terms

Table of content: Part 1: What is GIT? Why should I care? Part 2: Definitions of terms and concepts. <-------- You are here Part 3: How to

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

Part 4: How to use GIT as 1 person

Tumblr

A beginners guide to GIT: Part 4 - How to use GIT as 1 person

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 in

Part 5: How to use GIT as a group.

Tumblr

A beginners guide to GIT: Part 5 - How to use GIT as a group.

Table of content: Table of content: Part 1: What is GIT? Why should I care? Part 2: Definitions of terms and concepts. Part 3: How to lea

So starting a 4 week internship tomorrow...

My info is: Show up at 8:30, and I will help on a project to test a better method for time-stamping sonar data with time from GPS units on boats ( Well, GNSS.)

That... Is all. No clue what languages or what tech stack... protocols... system diagrams...

How did they do it before? If you have GNSS data then... you are pretty much as good as you will get... Nothing beats atmoic clocks in space, which are further calibrated with atomic clocks on the ground...So they did not use GNSS before? Why not?

Like, they know I am uninformed, but... I try to make myself calm by researching and testing stuff ahead of time... So yay massive anxiety.

Oh well... Nothing for it but showing up and doing my best.

Ha Ha!

I did it! I got up at 3 AM to start working before going into work at 8 and I managed to do good during the code review!

I managed to teach the apprentice a good chunk of stuff embedded and C++. ( Static_cast, Steongly types enums, rule of 0/5, system clock running backwards and a bit more ) AND I managed to know a few things that my supervisor had not run into before! ( One of which was Godbolt existing... which confuses me, but oh well ).

I also picked up a bunch of good stuff (For example, I realized I was still thinking in terms of microcontrollers and so had not thought about how the fact that main() takes arguments influences the code architecture)

Now my brain is mush but I do not care! It went well! I can do this!

AHHHH!

Have to do a code review of a codebase I have had access to for 2 days... by copy... As in, I do not yet have access to the reposetory, as so cannot build the project... And so none of my tools work on it... Because massive anxiety an autism, and my supervisor asked if it was ok to have it today (Friday), rather than on Monday and so my mouth just said the words it figured the other person in the conversation wanted to hear... I do not have access to the internal communication tools either so... juuuust have to do it..... AHHHHHHHHH! I swear... I am so happy I went on tumblr, because I am just using the "Do it alone, do it scared" as a freaking mantra at this point...

(Also, sorry for not answering people or being super active... I am just focusing as much as I can on this internship)

I must admit I dislike posts like this.

What AI made that? Because they are getting GOOD, and showing examples from bad or old AI's work is... very close to lying.

And it is not reaching human level GAI that is the big danger.

Nor is it how the content creation industries are using them (IE, to strip copyright away from smaller creators IP), although that is bad.

The BIG danger is that WE CANNOT TEST THEM. It is called the alignment problem. It basically means that when we run these machine learning algorithms in test environments, they can and will be working wrong, and we cannot detect it. There have been global competitions to design tests, tools and guides for detecting such misalignment while they run in test environments, and so far, the success rate is 0%. A few handful of ideas have been brought forth, and none of them have worked so far. And that is with really simple machine learning algorithms solving really simple problems that we know the solution to. And THOSE we cannot make safe. The first real test that shows anything, is when they are being run in real life. And we are NOT using these machine learning algorithms on problems we know the correct answer to, and so would at least be able to check when they run in real life. We are using them on problems we do NOT know the answers to. And then we pray that they are correct, and that they do not have any horrible hidden side-effects. And it is just hope. Because there is no way to find out. And these AI run the entire stock market. They run Healthcare, they determine if you can get insurance, they analyse job applicants, they guide police, they calculate your credit score, they control the electrical grid. They are being put into any and everything. These untestable AIs are being put in basically all of our infrastructure. It is not that they are not tested, it is that they CANNOT be tested. Any firm using machine learning algorithms claiming that they are tested and safe either do not know anything about machine learning algorithms (Which would be horrifying) or are lying (Which would be horrifying). They are not following good guidelines, because no such thing exist. They are not measuring to make sure the algorithms are safe, because such a thing is beyond the best researchers in the area.

And near all AI safety experts are BEGGING us to slow down. We have NO idea what is happening, and bad people wanting to make money is claiming that means there is nothing wrong.

"AI will kill us all!", they say, "You can't even be certain if you're texting with a human or an AI", they say.

Meanwhile, the AI:

(im not saying that human level AI is impossible, just extremely far away and that the current hype is mostly unearned)

WOOOOOOO!

IF ALL GOES WELL IM GETTING TESTOSTERONE SOON

That's amazing! Big congratulations! I really hope everything goes well so that you can get started on it soon! ❤️

I love GDB (Gnu debugger). It is only useful when something have gone wrong, but GDB just makes it sooooo much easier to find the issue. The picture is of a particularly deep stack. It is a short overview of every stack-frame, and where in the code it was called from, and to what. I can also easily investigate every single stack frame alone, finding what each variable contained the moment the crash happened, what arguments each function took, and the memory position of every single element. By the way, to run this, all I did was: gdb ./build/MyAwesomeProgram run bt

If you work in C or C++, it is SUCH a handy tool to know. And it is pre-installed on basically every machine.