#Git code management

[redactedconcepts]

Source code management

What is source code management?

It allows a developer to organize code iterations chronologically, and version it for an application. The most powerful features of source code management systems are in how they allow teams of very diverse sizes to work together on the same application simultaneously.

Some terms that are common to all of them:

A project will be called repository, it’s representing the index/the filesystem root of your project.

Developers might create branches of the codebase, that they will iterate on separately to other developers. For instance, a branch can be meant to be used for a given feature, or a given bug fix. One can create however many branches they need.

Once a branch is ready for it (it’s been tested, peer-reviewed, etc.), it can be merged back to the main branch. The main branch may be called differently: in Git it’s called master , in SVN it’s called trunk.

While coding on their branch, developers are meant to work in small, atomic iterations, called commits. All commits have a commit message describing in one sentence what’s in there.

All commits together are called the history , and it’s a big deal to write meaningful commits and commit messages in order to keep the project’s history clean at a glance, to understand what has been going on and who did what.

Some people might be modifying the same pieces on the codebase on different branches, and this could create conflicts when one merges those branches together. Some of those conflicts can obviously only be fixed by a human, and each system has a different way to manage merge conflicts.

Which systems exist?

I’ll put each specific wording between quotes. The same words may be used for differing notions across the various products.

SourceSafe was an early source code management system from Microsoft, which didn’t handle branches, merges, or conflicts. You could “check out” a file, which meant no one else was allowed to “check it out” and modify it at the same time. When you were done with it, you could “check in” the file, making it editable again to the others. Not very suitable for large teams that may work on the same file, and longer iterations in a given file. SourceSafe is discontinued today.

CVS was among the first open-source source code management systems in the industry, and used to be wildly popular, but is barely seen anymore. It didn’t handle branches, but two people could modify the same file at the same time. People would “update” their whole directory to get everybody else’s work before starting, and “commit” their code to the server when they’re done. When they would “commit” a file that had been “committed” by someone else since last time they “updated”, the system was not able to merge, so it would consider it a conflict every time, that you would have to manually fix (even if the changes were not on the same lines, for instance).

SVN was built upon CVS to handle branches, so a lot of terminology is the same. At some point, it was the most used system, and it is still seen in the industry, even though people are walking away from it. When you’d create a branch, it would actually copy-paste the whole codebase into another directory in the code repository; then, you’d try to merge, and it would massively compare each file one by one. Merging algorithms were smarter than the CVS ones, but you still had conflicts on most merges, even those that shouldn’t necessarily require a human. When you’d create a “tag” (which is a set version of your code, like “1.2.0”), then the whole codebase would simply be massively copy-pasted into another directory too, but without the intention to merge it back later.

Git doesn’t copy-paste the whole codebase when branching and tagging, but stores each commit as a code iteration, in an organized structure that resembles a tree. This allows it to have a much smarter merging algorithm, and it almost never bothers you with conflicts, except for those that really need a human decision. As a result, the cost of branching/merging is very low, and people typically branch/merge a lot, therefore one should never directly work on the “master” branch, if they’re not the only developer on the project. Also: unlike its predecessors, Git allows to work and commit without needing to talk with a server, which allows to work on planes, for instance; and it also can work as a decentralized (peer-to-peer) system, although it’s very rarely done that way.

Mercurial is very similar to Git in its concepts (although the syntax of its command-line tool is often different). It is more rarely seen in the industry than Git, but is still very relevant. It is the one used by Facebook, for instance, for its main application.

The lowdown on Git

A particularity about Git, is that it’s designed to be useable without a central repository (you can pull code from your friend’s computer, and push you work back there, for instance), but not many people use it that way. There is usually a central Git server that the whole team pushes code to and pulls code from; however, that explains why it is often referred as a “decentralized” system.

So that you can work without a server, the commit operation is local, no one other than your computer knows you committed something. You can make several commits however you want, but when you want the server to know about it, you must push them there. You want to be pulling from the repository often if other people may be working on the same branch as you, because each pull performs a merge operation between the code you didn’t have, and the code you recently committed locally. Therefore, in order to let you push , Git will sometimes demand that you pull first, so that the merge can be done on your computer, and you take care of potential conflicts.

Sometimes, you may have modified 3 files, but there are only two that you wish to include in the commit you’re about the make. Therefore, Git has a notion of “ index”, in which you add your modified files so that they’re included in the next commit you register.

How to configure the remote servers your local repository is talking to? They’re called remotes , and you can configure however many you need. The main one is typically named origin (that’s the name that is setup by default when you clone a project from a remote location in the first place). You can also configure however many branches you need, and name them as you please, and the default one is usually called master.

Some UI tools for Git exist, but Git is able to do so many things, that they don’t represent the magnitude of cases for which you need Git. You really want to learn to use it with the command line. Here are some commands:

$ git clone url_of_your_remote_repository # Clone a repository from a remote repository $ git add file1 file2 # will add those two files to the index if they were modified $ git commit -m "Meaningful commit message" # will commit those two files (locally) $ git add . # will add all of the modified files to the index at once $ git commit -m "Other meaningful commit message" # will commit all of those files together $ git push origin master # send all commit to the remote server

Now, let’d do this again, but by on a branch:

$ git branch my_feature # Creating the branch $ git checkout my_feature # Changing the codebase so that we're on that branch now $ git checkout -b my_feature # This does the two previous operations in one ;) $ git add file1 file2 $ git commit -m "Meaningful commit message" # We didn't just commit this on the master branch like last time, but on the my_feature one $ git add . $ git commit -m "Other meaningful commit message" $ git push origin my_feature # Notice, we're not pushing master anymore, you just create a new remote branch

Next time you want to work on that branch, you should probably do this first:

$ git checkout my_feature # Just making sure you're currently on the right branch! $ git pull origin my_feature # Pulling what your coworkers have done so far.

And when you’re done with the whole feature and want to merge it to master:

$ git checkout master $ git merge my_feature

One other pretty neat thing: if you have a non-Git directory in your computer, and you want to turn it into a Git repository, it’s that easy:

$ git init # You're done! $ git remote add origin url_of_your_git_server # So that you can push your code somewhere.

When you’re in a Git repository, and want to know which files are modified but not in the index, and those that are modified and are in the index, you can run:

$ git status

Git provides many more abilities, such as rewriting pieces of the history of the project if you feel the commits were not meaningful enough, displaying the history in visually meaningful ways, …

For instance, you should run this right now, and see how a complex history can be viewed really nicely:

$ git clone [https://github.com/loverajoel/jstips.git](https://github.com/loverajoel/jstips.git) # You will need a GitHub account for this to work $ cd jstips # changing your directory into the one you just downloaded $ git log --graph --pretty=tformat:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%an %cr)%Creset' --abbrev-commit --date=relative

Cool, right?

What is the difference between Git and GitHub?

Git is everything we’ve covered so far: a source code management tool, that comes with a command-line tool for its users.

GitHub is one of many services that provide at the same time:

a Git repository server to push your code to

a web UI to that view your repositories, with their files and commits

a number of extra features (managing your team and accesses, …) Two GitHub features you have to get familiarized with are:

Forks : you can fork any repository on GitHub, and it will duplicate the repository’s codebase into repository that you own. For instance, if you fork twbs/bootstrap, and your GitHub username is “my_username”, then it will create the my_username/bootstrap repository, and it will remember where it was forked from. Usually, you aren’t allowed to push on other people’s repositories, so that will give you a repository that you can push to, since you own it.

Pull requests: once you’ve pushed your code to your repository (or sometimes to a branch of the main repository, if you’re allowed), then you can create a pull request towards the main repository’s master branch. Somebody in charge of the main repository will review your pull request (potentially asking you to change a couple of things), and merge it if it’s suitable to be in the main product.

GitHub has many competitors, two of the main ones being GitLab and BitBucket (which provide very similar services). We chose to make you use GitHub because that’s where most of the industry is (that way, you’ll be able to interact with them on their open-source projects), and it’s also where tech recruiters typically go check out to see what you’ve been up to.

Some interesting links about Git

https://try.github.io: an interactive tutorial for beginners.

https://help.github.com/articles/good-resources-for-learning-git-and-github/: a list of resources about Git, curated by GitHub.

http://nvie.com/posts/a-successful-git-branching-model/: once you master the technical tool, you have many ways to organize your branches according to your project. This very notorious article from 2010 introduces git-flow , a detailed proposal for organizing collective work with Git that is still the most common today. You should talk about that each time you start a collaborative project using Git.

http://semver.org: now that you can give version numbers to your code iterations, how should you number them? Semantic versioning is the most used versioning scheme.

Git from the inside out

Learn git branching

[virtualizationhowto]

Docker Development Environment: Test your Containers with Docker Desktop

Docker Development Environment: Test your Containers with Docker Desktop #homelab #docker #DockerDesktopDevelopment #SelfHostedContainerTesting #DockerDevEnvironment #ConfigurableDevelopmentEnvironment #DockerContainerManagement #DockerDesktopGUI

One of the benefits of a Docker container is it allows you to have quick and easy test/dev environments on your local machine that are easy to set up. Let’s see how we can set up a Docker development environment with Docker Desktop. Table of contentsQuick overview of Docker Development EnvironmentSetting Up Your Docker Development Environment with Docker Desktop1. Install Docker Desktop2. Create…

[barpsy-abaub]

Da New Boss!

Lord Inquisitor! It is with great regret that I inform you that the research group you sent to the planet 09-76C was attacked by xenos. Part of the group was captured by orks; may the God-Emperor have mercy on their souls. Fortunately, two weeks after they disappeared from the radars, we managed to intercept a fragment of the broadcast from the BONE implant of one of the captive ogryn bodyguards. We'll continue to try to determine the coordinates of the broadcast source. I have attached the translation of the broadcast to this message, in case you are interested in it. God-Emperor be with us.

RECORD: 09-76; code: BONE 56-533

"…Listen, boyz! Da Nob Humie iz dumb az squig, but iz Big. Da Smart Gobllo iz smol, but is Smart! Humie listens to us. Humie can be manni-pula-tid! Gobllo 'll make da Nob Humie da Boss, 'll make him orky and green, and no one 'll dare to stomp us grotz like dhey did before with such boss! We'll be stomping dhem all insted!"

"…Hey, you git! Stop chopping dis fing on 'is head, it may be…"

[sleyu]

thinking about meanbf!sirius <3 visits you at work only to fuck you in the staff bathroom <3 speaks to you in french while you fuck because he knows you won’t understand what he’s saying and it makes you teary eyed <3 i love him so much PLEABS!!!

stop stop do you know how delusional this is making me . . . this is all i’m gonna think about when i’m at work.（；＿；）♡

i can picture him visiting you at work, maybe to pick you up after your shift ends, and him narrowing his eyes at one of your male coworkers that's being a little too close for comfort. when sirius comes up to you to take you home and your coworker protectively stands in front of you, he just stands there, feeling shocked for a brief moment, sneering before softening his eyes at the sight of you stepping towards him and hugging him tightly.

maybe it was the presence of your coworker entirely, or maybe it was the coworker asking you if sirius was simply your friend that made him want to steal you away every time you went on a break to fuck you stupid.

suddenly, sirius didn’t just visit your workplace to drop you off or pick you up. he began forcing you to text him the time you went break so that he could drag you to the staff bathroom for a nice, “quick,” 30-minute fuck. he practically has the bathroom code memorized with how many times he’s fucked you in it.

he would sit there for a while, clicking his ring-clad fingers against the table, bouncing his knees—doing anything to relieve him of his impatience. sirius would silently reel at the apprehension written all over your face and the flush on your cheeks as your coworkers or customers would speak with you. upon your break beginning, you could barely manage to kiss your boyfriend on the lips before he yanked you away to the employee bathroom.

‘why does he have to touch you so much, hm?’ he’d mutter bitterly, hastily lifting your skirt and pushing your panties to the side, simpering at the slick on his fingers as he dragged his fingers up your slit, slowly circling his middle finger over your gushing hole. ‘just touching you for no good reason.’

you would furrow your eyebrows at the agonizing feeling and hum in agreement with the man behind you. the hard porcelain of the sink was pressing painfully against your hips and your heart was beating rapidly, your mind only praying that people at work hadn’t caught on to the employee bathroom being occupied for thirty whole minutes nearly every day.

‘don’t know, siri,’ you’d mumble while sighing breathlessly, feeling flush at the sight of sirius staring at you intensely from the washroom mirror, studying your facial expressions while smiling in amusement at your bashfulness.

sirius would smile broadly at the sight of you sinking your teeth into the back of your hand, a useless and insufficient attempt in muffling your cries as he hammered into you from behind, watching you take the extra step to turn on the sink faucet to conceal the loud, echoing sounds of skin slapping as he thrust into you. he would exhibit a shit-eating grin, lazily staring at your eyes welled up with tears of humiliation at the lewd, moist sounds of you creaming around his cock with each rut.

sirius’s pace is unforgiving and relentless, and all the while, he would tug on your hair to jerk your head back so he could bite and suck on your neck, leaving bruised, mean marks along the side of your throat that he makes certain will show.

‘sluts like you love getting fucked in places like this, huh? just imagine what they’d think—your little friends,’ sirius breathed shakily, feeling his mind go numb at the feeling of your drenched cunt pulsating around his thick, throbbing cock.

‘does that git know what a fuckin’ slut you are for me? does he know that this cunt gets filled up every second of every day?’

‘‘s like you can’t get enough—fuck—i’m sure he can’t fuck you like this—oh—satisfy all your needs like me, yeah?’

sirius is the epitome of mean and truly does not give a fuck about what anything else thinks. he would purposely pull your hand away from your mouth, letting your moans spill uncontrollably from your mouth, echoing inside the enclosed space of the washroom.

he wants that “fucker”—according to sirius—to hear the way you lose your mind with his cock inside you. sirius would only laugh softly at the sight of your head dropping helplessly, tears spilling down your cheeks, lips parted with pants escaping them at the feeling of his cock brushing against the sweet spots inside your cunt.

‘need more. i don’t think i have enough time, sirius,’ you’d mewl. ‘please go harder.’

sirius would not care if this was cutting into your work time but he’s more than happy to fuck you harder and faster. he’s not stopping until he’s pleased and you're fucked out—eyes rolling back, and throat worn out from your loud moans. he could care less if your break was finished or if someone was banging on the door, begging to use the washroom—he’s finished when he’s finished.

‘cunts taking me so well, i’m definitely not stopping. ‘n i’m sure my girl doesn’t want me to either—not when you’re so close, yeah?’

and speaking of him talking to you in french . . . he knows you get off to his dirty talk, so him speaking in a language you can’t understand—hearing how you whine at the feeling of being unaware of his thoughts and his words only make the knot in his stomach tighter.

secretly, sirius is mumbling cheesy shit like, ‘i love you,’ or ‘you’re so pretty,’ to save himself from the embarrassment of saying soft things so contradicting to his fronting personality.

also, this is sirius. we all know that he’s working to the fucking bone to make sure he cums inside you and that his seed is buried deep inside your tight little cunt. without a doubt, he’s saving a little bit of his cum for your panties, cumming all over them, dampening the cotton fabric so that when you put them back on after getting dressed, your cunt would be stained and sticky from his seed, leaving you uncomfortable all day at the feeling of your wet, soiled underwear.

i think, if we are truly wanting to appreciate and hate the essence of mean bf ! sirius, i fear that he’s gonna pull out of you the very last second, when your one thrust away from cumming, watching and reeling as you sob at the lost contact, unconsciously wiggling your bum to entice him to take you again and help you find your release. he needs to make sure your cunt aches and longs for him, yearning the feeling of his long cock thrusting inside relentlessly.

‘no—fuck—please, sirius!’ you’d sob, shoving your head against his chest and hitting him weakly with your fist. ‘feel so empty, siri—please. it hurts so bad.’

sirius almost succumbed at the sight of your trembling pout and your longing, teary eyes. unfortunately, he persevered against temptation and pressed a gentle, tender kiss on your temple before pulling away and helping you get dressed again. he would coo and wipe away your tears, laughing to himself at the sight of your glare and your thighs rubbing against each other in an attempt to find relief and ease your aching, empty cunt.

‘when i pick you up, puppy,’ he’d pull you into a deep kiss, firmly gripping the back of your neck. ‘i’ll fuck you and make you cum as much as you want. good girls wait, yeah?’

[codingquill]

Welcome back, coding enthusiasts! Today we'll talk about Git & Github , the must-know duo for any modern developer. Whether you're just starting out or need a refresher, this guide will walk you through everything from setup to intermediate-level use. Let’s jump in!

What is Git?

Git is a version control system. It helps you as a developer:

Track changes in your codebase, so if anything breaks, you can go back to a previous version. (Trust me, this happens more often than you’d think!)

Collaborate with others : whether you're working on a team project or contributing to an open-source repo, Git helps manage multiple versions of a project.

In short, Git allows you to work smarter, not harder. Developers who aren't familiar with the basics of Git? Let’s just say they’re missing a key tool in their toolkit.

What is Github ?

GitHub is a web-based platform that uses Git for version control and collaboration. It provides an interface to manage your repositories, track bugs, request new features, and much more. Think of it as a place where your Git repositories live, and where real teamwork happens. You can collaborate, share your code, and contribute to other projects, all while keeping everything well-organized.

Git & Github : not the same thing !

Git is the tool you use to create repositories and manage code on your local machine while GitHub is the platform where you host those repositories and collaborate with others. You can also host Git repositories on other platforms like GitLab and BitBucket, but GitHub is the most popular.

Installing Git (Windows, Linux, and macOS Users)

You can go ahead and download Git for your platform from (git-scm.com)

Using Git

You can use Git either through the command line (Terminal) or through a GUI. However, as a developer, it’s highly recommended to learn the terminal approach. Why? Because it’s more efficient, and understanding the commands will give you a better grasp of how Git works under the hood.

GitWorkflow

Git operates in several key areas:

Working directory (on your local machine)

Staging area (where changes are prepared to be committed)

Local repository (stored in the hidden .git directory in your project)

Remote repository (the version of the project stored on GitHub or other hosting platforms)

Let’s look at the basic commands that move code between these areas:

git init: Initializes a Git repository in your project directory, creating the .git folder.

git add: Adds your files to the staging area, where they’re prepared for committing.

git commit: Commits your staged files to your local repository.

git log: Shows the history of commits.

git push: Pushes your changes to the remote repository (like GitHub).

git pull: Pulls changes from the remote repository into your working directory.

git clone: Clones a remote repository to your local machine, maintaining the connection to the remote repo.

Branching and merging

When working in a team, it’s important to never mess up the main branch (often called master or main). This is the core of your project, and it's essential to keep it stable.

To do this, we branch out for new features or bug fixes. This way, you can make changes without affecting the main project until you’re ready to merge. Only merge your work back into the main branch once you're confident that it’s ready to go.

Getting Started: From Installation to Intermediate

Now, let’s go step-by-step through the process of using Git and GitHub from installation to pushing your first project.

Configuring Git

After installing Git, you’ll need to tell Git your name and email. This helps Git keep track of who made each change. To do this, run:

Master vs. Main Branch

By default, Git used to name the default branch master, but GitHub switched it to main for inclusivity reasons. To avoid confusion, check your default branch:

Pushing Changes to GitHub

Let’s go through an example of pushing your changes to GitHub.

First, initialize Git in your project directory:

Then to get the ‘untracked files’ , the files that we haven’t added yet to our staging area , we run the command

Now that you’ve guessed it we’re gonna run the git add command , you can add your files individually by running git add name or all at once like I did here

And finally it's time to commit our file to the local repository

Now, create a new repository on GitHub (it’s easy , just follow these instructions along with me)

Assuming you already created your github account you’ll go to this link and change username by your actual username : https://github.com/username?tab=repositories , then follow these instructions :

You can add a name and choose wether you repo can be public or private for now and forget about everything else for now.

Once your repository created on github , you’ll get this :

As you might’ve noticed, we’ve already run all these commands , all what’s left for us to do is to push our files from our local repository to our remote repository , so let’s go ahead and do that

And just like this we have successfully pushed our files to the remote repository

Here, you can see the default branch main, the total number of branches, your latest commit message along with how long ago it was made, and the number of commits you've made on that branch.

Now what is a Readme file ?

A README file is a markdown file where you can add any relevant information about your code or the specific functionality in a particular branch—since each branch can have its own README.

It also serves as a guide for anyone who clones your repository, showing them exactly how to use it.

You can add a README from this button:

Or, you can create it using a command and push it manually:

But for the sake of demonstrating how to pull content from a remote repository, we’re going with the first option:

Once that’s done, it gets added to the repository just like any other file—with a commit message and timestamp.

However, the README file isn’t on my local machine yet, so I’ll run the git pull command:

Now everything is up to date. And this is just the tiniest example of how you can pull content from your remote repository.

What is .gitignore file ?

Sometimes, you don’t want to push everything to GitHub—especially sensitive files like environment variables or API keys. These shouldn’t be shared publicly. In fact, GitHub might even send you a warning email if you do:

To avoid this, you should create a .gitignore file, like this:

Any file listed in .gitignore will not be pushed to GitHub. So you’re all set!

Cloning

When you want to copy a GitHub repository to your local machine (aka "clone" it), you have two main options:

Clone using HTTPS: This is the most straightforward method. You just copy the HTTPS link from GitHub and run:

It's simple, doesn’t require extra setup, and works well for most users. But each time you push or pull, GitHub may ask for your username and password (or personal access token if you've enabled 2FA).

But if you wanna clone using ssh , you’ll need to know a bit more about ssh keys , so let’s talk about that.

Clone using SSH (Secure Shell): This method uses SSH keys for authentication. Once set up, it’s more secure and doesn't prompt you for credentials every time. Here's how it works:

So what is an SSH key, actually?

Think of SSH keys as a digital handshake between your computer and GitHub.

Your computer generates a key pair:

A private key (stored safely on your machine)

A public key (shared with GitHub)

When you try to access GitHub via SSH, GitHub checks if the public key you've registered matches the private key on your machine.

If they match, you're in — no password prompts needed.

Steps to set up SSH with GitHub:

Generate your SSH key:

2. Start the SSH agent and add your key:

3. Copy your public key:

Then copy the output to your clipboard.

Add it to your GitHub account:

Go to GitHub → Settings → SSH and GPG keys

Click New SSH key

Paste your public key and save.

5. Now you'll be able to clone using SSH like this:

From now on, any interaction with GitHub over SSH will just work — no password typing, just smooth encrypted magic.

And there you have it ! Until next time — happy coding, and may your merges always be conflict-free! ✨👩‍💻👨‍💻

[dolconfessionsss]

Devil here again! Thanks a lot for your answers! Yeah, I'm basically on the opposite side of escapism where I try to torture myself with every media I engage with. It's a rather unique way of engaging with media and it worries some. But It's what I enjoy. I try to learn and compare and engage with most media like I would philosophy. There is a **LOT** to do about the game. Lots of big things need updates, reworks, etc, one of which is the combat system that's being worked on too. The Baileys daddy-issues thing taken out of context is far worse than what it actually is. Inside the server basically all the Bailey fans are well aware that fatherly issues are a large draw towards characters like Bailey, Eden and even Avery. A friends server I'm in even uses custom stickers for "Daddy Issues Club". The Abortion thing, yeah, it's hard to properly explain things to many different people many different times and attrition just wears down peoples energy and drive, so sometimes things just start getting brushed off and hit with a "No because we said so." The Evilness and Rudeness has toned down a lot, some still remains but that is in general part of the culture, I've become well aware I can't be that way to everyone and to better read the room. The thing about peoples social media I've stopped doing. Yeah it's public but still, I'm an admin, this is a big server, it's just rude. Instead we've started DMing people we see with a lot of linked accounts or if we see private info on them to alert them in private that they might be in danger of people seeing things they don't want seen. Puris aesthetic is very much yellow and angel based, but yeah, no self-inserts in DOL. We are very much against that given the themes of the game. Sydneys whole thing is that their fate is decided by others. They are rather spineless and the Temple has dictated their entire life up until they met the Player/PC. At that point now Sydneys life is in the players hands. But no matter what we as the players do Sydney is doomed to a life of danger and pain. When it comes to contributions they are reviewed and approved by Contribution Managers which are trusted and experienced individuals. These CMs talk to people, teach them, give them notes on how to edit scenes. Once these scenes are completed and reviewed they are put into the pipeline to be coded into the game by our Coders. They send Merge Requests to the Git, where these merge requests are usually checked once more and then approved by Puri or Vrel and such. Before all this it was far easier for people to sneak things in. Edens OOC soft content, Trans-Coded Robin content, basically **ALL** of Morgan and his...incestious rat-eating.

Ooh, a rework on the combat system? 👀✨ Now that's something I would genuinely look forward to, since I built a story of my PC being a kind of fighter who plays filthy dirty hehehe >:)

Once again I have to ask: no Mommy Issues Club? 🥺 In all seriousness, it does tells about the fandom - or at least the server specifically - that there's more emphasis on problematic fatherly figure than motherly ones :0c

Oh yes, exactly one-on-one with how I view Sydney's whole character <3 They have absolutely no control over their own life, they are just switching control from the Temple to PC. What an absolutely self-destructing cutie, I love them so much 💖✨

The contribution system sounds really interesting! How are the Contribution Managers chosen? Were they handpicked personally, or were there application out for anyone to apply for it? And now I have to ask: from the sound of it, Morgan's everything is a mess. How did their character got so 'bad' to this point? I feel like Eden's Soft OOC-Ness and Robin's Trans-Codedness (appearently? Never notice that huh) doesn't seem as bad as Morgan?

Also wait, Trans-Coded Robin moments? I am probably just blind but I'd love if anyone can point out what these moments are because I do not notice any of them 👁👄👁

[souhaillaghchimdev]

How to Build Software Projects for Beginners

Building software projects is one of the best ways to learn programming and gain practical experience. Whether you want to enhance your resume or simply enjoy coding, starting your own project can be incredibly rewarding. Here’s a step-by-step guide to help you get started.

1. Choose Your Project Idea

Select a project that interests you and is appropriate for your skill level. Here are some ideas:

To-do list application

Personal blog or portfolio website

Weather app using a public API

Simple game (like Tic-Tac-Toe)

2. Define the Scope

Outline what features you want in your project. Start small and focus on the minimum viable product (MVP) — the simplest version of your idea that is still functional. You can always add more features later!

3. Choose the Right Tools and Technologies

Based on your project, choose the appropriate programming languages, frameworks, and tools:

Web Development: HTML, CSS, JavaScript, React, or Django

Mobile Development: Flutter, React Native, or native languages (Java/Kotlin for Android, Swift for iOS)

Game Development: Unity (C#), Godot (GDScript), or Pygame (Python)

4. Set Up Your Development Environment

Install the necessary software and tools:

Code editor (e.g., Visual Studio Code, Atom, or Sublime Text)

Version control (e.g., Git and GitHub for collaboration and backup)

Frameworks and libraries (install via package managers like npm, pip, or gems)

5. Break Down the Project into Tasks

Divide your project into smaller, manageable tasks. Create a to-do list or use project management tools like Trello or Asana to keep track of your progress.

6. Start Coding!

Begin with the core functionality of your project. Don’t worry about perfection at this stage. Focus on getting your code to work, and remember to:

Write clean, readable code

Test your code frequently

Commit your changes regularly using Git

7. Test and Debug

Once you have a working version, thoroughly test it. Look for bugs and fix any issues you encounter. Testing ensures your software functions correctly and provides a better user experience.

8. Seek Feedback

Share your project with friends, family, or online communities. Feedback can provide valuable insights and suggestions for improvement. Consider platforms like GitHub to showcase your work and get input from other developers.

9. Iterate and Improve

Based on feedback, make improvements and add new features. Software development is an iterative process, so don’t hesitate to refine your project continuously.

10. Document Your Work

Write documentation for your project. Include instructions on how to set it up, use it, and contribute. Good documentation helps others understand your project and can attract potential collaborators.

Conclusion

Building software projects is a fantastic way to learn and grow as a developer. Follow these steps, stay persistent, and enjoy the process. Remember, every project is a learning experience that will enhance your skills and confidence!

[izicodes]

Mini React.js Tips #2 | Resources ✨

Continuing the #mini react tips series, it's time to understand what is going on with the folders and files in the default React project - they can be a bit confusing as to what folder/file does what~!

What you'll need:

know how to create a React project >> click

already taken a look around the files and folders themselves

What does the file structure look like?

✤ node_modules folder: contains all the dependencies and packages (tools, resources, code, or software libraries created by others) needed for your project to run properly! These dependencies are usually managed by a package manager, such as npm (Node Package Manager)!

✤ public folder: Holds static assets (files that don't change dynamically and remain fixed) that don't require any special processing before using them! These assets are things like images, icons, or files that can be used directly without going through any additional steps.

✤ src folder: This is where your main source code resides. 'src' is short for source.

✤ assets folder: This folder stores static assets such as images, logos, and similar files. This folder is handy for organizing and accessing these non-changing elements in your project.

✤ App.css: This file contains styles specific to the App component (we will learn what 'components' are in React in the next tips post~!).

✤ App.jsx: This is the main component of your React application. It's where you define the structure and behavior of your app. The .jsx extension means the file uses a mixture of both HTML and JavaScript - open the file and see for yourself~!

✤ index.css: This file contains global styles that apply to the entire project. Any styles defined in this file will be applied universally across different parts of your project, providing a consistent look and feel.

✤ main.jsx: This is the entry point of your application! In this file, the React app is rendered, meaning it's the starting point where the React components are translated into the actual HTML elements displayed in the browser. Would recommend not to delete as a beginner!!

✤ .eslintrc.cjs: This file is the ESLint configuration. ESLint (one of the dependencies installed) is a tool that helps maintain coding standards and identifies common errors in your code. This configuration file contains rules and settings that define how ESLint should analyze and check your code.

✤ .gitignore: This file specifies which files and folders should be ignored by Git when version-controlling your project. It helps to avoid committing unnecessary files. The node_modules folder is typically ignored.

✤ index.html: This is the main HTML file that serves as the entry point for your React application. It includes the necessary scripts and links to load your app.

✤ package.json: A metadata file for your project. It includes essential information about the project, such as its name, version, description, and configuration details. Also, it holds a list of dependencies needed for the project to run - when someone else has the project on their local machine and wants to set it up, they can use the information in the file to install all the listed dependencies via npm install.

✤ package-lock.json: This file's purpose is to lock down and record the exact versions of each installed dependency/package in your project. This ensures consistency across different environments when other developers or systems install the dependencies.

✤ README.md: This file typically contains information about your project, including how to set it up, use it, and any other relevant details.

✤ vite.config.js: This file contains the configuration settings for Vite, the build tool used for this React project. It may include options for development and production builds, plugins, and other build-related configurations.

Congratulations! You know what the default folders and files do! Have a play around and familiarise yourself with them~!

BroCode’s 'React Full Course for Free’ 2024 >> click

React Official Website >> click

React's JSX >> click

The basics of Package.json >> click

Previous Tip: Tip #1 Creating The Default React Project >> click

Stay tuned for the other posts I will make on this series #mini react tips~!

[yasirinsights]

GitHub and Git Commands: From Beginner to Advanced Level

Git and GitHub are essential tools for every developer, whether you're just starting or deep into professional software development. In this blog, we'll break down what Git and GitHub are, why they matter, and walk you through the most essential commands, from beginner to advanced. This guide is tailored for learners who want to master version control and collaborate more effectively on projects.

GitHub and Git Commands

What Is Git?

Git is a distributed version control system created by Linus Torvalds. It allows you to track changes in your code, collaborate with others, and manage your project history.

What Is GitHub?

GitHub is a cloud-based platform built on Git. It allows developers to host repositories online, share code, contribute to open-source projects, and manage collaboration through pull requests, issues, and branches

Why Learn Git and GitHub?

Manage and track code changes efficiently

Collaborate with teams

Roll back to the previous versions of the code

Host and contribute to open-source projects

Improve workflow through automation and branching

Git Installation (Quick Start)

Before using Git commands, install Git from git-scm.com.

Check if Git is installed:

bash

git --version

Beginner-Level Git Commands

These commands are essential for every new user of Git:

1. git init

Initialises a new Git repository.

bash

git init

2. git clone

Clones an existing repository from GitHub.

bash

git clone https://github.com/user/repo.git

3. git status

Checks the current status of files (modified, staged, untracked).

bash

git status

4. git add

Stage changes for commit.

bash

git add filename # stage a specific file git add . # stage all changes

5. git commit

Records changes to the repository.

bash

git commit -m "Your commit message"

6. git push

Pushes changes to the remote repository.

bash

git push origin main # pushes to the main branch

7. git pull

Fetches and merges changes from the remote repository.

bash

git pull origin main

Intermediate Git Commands

Once you’re comfortable with the basics, start using these:

1. git branch

Lists, creates, or deletes branches.

bash

git branch # list branches git branch new-branch # create a new branch

2. git checkout

Switches branches or restores files.

bash

git checkout new-branch

3. git merge

Merges a branch into the current one.

bash

git merge feature-branch

4. git log

Shows the commit history.

bash

git log

5. .gitignore

Used to ignore specific files or folders in your project.

Example .gitignore file:

bash

node_modules/ .env *.log

Advanced Git Commands

Level up your Git skills with these powerful commands:

1. git stash

Temporarily shelves changes not ready for commit.

bash

git stash git stash apply

2. git rebase

Reapplies commits on top of another base tip.

bash

git checkout feature-branch git rebase main

3. git cherry-pick

Apply the changes introduced by an existing commit.

bash

git cherry-pick <commit-hash>

4. git revert

Reverts a commit by creating a new one.

bash

git revert <commit-hash>

5. git reset

Unstages or removes commits.

bash

git reset --soft HEAD~1 # keep changes git reset --hard HEAD~1 # remove changes

GitHub Tips for Projects

Use Readme.md to document your project

Leverage issues and pull requests for collaboration

Add contributors for team-based work

Use GitHub Actions to automate workflows

Final Thoughts

Mastering Git and GitHub is an investment in your future as a developer. Whether you're working on solo projects or collaborating in a team, these tools will save you time and help you maintain cleaner, safer code. Practice regularly and try contributing to open-source projects to strengthen your skills.

Read MORE: https://yasirinsights.com/github-and-git-commands/

[f1-disaster-bi]

A little something for my bestie. @princelancey I hope this makes you smile ❤️

".....do I have to wear this?"

Esteban pinches the bridge of his nose to stop himself from murdering the man behind him. He'd recently stopped hooking up with that lawyer who worked out of the diner so he really couldn't afford jail time right now.

He took a few deep breaths instead before he turned around to look at his newest co-worker and the man currently living on his couch; Lance Stroll.

Lance was holding the mustard yellow shirt with two red stripes as if the thing had bitten him as he looked at Eateban with the most offended look he could muster.

"Yes, it is the uniform", Esteban managed to get out as he crossed his arms over his own ugly mustard and red striped shirt, "Just be happy they let us wear our own pants now"

He swore Lance's face somehow git paler at those words. He might have even gagged a little as he tossed the shirt onto the couch and went to wash his hands as if he had caught something just by holding the material.

"Surely that shirt must be a health code violation. I mean, it has stains!", Lance rambled as he washed his hands quickly before starting to pave, "Are you sure I can't just wear my own clothes?"

Esteban had to shove down his laughter at the thought of Lance Stroll, only child of the now disgraced Lawrence Stroll, serving tables in their shitty little diner where dreams went to die while dressed in Gucci.

"You want to wait tables in those clothes? And mop floors?", Esteban replied with a shake of his head, "Listen, I know you're used to money but you are poor now. And us poor people? We wear shitty work uniforms and go to our soul sucking jobs because we need to pay rent"

Lance sighed and ran his fingers through his hair as he nodded, and Esteban felt a bit guilty for snapping at him, but he knew Lance needed to get a grip on his new reality because there was no where else for him to go.

Hell, before Esteban had offered him his couch, Lance had been near homeless and sleeping on the subway while carry everything he'd been allowed to take from his father's penthouse from job interview to job interview.

Lance was at rock bottom, and Esteban knew what that felt like because he'd been living at rock bottom since he was born.

"Look, the uniform is ugly, but it's better than ruining your clothes", Esteban offered after a few moments along with a hesitant smile, "I just know if you got a stain from the mystery stew on your expensive hoodie, we'd never get it out"

"I know", Lance groaned as he picked up the shirt again and began to walk to their shitty little bathroom, "Maybe I can convince the owner to invest in better quality?"

Esteban actually had to laugh at that comment.

"He can't even invest in meat that's actually what the menu says it is, so good luck with that"

[information-will-not-harm]

7 extensions of VS-Code to boost productivity.

Boosting your productivity as a beginner programmer is essential. Visual Studio Code (VS Code) offers many extensions to streamline your workflow. Here are some of the best VS Code extensions to help you write cleaner code, debug efficiently, and manage projects effectively.

1. Prettier - Code Formatter

Function: Automatically formats your code to make it clean and consistent.

Usage: Saves time on manual formatting and ensures your code adheres to style guides.

Install: Search for "Prettier - Code formatter" in the extensions marketplace and install it

2. ESLint

Function: Identifies and fixes linting errors in your JavaScript and TypeScript code.

Usage: Helps catch common errors and enforce coding standards.

Install: Search for "ESLint" in the extensions marketplace and install it.

3. GitLens — Git supercharged

Function: Enhances the Git capabilities in VS Code by providing insights into code authorship and history.

Usage: This makes it easier to understand the history and evolution of your codebase.

Install: Search for "GitLens" in the extensions marketplace and install it.

4. Code Spell Checker

Function: Checks your code for spelling errors.

Usage: Helps catch typos and improve code readability.

Install: Search for "Code Spell Checker" in the extensions marketplace and install it.

5. Path Intellisense

Function: Autocompletes file paths in your code.

Usage: Saves time and reduces errors when working with file paths.

Install: Search for "Path Intellisense" in the extensions marketplace and install it.

6. Bracket Pair Colorizer 2

Function: Colorizes matching brackets to make it easier to identify block structures.

Usage: Improves readability of your code, especially for nested blocks.

Install: Search for "Bracket Pair Colorizer 2" in the extensions marketplace and install it.

7. Pets

Function: Adds a fun, interactive pet to your VS Code workspace.

Usage: Provides a cute, engaging way to take short breaks and reduce stress.

Install: Search for "Pets" in the extensions marketplace and install it.

[kinghijinx22]

Top 10 Ghost in the Shell Stand Alone Complex episodes

Number 10- SA: Runaway Evidence – TESTATION

One of the most trans coded stories in a franchise with a lot of trans coded themes, I mean have you read the lyrics to the song from this episode Beauty is Within Us? It's just in the text at that point. Very emotional episode that made me cry a lot more on recent viewing.

Number 9- SA: Tachikoma Runs Away; The Movie Director's Dream – ESCAPE FROM

An episode split in 2 halves. The first being a Tachikoma development episode that gets surprisingly emotional. And the second being a subtle development episode for the Major with a very cyberpunk premise as we see just how mentally powerful she is.

Number 8- DU: Abandoned City – REVERSAL PROCESS

For a character that is so confident in herself and rock solid in her resolve, at least in Stand Alone Complex, this is one of the few times where we see the Major shook. Batou's reassurance is sweet though and also answers the question of why so many people follow Kuze as well, strengthening the parallels between them. Batou's philosophy talk with Gouda with the help of linking with Major's big brain is great. Boma does something.

Number 7- IN: The Day the Bridge Falls – MARTIAL LAW

The Major and rest of Section 9 deciding to break off from Government orders and go on their own mission to help save the refugees is really suspenseful. The highjacking of the chopper while Gouda makes his own moves and the Major warning Kuze just in time through brain connection while one of the best songs Torukia plays is super hype. I also like the conversation where Kuze literally talks to that old guy about Communism and also that old very much feeling like his version of Aramaki and I think even having the same VA? Again emphasizing the parallels between the Major and Kuze.

Number 6-C: The Copycat will Dance – MEME

*Monsoon has entered the chat*, seriously though this a great episode that explores the concept of memes, copy cats and how something becomes an icon as we really dig into the Laughing Man case. That final scene with the Major and Aramaki with that sunset lighting while Velveteen plays is real good.

Number 5- IN: Return to Patriotism – ENDLESS∞GIG

Beautiful but somber ending to an incredible show. The Major siding with Kuze and trying to save the refugees in her own way was awesome. The steaks have literally never been this high. I mentioned this in another post but I appreciate GITS not pulling any punches in it's accurate portrayal of the american government being as vile as they are, causing violence in other countries so they can call themselves heroes. The Tachikomas once again sacrificing themselves to save the day. Both Torukia AND I Do playing. The Major giving that genocidal right wing politician Gouda the most satisfying comeuppance that real life evil politicians should be getting. But then the Major not being able to save Kuze and the mellow ending of stopping the immediate conflict while certain issues still persist, and Christmas in the Silent Forest playing for the final credits. Beautiful but sadly realistic ending.

Number 4-DU: Natural Enemy – NATURAL ENEMY

Great episode to really kick off the main plot of 2nd Gig. It manages to introduce us to our main antagonist of the season, the vile but memorable master manipulator Gouda. The main conflict with the discrimination and poor treatment of refugees leading to heightened tensions. And the scene of Major leading her team in the Tachikomas to stop the rouge AI controlled choppers while one of the hypest but most beautiful songs Cyberbirds plays is one of the greatest action scenes in the entire show, especially the ending of Major getting out of the shot up Techikoma to hold down the chopper herself to give Saito a clear shot.

Number 3- DI: Beware the Left Eye – POKER FACE

The only time that we ever get to witness the Major and her team when they were in the military. Told through the framing device of Saito telling this story to his poker friends, we see how the Major and Saito first met on the battlefield in an intense sniper duel. It's one of best fight scenes in the entire show and what I love about it so much is that is manages to so much while not a lot is physically happening, it's all a super intense 4D chess mind game until the sudden ending where Major makes her move and we see how Saito lost his eye. Good backstory and cool fight scene that demonstrates just how scary facing down with the Major is, as well as making Saito a little more interesting.

Number 2- C: Left-Behind Trace – ERASER

The ramp up of the Laughing Man Case as we head into the endgame of 1st Gig. The Major showing concern for squshiest boy Togusa and being the protective parent of her team was very sweet. The final action scene where she takes on a big mech, all on her own in a fight that is very purposefully reminiscent of her fight against the Spider Tank in the original Oshii film is incredible. And the moment where she hulks the fuck out and demands Saito bring over the big ass anti armor rifle that she wields with one hand gives me chills every time. A nice detail I like is how it looks like her Ghost leaves her Shell for a moment when the mech almost crushes her head and the intense anger she feels afterwards probably being because she almost never feels that helpless and is ready to bring down the pain on anyone that makes her feel that.

Number 1- IN: Grass Labyrinth – AFFECTION

The most backstory the we ever get for the ever enigmatic but inspiring Major Motoko Kusanagi. I love the surreal vibes of the set up as she finds the antique store and what are original prosthetic bodies of herself of Kuze. The story that old lady tells, not knowing that one of those prosthetic bodies used to belong to the person she's talking to is beautiful. Where we learn more about just how young the Major was when she had get a full prosthetic body, why she had to get it, how she lost her parents and even how she knows Kuze. The Major being such an inspiration to someone even at such a young age is beautiful. And I love how this trip down memory road eases her up on the new recruits, because no body is perfect when they are new at something. Even Batou couldn't trail her. A beautiful episode and another one that always makes me cry.

[codemerything]

The Quiz App: Final.

Hello everyone, If you follow me or happen to have seen the post I made on the 21st of August (this post precisely) I casually made a request because I was tired of coding alone(still am 😆) and people showed interest starting with @xiacodes. Immediately- We talked about what we wanted to do causally and it ended up being "The Quiz App", We had a few calls on the Codeblr Discord to decide what we wanted to do and where we would stop, with @lazar-codes joining us later on to contribute. We digressed a bit and talked about other things lol but you get it.

Active Contributors

@xiacodes did 99% of the styling (she really loves styling) and it turned it great.

@lazar-codes suggested Trello(a task-management system) which we use to organize tasks and check progress.

I did the documentation, helped with the quiz-app logic, and theme mode and I was generally just all over the place offering help here and there, also being a sponge absorbing all the new pieces of information. 🤩🤩 Today, I merged the testing branch with the master branch, bringing an end to an experience that I want to cherish forever.

(I clearly suck at Geography lol) ⚠⚠⚠ I also want to take this opportunity to encourage Web Developers + programmers to contribute to open-source projects: It's one of the best ways to learn from other people, share ideas and put your Git knowledge into practice. Check out The Quiz App here The Quiz App (mmnldm.github.io) Special Shout-Out to @a-fox-studies Your presence is always appreciated!

[priya-joshi]

The Roadmap to Full Stack Developer Proficiency: A Comprehensive Guide

Embarking on the journey to becoming a full stack developer is an exhilarating endeavor filled with growth and challenges. Whether you're taking your first steps or seeking to elevate your skills, understanding the path ahead is crucial. In this detailed roadmap, we'll outline the stages of mastering full stack development, exploring essential milestones, competencies, and strategies to guide you through this enriching career journey.

Beginning the Journey: Novice Phase (0-6 Months)

As a novice, you're entering the realm of programming with a fresh perspective and eagerness to learn. This initial phase sets the groundwork for your progression as a full stack developer.

Grasping Programming Fundamentals:

Your journey commences with grasping the foundational elements of programming languages like HTML, CSS, and JavaScript. These are the cornerstone of web development and are essential for crafting dynamic and interactive web applications.

Familiarizing with Basic Data Structures and Algorithms:

To develop proficiency in programming, understanding fundamental data structures such as arrays, objects, and linked lists, along with algorithms like sorting and searching, is imperative. These concepts form the backbone of problem-solving in software development.

Exploring Essential Web Development Concepts:

During this phase, you'll delve into crucial web development concepts like client-server architecture, HTTP protocol, and the Document Object Model (DOM). Acquiring insights into the underlying mechanisms of web applications lays a strong foundation for tackling more intricate projects.

Advancing Forward: Intermediate Stage (6 Months - 2 Years)

As you progress beyond the basics, you'll transition into the intermediate stage, where you'll deepen your understanding and skills across various facets of full stack development.

Venturing into Backend Development:

In the intermediate stage, you'll venture into backend development, honing your proficiency in server-side languages like Node.js, Python, or Java. Here, you'll learn to construct robust server-side applications, manage data storage and retrieval, and implement authentication and authorization mechanisms.

Mastering Database Management:

A pivotal aspect of backend development is comprehending databases. You'll delve into relational databases like MySQL and PostgreSQL, as well as NoSQL databases like MongoDB. Proficiency in database management systems and design principles enables the creation of scalable and efficient applications.

Exploring Frontend Frameworks and Libraries:

In addition to backend development, you'll deepen your expertise in frontend technologies. You'll explore prominent frameworks and libraries such as React, Angular, or Vue.js, streamlining the creation of interactive and responsive user interfaces.

Learning Version Control with Git:

Version control is indispensable for collaborative software development. During this phase, you'll familiarize yourself with Git, a distributed version control system, to manage your codebase, track changes, and collaborate effectively with fellow developers.

Achieving Mastery: Advanced Phase (2+ Years)

As you ascend in your journey, you'll enter the advanced phase of full stack development, where you'll refine your skills, tackle intricate challenges, and delve into specialized domains of interest.

Designing Scalable Systems:

In the advanced stage, focus shifts to designing scalable systems capable of managing substantial volumes of traffic and data. You'll explore design patterns, scalability methodologies, and cloud computing platforms like AWS, Azure, or Google Cloud.

Embracing DevOps Practices:

DevOps practices play a pivotal role in contemporary software development. You'll delve into continuous integration and continuous deployment (CI/CD) pipelines, infrastructure as code (IaC), and containerization technologies such as Docker and Kubernetes.

Specializing in Niche Areas:

With experience, you may opt to specialize in specific domains of full stack development, whether it's frontend or backend development, mobile app development, or DevOps. Specialization enables you to deepen your expertise and pursue career avenues aligned with your passions and strengths.

Conclusion:

Becoming a proficient full stack developer is a transformative journey that demands dedication, resilience, and perpetual learning. By following the roadmap outlined in this guide and maintaining a curious and adaptable mindset, you'll navigate the complexities and opportunities inherent in the realm of full stack development. Remember, mastery isn't merely about acquiring technical skills but also about fostering collaboration, embracing innovation, and contributing meaningfully to the ever-evolving landscape of technology.

[dolconfessionsss]

Devil again! The Transphobic Mod (Ex-Mod) no longer is transphobic as far as I know and believe, and to not share too much of their personal life only what is public, have dated or are still dating a trans person somewhat recently. Can't talk about calling a head-canon cringe, I don't know what it actually was. The meme being spread was bad and that was stopped, it was a short-lasting joke (Blahaj and Skirt meme, transfem focused) that quickly became just toxic. Contribution Managers are hand-picked from trusted and veteran contributors to the game. Basically people that know a **LOT** about the game, lore, characters, that can communicate well with PurityGuy and Vrelnir, that have some writing skills and coding skills and such. VIPs are people that have for a very long time contributed important things to the game. Scythe and Cow Contributor Guy (Jimmy) have been around for YEARS at this point and while they might have some very bad takes they did help make DoL what it is (Jimmy being the entire reason DoLs images and such are now using a new renderer). They have been warned about their political takes and they have stopped talking about it. Being VIP doesn't make you immune to criticism or rules. The game is public via Git: https://gitgud.io/Vrelnir/degrees-of-lewdity If you know HTML, JS, SugarCube, etc, you can mod it, make your own versions, etc. Just be aware if you mod in stuff like Loli/Underage you won't be able to share it or talk about it in most places, and that your Git has to be public to be shared too due to DoLs license. No making private repos and then wanting them to be hosted in public. If y'all have any more questions I will stick around for a bit longer and lurk. Ps. I won't list names but a good chunk of the current staff team is queer or trans, so not like it's just some cis-boys club.

Ooh, thanks for the throughout answer, Devil! And the disclaimer as well :0c That's a heads up for all modders out there, so take notes (^-^)/

I'm blanking on more questions at the moment, so just gonna thank you again for taking the time to answer not just my questions, but also the other asks in this blog as well :]