Denis' Micro Blog

What's up, everybody.

Hope you're doing well today. ❤

Well. I think I made my point in all of my previous blog posts clear. I am a Software Developer. That should shock exactly no one at this point.

One thing that we developers do is use something called a Source Control System (in short SCS).

What is that, some of you may ask right now. Working on source code in larger groups can be a pain in the ass when it comes to collaborating on the same source code files. Organization between those developers can fail. Everybody is one a different state. Chaos ensues, and everything collapses. We don't want that. So that's why we use SCSs.

They help us manage that organize that mess inside a central repository, from which different users can make changes or commits, and then others can pull the current state by just referencing the latest commit. This way everybody's on the same page.

It gets even better though. 😁

By using these commits we create a "timeline" of the different changes we can jump back and forth to.

Basically like using one of these bad boys. Okay... It's an enter key but still...

I think you get the idea and how useful that may be.

Okay... Great thing you got there, dumbass. But what's going on with the title?

Great question. (which I definitely didn't craft before...)

Think about it for a second. Source code isn't that different from everyday documents "normal" people use. It's still (weird) text inside a standard text file. (with a special file type)

So there isn't really a restriction on the files, file encoding, or file content you can use.

So... We can use it for not only source code but other files we encounter in our everyday life.

Let me give you a few examples.

Ever noticed how a few tools, programs, or learning thingies can export user settings or your personal progress inside a text file? Source-control it to back it up and have a way to revert to an earlier state. A backup on steroids. 😉

Documents. Well. Documentation in software development is quite frequent. Or at least it should be more frequent... Doesn't matter what you got. Plain text, Markdown, LaTeX, and even Word documents. They all work.

Or graphic design. Very useful if multiple people are working on something together. This way you have always the "progress" of your finest pieces of art tracked.

Honestly, there are so many uses for SCSs, and I haven't even mentioned stuff like Continuous Integration and Automated Build processes to generate final versions of something. Like a PDF file from a LaTeX document. Or the final executable from source code, as it was initially intended. 😅

As you can see, the possibilities are endless, sunshine, rainbows, and unicorns await you, as well as a 73,69% increase in productivity. Warning: Advertised benefits may vary from real outcomes. I am not responsible for diminished outcomes and no payouts will be made in this case.

So... Source-Control everything, I guess. What are you waiting for? Do it.

See ya.