Absolutely

play roblox

Look up thenewboston on youtube, he has a lot of good entry-level tutorials

Is your OS 32-bit?

Hi,

By 'applied' do you mean that you messaged me or posted a comment? I double checked my message history and the original post, and I couldn't find your name. It's possible it never made it through to the site.

I'd be more than happy to teach you whatever I can. I can message you and schedule some sessions if you'd like.

I can't tell you whether the drive is recoverable or not with no other information. It's possible it responds to SATA commands but cannot read from sectors. It's possible that it's mostly fine but there are some bad sectors that prevent the filesystem from being recognised. It's possible the platters are completely destroyed.

If there's data you care about, and if the drive is actually bad, I don't know of a better tool to recover drives than ddrescue, which works at a low level and will try its best to read every byte it can off a failing drive. It's also very slow, and you'll require a space big enough to put the data from the failing drive.

As for the software side, if you're using Windows, I can't really help you. I haven't used Windows in a decade and don't really know how it works.

In the start tray, search for "Disk Management" and you'll get to the partition controller. Here you can remove/uninstall the disc. You'll still wind up with broken shortcuts however.

Sorry if this is too technical.

lol this is my wheelhouse.

chmod, as well as a lot of other commands, support recursively operating on a path themselves; chmod -R.

More generally, I'd recommend using find -exec (man find), which you can pass flags to filter what you want (e.g. -type f for only files).

While most commands expect a list of files to operate on as their arguments and not in stdin, xargs transforms lines from stdin to command line arguments.

In simple cases, you can use a shell for loop as follows:

for file in directory/* ; do
  echo "$file"
  do_something "$file"
done

I wouldn't recommend ever using ls in scripts; it's made to output human-readable text and not something that a script can reliably parse (think of edge cases like a filename with embedded newlines).

smile and nod, laugh at dumb jokes

being an easy person to be around is way more valuable than 5 years of experience with "backend technologies"

deleted by creator

lmao not really. "Good" jobs won't give a shit if you give a shit, it'll be a professional arrangement. But it's a crapshoot as to whether you're going to get one of those, or even get to the interview stage.

I've noped out early in the application process because I decided I'd have to be mostly brainworm in order to work there.

Depending on the place, a completely different person will be deciding whether to pass you on to the interview process than the people actually interviewing you. I.e. screened by HR/recruitment, and interviewed by potential coworkers. Focus on keywords with HR, in your cover letter, resume, and then with fellow engineers you can mostly be chill and actually talk about technology. HR/recruitment will be looking to check off all the boxes for knowing each and every little technology they use, so try and tune that stuff to the listing, but be honest when talking to fellow engineers, as they can draw a distinction between "knowing Javascript" (made a webpage in college) and knowing Javascript.

You probably know all that though, and I can't really offer too much to help. It just sucks.

ext4 and other Linux-native filesystems support extended file metadata, where you can put that information right in the file. I think KDE's Dolphin file browser has support for tags using these.

What you're essentially asking for, though, is how to make a database that correlates those assets with some metadata.

One solution is to use the filesystem as a "poor man's" database, like you suggest. I would recommend using symlinks for this: instead of copying the files, you just reference them in multiple locations. This has the advantage of all your tools supporting it out of the box, since they're just regular files on the filesystem

Another is to use a text document of some format, essentially a spreadsheet, that matches metadata with file path.

You could use SQL with a real database. This is a heavyweight and very powerful tool, might be overkill.

Finally, there are probably third party tools geared towards this already. Think of something like itunes but more general. You'd probably be able to find them by searching for "Music tagger" or "photograph tagger".

Never used sheets before, can try to help if you're having a specific problem

deleted by creator

Sure, lots of libraries for sensors, controllers, etc. are available in Python. I'd say it's a great first pick.

I've worked with Linux professionally for years, and here's a secret: distro doesn't matter all that much, especially if you're just a desktop user. Since they're packaging mostly the same software differently, you can just pick which one you'd like.

• Debian is a community distribution with actual democracy behind it
• Red Hat distros have corporate support
• Arch Linux is very rolling release
• Ubuntu is Ubuntu
• Gentoo compiles stuff from source, which appeals to some people

etc.

As for dual booting, if you want to keep using Windows or whatever for anything, there's no real reason you ever have to stop dual booting. You can keep it there if you need it. Some people remove it because they truly don't need it, some people remove it because they like to commit and if they don't they'll never learn Linux, and a lot of people just have Windows there indefinitely.

A note on Debian since that's what I use: Debian, when you install it, is entirely free software. If you want to download non-free things (like NVIDIA drivers, wifi drivers) you have to enable that and then install them. If Debian runs slow but Ubuntu is fast, it's probably the graphics drivers, as Ubuntu gets most of its packages from Debian.

deleted by creator

Not really much experience with electronics/soldering, aside from like watching Ben Eater, sorry. Have a friend I could bug, but that's all.

Someone else DM'd me for tips on PC building, and I could paste my response here if that'd be useful.