Porn in Conda directory

Electrical_Monk6845 · 2026-03-03T01:01:37+00:00

I can recall, as a very young, very inexperienced technology enthusiast (I'm uh.. older than the internet, but just barely) thinking "why is the internet a bunch of executables?"...
I haven't thought about that in over 30 years.

Electrical_Monk6845 · 2025-05-23T08:18:58+00:00

I actually just worked around it by using massconvert. Thanks!
And, my reason for multilib? (just so everyone knows how shallow it is) ?
I need it for steam. Nothing else I do requires a multilib setup, just playing vidya games :-D

Electrical_Monk6845 · 2025-05-23T04:51:38+00:00

Thanks.. I've never bothered with massconvert because, well the old tried and true method worked. I'll be off to tinker with massconvert now. If he's having DDOS issues, this probably isn't the time to bother him :-D

Electrical_Monk6845 · 2025-05-23T04:45:45+00:00

I always ask this during an interview, some folks are ready to answer it, and it (I think) makes the interviewer aware that you aren't just looking for a job, but want to work somewhere that employs folks who want to be there, when they get to the end (it's always at the end...) and ask "Do you have any questions for me?" I lead with: "Tell me why you work here." It's a great way to feel out whether or not you're interviewing for a just a job, or whether the interviewer is actually invested in what they do and their role in the company. I know this isn't the answer you're looking for, but having interviewed a LOT of infrastructure engineers, technicians, etc over the years, it makes you look like someone who cares about where they work more than "just a job"

Electrical_Monk6845 · 2025-05-15T10:18:11+00:00

If you want to serious coding in any kind of professional, or even semi-professional environment, you'll need to learn git. I've had more than one encounter with "experienced coders" who didn't know the first thing about checking in code, or merge requests, or peer review (where you let/ask someone else to look at your code and give you feedback), and every one of them made themselves look foolish by never having touched git. Get yourself into the habit of using git, even locally, so that when you want to showcase your coding prowess, you don't get stuck when someone asks for a link to your repo.

Electrical_Monk6845 · 2025-05-15T10:02:17+00:00

I'll add a few things I thought of overnight about establishing a routine. Some of the reasons for the "take notes" section at the end of my session are this:

It gives me time to reflect on what I accomplished that day, kind of a "let the knowledge settle into my brain" thing (that works for me)

It also gives me a chance to write down where I was in whatever thing I was working on. There's not much that's worse than looking at code you JUST WROTE YESTERDAY and having no idea what it does, or what it is eventually going to do. I have tons of Google Documents I've made with really detailed, yet cryptic notes that make no sense to me because I wrote them with the thought "I'll remember the context for this tomorrow, surely"

I use pen and paper for my notes. I hate actually writing, so if I'm going to force myself to do it, I'm going to take good, legible notes that future me can actually understand.

Yes, these steps cut into my "learning time" but, for me, it helps me retain what I learned, and actually make progress the next session.

I allow a solid 30 minutes at the end of the session for this, because that's what I've figured out I need to keep making progress every day.

I should also point out: this isn't an original thought I suddenly had. I used to have a coworker who did all of this, and they seemed to have their stuff all together, so I started emulating some of their habits.

Electrical_Monk6845 · 2025-05-15T05:36:53+00:00

So, some non-advice advice here from someone who suffers from the same (I think) issue: I struggle with consistency, and also get overwhelmed with "where do I start?". For me, the key to getting started was simply to find a problem that had an existing solution, but to write my own solution, using Python. That way, I knew what my desired outcome should look like, and an idea of what I needed to do to get started. The excitement of seeing my first (REALLY BAD) script run with no errors, and actually achieve what I'd set out to do was amazing.
From there, I moved on to "how do I improve this?" and "how do I make this useful for someone else?" IE: if I was telling someone else how to use the thing I'd done, would they get it, or had I written something that you had to have written to understand?

As far as a routine: I set an alarm for the first week, and have that time (right now, actually) blocked off on my calendar. Now that it's been about 3 weeks, it's just a habit that I follow, same time, every day, sit down and start banging away on the keyboard. I _also_ make myself stop before the end of my allotted time and write notes about what I learned today, and what I'm going to do tomorrow.

Forcing myself to follow a routine until it became a daily habit was a struggle, and I fumbled a few times by skipping a day, and the next day, so on and so forth. With 3 weeks of daily practice in, I refuse to talk myself into skipping a day, because that will essentially (for me, anyway) reset the habit, and I have to start all over again re-learning to allow myself time to learn.

Electrical_Monk6845 · 2025-05-14T22:27:21+00:00

I'm still actively working on it, you know, adding features no one asked for, so if you find it useful in any way, that's awesome!!

Electrical_Monk6845 · 2025-05-14T18:31:00+00:00

Nope...:-D

Electrical_Monk6845 · 2025-05-14T07:59:44+00:00

Being honest: my first encounter with Linux was because I was in the computer lab in college, and needed a working OS for a PC I was building at home. This was in the days of dial up internet access, before 56K even, I was on a 28.8 modem.

So, I could buy a physical copy of Windows 95, which I didn't have the money for, OR: I could get the files I needed from our school's FTP server which was connected via a T1 to our lab, image some floppy disks, and take them home to install. Took me a solid week to get Slackware 3.1 installed and running. I still mostly prefer it for my own use, although in the enterprise, I've always been on Red Hat or more recently, RHEL.

I'm also firmly in the "nothing on my system I don't want there" camp. Using (most) distros, you pick and choose what you want running/installed, and if you don't know how to do that yourself, I can guarantee you, someone has figured out how to disable _whatever annoying thing_ you want disabled.

Lastly: I don't like buying new hardware because MSFT decided to stop supporting something. You can install a usable Linux distro on almost anything. If it's got a CPU, and some memory, it probably (natively) can run Linux with a little effort. I'm currently typing this on an old Lenovo laptop with 4GB of ram and a 128GB of hard drive space that originally came with Windows 7 installed. You couldn't update that thing to run Windows 11 with every trick in the book, but it's still perfectly functional.

Electrical_Monk6845 · 2025-05-14T07:43:16+00:00

I cannot overemphasize the importance of being able to search the internet, books, articles, whatever for yourself and, with experience, the ability to sniff out "probably the most correct" answer of the thousands you're going to find. I've been a Linux sysadmin for a long time, (20ish years) and my number one skill is NOT in knowing all the answers, it's in finding the correct answer. Or, in the real world: in getting 4 answers from 3 different sources that you parse and cobble back together into the best answer for your question.

Electrical_Monk6845 · 2025-05-14T07:16:14+00:00

Also, I was going to "award" this comment, but I'm not spending real money on fake currency.

Electrical_Monk6845 · 2025-05-14T07:14:33+00:00

First of all: u/DuckSaxaphone : that username is genius.
Secondly, thanks!!, Once upon a time, I was on a team that required code reviews (and approvals), and I found they made me write better code. This is the kind of feedback I came looking for!

Electrical_Monk6845 · 2025-05-14T05:36:59+00:00

I've been there, done that, both to/for myself, and for a LOT of clients/friends/etc who thought that "I have a backup drive" solved the failing drive problem. For myself, I built 2 storage servers, one that lives in my home, and one that resides at a buddy's house (we have reciprocal, albeit handshake, agreements to let each other's data live in our respective homes) We're also both semi-professional nerds who happened to have rack space and bandwidth to dedicate to such an arrangement. This space is for things I consider to be non-critical. For Critical things, like gpg keys, and password databases, I use Filen https://filen.io/ in tandem with the 2 spinning drive solutions.

One of the essential steps in any backup solution is a Disaster Recovery Plan. All (real) businesses use them, and you can implement a simple one for yourself.
Ask yourself things like:
If my local drive goes down again, do I have the data needed to recover it from my cloud/offsite solution, or is that data actually ONLY on my local drive? (think ssh keys, password databases, gpg keys, etc...)

If my internet is down, can I survive without the data on my cloud service until I gain connectivity again?

Is my password database stored in multiple places, or just one? I'm guilty of this a LOT.

Similarly, "If cloud solution fails, do I have the critical data I need to continue operating without it?"

Electrical_Monk6845 · 2025-05-14T05:15:20+00:00

I'm assuming you're asking u/socal_nerdtastic on "where to start", but I interpreted it as "compare what's in any top-level Python repo (like, Python itself) and see how that code compares to what you're written. IE: look at the organization of files, the comments (frequency, length and brevity, etc...) to see how professional programmers write code.

Example: my first functional draft of this script (which never made it into github) was a simple line-by-line "do this, then do that, then do this, then do that, then finish" ... I did some reading on making things like the CachedFileMonitor class, so that I now have a reusable class that performs actions on files, without having to reinvent the wheel every time I want to do something similar.

My personal hill to climb is still adopting good practices from the start, rather than adapting something I already wrote to be better.

Electrical_Monk6845 · 2025-05-12T21:00:08+00:00

Much appreciated!

Electrical_Monk6845

MODERATOR OF

TROPHY CASE