Home Upgrade Search Memberlist Extras Hacker Tools Award Goals Help Wiki Contact

AI coders dont know about git

(Mar 31, 2025 04:31 AM)Chornaya Magiya Wrote:  Everyone talks about Git, but the thing is, Git projects, data, and API keys get hijacked daily. Personally, I wouldn't put any files on Git or allow employees to do so, unless they are experienced IT professionals who won’t fall for phishing links.

The point is, you always need to do backups.
Personally for my opinion best is to do local backups.

If u want work with team, np create local network folder and go ahead :) works for all languages haha

... Git is a Version Control System for tracking file modifications. Its history allows reverting files to previous states, addressing the need for reversibility. The context you replied to was someone using the 'Cursor' AI tool who lost months of work and specifically asked how to make actions reversible. Given that Git's core function directly solves that user's problem, what do your concerns about project hijacking or your suggestion of local network folders mean in that specific scenario? How would those points better address the need for version history and easy reversion compared to Git?
looking for work
I can say i have forgotten to make backups when trying out ideas then breaking everything. This happens a lot less now days but its just human error though nothing is an excuse for a lack of skill.

I had multiple junior developers at my work that where able do anything without some sort of helper yet we still hired them.

It's very sad that is has become a practice that a company will still pay people for and i can say i am far from the best programmer. I can at least write decent code while people still gripe about wanting more pay while knowing nothing just because they graduated with a fancy degree.

i have no idea how people can even go through college and learn nothing its very sad i was lucky enough to have great professors that cared enough to teach. I guess this is not common anymore.

I graduated in 2012 so in around a decade it changed this much its pretty crazy.
(Mar 16, 2025 01:31 PM)Phantom_NiNja Wrote:  Everyone is cheating using AI in today's time. I heard that 60% of kids in school from elementary to highschool cannot read or count money.

We got a new hire that just got out of highschool and his job was to process payments. He demanded the customer use paypal, vemo, or apple pay or google pay. He said they have to convert their money into digits. Our boss got pissed off because too many customers complained that we refused to accept cash payments.

That kid ended up getting fired. The reason he didn't know how to count money and his defense is that it's an old outdated system. He told our boss that people need to get with the times and start using digital wallets like crypto and debit cards or credit cards. He said no one pays in ash anymore.

He said he doesn't know how to count money because he never had to count money in his life and he himself uses crypto and a debit card to pay for things.

I am dumb founded.

that's terrifying

i'm hearing that kids aren't being taught to read analog clocks either- not sure how true that statement is but i honestly wouldn't doubt it
I think the issue isn't the accessibility of AI or even its quality or rather the lack of such ruined people. If they had a normal education without smartphones or at least without them til hs this wouldn't be nearly as bad as it is, literally has turned smart people dumb, and its truly only going to be used to its full power by a very small % of people. I'm just stuck in my manual ways of copying every folder and renaming everything with a script rather than pushing a single command to do it all for me.
(Apr 20, 2025 04:20 AM)ZeLizzard Wrote:  I think the issue isn't the accessibility of AI or even its quality or rather the lack of such ruined people. If they had a normal education without smartphones or at least without them til hs this wouldn't be nearly as bad as it is, literally has turned smart people dumb, and its truly only going to be used to its full power by a very small % of people. I'm just stuck in my manual ways of copying every folder and renaming everything with a script rather than pushing a single command to do it all for me.

What.

People are just lazy.
looking for work
(Mar 31, 2025 04:31 AM)Chornaya Magiya Wrote:  Everyone talks about Git, but the thing is, Git projects, data, and API keys get hijacked daily. Personally, I wouldn't put any files on Git or allow employees to do so, unless they are experienced IT professionals who won’t fall for phishing links.

The point is, you always need to do backups.
Personally for my opinion best is to do local backups.

If u want work with team, np create local network folder and go ahead :) works for all languages haha

You can always host your instance of gitea. https://about.gitea.com/ and not worry about leaking stuff.
(Mar 31, 2025 04:31 AM)Chornaya Magiya Wrote:  Everyone talks about Git, but the thing is, Git projects, data, and API keys get hijacked daily. Personally, I wouldn't put any files on Git or allow employees to do so, unless they are experienced IT professionals who won’t fall for phishing links.

The point is, you always need to do backups.
Personally for my opinion best is to do local backups.

If u want work with team, np create local network folder and go ahead :) works for all languages haha


(Apr 5, 2025 11:44 AM)Klonopin Wrote:  ... Git is a Version Control System for tracking file modifications. Its history allows reverting files to previous states, addressing the need for reversibility. The context you replied to was someone using the 'Cursor' AI tool who lost months of work and specifically asked how to make actions reversible. Given that Git's core function directly solves that user's problem, what do your concerns about project hijacking or your suggestion of local network folders mean in that specific scenario? How would those points better address the need for version history and easy reversion compared to Git?

(Apr 20, 2025 07:44 AM)Tor Wrote:  You can always host your instance of gitea. https://about.gitea.com/ and not worry about leaking stuff.

Or you could just use Git and have it locally. No need to host it on a repository. Gitea would be no different than using a private repository on github for example; both ways, you avoid leaking.


errm let me just have a public repo and lets push all my .env variables there!!1
looking for work
(Apr 20, 2025 04:43 AM)Klonopin Wrote:  What.

People are just lazy.

I agree with this and will add to the previous comment because i have experienced this with junior developers mainly.

Almost all of them rely on training wheels without understanding what the language in question should do let alone use programming conventions and follow standards without crying about every little thing. This is personal experience so it may differ but this seems to be the case no matter the skill level the junior developers i have worked with over the last 10 years.

The company i work for is a mid size company meaning around 250 or so people at any given time not counting interns because they normally are just here for school and normally leave its not just a skill issue. I fail to see how people can go to college and lack a basic understanding of programming some of the senior developers myself included are self taught so i believe its a much deeper issue of training more than just AI .

We use AI for many things but if you do understand what the source code in question is meant to do and how it works well then you shouldn't be using AI outside of simple tasks to begin with and git i use github mainly for myself and my company.

The one i work for uses an ultimate gitlab license for government as its a contracting company with minimal issues though i could not tell you if its fully secure or not but i would hope so but hey its goverment projects so who the heck knows. :p
(Apr 20, 2025 10:22 AM)Klonopin Wrote:  Or you could just use Git and have it locally. No need to host it on a repository. Gitea would be no different than using a private repository on github for example; both ways, you avoid leaking.


errm let me just have a public repo and lets push all my .env variables there!!1

You can host gitea on your LAN on a private machine with no outside access. Thankfully things like VLAN's, firewalls and secure tunnels exist. Anyway, gitea is for people who're afraid of the commandline or need some additional web / ui features. It's not needed, you can just git push code directly to a backup machine running somewhere in your local area network for example.

Also: Only using Git locally is just BEGGING for problems. You can self-host your own git repo's, sure, and store them locally but what you really need if you're doing that, in addition to version control, is a solid backup procedure. Preferably, you store your backups somewhere outside of your home (you know, in case of house fires or the likes) and not in some kind of cloud providers' watchful eye if you care about your privacy and code.

After all, storing any kind of sensitive data locally (including git repositories) without backups is completely pointless if (actually, I should say WHEN) you lose all your data due to SSD / HDD failure. These things happen. Especially if you read/write a lot of data which is usually the case if you're working on large projects or just projects with a lot of dependencies in general and add a dash of docker / OCI on top.

Using git or other version control tools in combination with a solid backup procedure is the key to success and just common sense. Most people today just use github and gitlab as their cloud 'backup' for code in addition to version control, which is understandable because it's free and simple, but if something is free, you're usually the product. Which results in things like GitHub Copilot being trained on your code and Microsoft having access to your code. But a cloud provider is not a foolproof backup mechanism. GCloud has proven this, by accidentally removing the data of a big customer very recently, OVH has proven this by burning down an entire cloud server park (by accident), etc. etc. That's why I always recommend taking backups of your devices and repositories on a weekly basis or even on a daily basis (depending on your needs) and storing backups outside of your own residence.
[Image: vp6iypF.gif]


Possibly Related Threads...
Thread / Author Replies Views Last Post
by HackersJun 4, 2024 11:18 AM 12 316 Jun 4, 2024 11:18 AM
Last Post: Hackers
by HackersMay 29, 2024 08:26 AM 2 300 May 29, 2024 08:26 AM
Last Post: Hackers
by HackersMar 22, 2024 06:01 AM 6 262 Mar 22, 2024 06:01 AM
Last Post: Hackers