There is a dark art to growing in small spaces and it’s super fun! Run 12-12 lighting from seedling and you can get a single mega bud, with proper care. The plants will only develop its main cola, basically. Unfortunately, small grows and screwing with their growth cycle causes stress and too much stress causes herms. Small price to pay, I suppose.

Oh, fuck off.

No, that is not what he said at all.

Another common example would be graphite as it is just small “sheets” of carbon. It what makes graphite perfect for pencils and also as a lubricant.

“real” is subjective.

I taught myself QuickBasic as it was the only thing I knew that was related to copying C64 BASIC out of magazines. (QBasic was packaged with DOS 3.11 I think and I was able to get a full copy of QuickBasic somehow. That was about +30 years ago? Dunno. I was about 12 at the time.) I didn’t know what other languages were out there besides TurboPascal. I did learn simple Pascal, but that was a short chapter.

I actually met someone else in the area that was learning to code, and of course, we wanted to write a game. The only way to code for a mouse at the time was to write an INT33 handler, so it kicked off our interest in asm. (I still use asm for MCU stuff on occasion, but it’s limited.) I quickly diverged into writing some really nifty… eh… “boot sector code” so that kicked off my career in security.

And yeah, it’s the same phenomenon for me: I just think in terms of bits and bytes getting shifted around and I still refuse to believe in “magic”. (Slight jab at Rust coders there, but in good fun.)

Fast forward to today, I train “kids” fresh out of college as part of my job now. The first thing I do is start giving them weird tasks that require they actually understand how something like an fopen() actually works.

(Funny story. I refused to “show my work” in math class for simple f(x) problems as I viewed it as unoptimized code. Lulz. I was such an autistic dork.)

That, 200%!

When I started in computers, years ago, I transitioned from QuickBasic directly into assembly. Ever since then, I can kinda “read the Matrix” (Blond, Brunette, Redhead…) and forget about how confusing a raw binary or how a mess of a dmp looks to someone else. (To me, I really just see patterns and nothing massively complicated.)

“It’s just data.” - You would be surprised how fuzzy that statement is for some people. It’s almost exactly like telling someone who doesn’t speak any English that “the sky is blue”. It’s totally cool though! Learning about the internals of any computer is really just a very long chain of “aha moments” as many concepts aren’t intuitive.

I would look into something like Doppler instead of Vault. (I don’t trust any company acquired by IBM. They have been aquiring and enshittifying companies before there was even a name for it.)

Look into how any different solutions need their keys presented. Dumping the creds in ENV is generally fine since the keys will need to be stored and used somehow. You might need a dedicated user account to manage keys in its home folder.

This is actually a host security problem, not generally a key storage problem per se. Regardless of how you have a vault setup, my approach here is to create a single host that acts as a gateway for the rest of the credentials. (This applies to if keys are stored in “the cloud” or in a local database somewhere.)

Since you are going to using a Pi, you should focus on that being a restricted host: Only run your chosen vault solution on it. Period. Secure and patch it to the best of your ability and use very specific host firewall rules for minimum connectivity. Ie: Have one user for ssh in and limit another user account to managing vault, preferably without needing any kind of elevated access. This is actually a perfect use case for SELinux since you can put in some decent restrictions on the host for a single app (and it’s supporting apps…)

If you are paranoid enough to run a HIDS, you can turn on all the events for any type of root account actions. In theory once the host is configured, you shouldn’t need root again until you start performing patches.

I dump memory more often than you would think. It’s usually not obfuscated or encrypted in any meaningful way even though it is fairly trivial to do so.

It’s good practice to scour through any bloatware installed on windows laptops. Since bloatware is generally written by the lowest bidder, you can find all kinds of keys and phone-home urls (sometimes with all the parameters) and other weird things. Just fire up a decent hex editor and search for strings in the dump file. You don’t need to know jack about reverse engineering either.

Second this.

Resins have a typical use-time for within a year. Some may last longer, some may not. Some may start to show exposure issues. Some just start to separate or solidify partially. Some resins don’t care at all. (It should be written somewhere on the bottle when the resin was made and when it should be used by.)

This is a helluva “unknown variable” you are working with, is my point. Resin is the absolute core of any printing functionality (obviously) and print settings are highly dependant on the resins qualities.

Just because I am so damn picky during my testing and learning process, I would abandon testing with that resin completely and be thankful it even printed a calibration test at all. (I would get a fresh bottle, is what I am saying.)

However, in the interest of using the resin, I would YOLO the exposure time (increase it) and start printing prototypes or other strange experiments. There is a bunch of things I could test even if using a sub-optimal resin.

You could spend time with the rest of that bottle and tweak the settings into partial-perfection. How reusable are those settings for future bottles though?

I see a lot of inconsistent exposure, which is super weird.

How old is the resin? New? Was it purchased at the time you got the printer? Was it well shaken? One particular resin I have will separate hard and basically needs a blender to get broken up again to be capable of printing.

The biggest issue I see is the gap in the outline at the very top of the print. That shouldn’t happen that late in the print at all. It’s iffy resin or there are small solid chunks floating around in your tank.

My first week with my resin printer was spent testing exposure and probably did about a hundred or so “cones of calibration” ( https://www.tableflipfoundry.com/3d-printing/the-cones-of-calibration-v3/ ) with a few different resins.

While a person generally needs to be a little on the crazy side to do that much testing, it was effective. After all of the that testing, what I found out is that comparing two prints with different settings is more valuable than just printing one single calibration test.

See if you can manage to print at least 8 tests at 8 different exposure levels. (I prefer 16, but you do you.) You will quickly learn how to interpret calibration tests and how exposure works.

But, back to your question and my official interpretation: You have a printer that is capable of printing! Yay! I ain’t being sarcastic and this is good. You do need some comparison prints though…

connecting it to the internet is a no-go with an orphaned kernel.

Hold my beer.

There was a precursor to butyl tape that I am thinking of specifically. It was more clay-like and just as nasty. (It would have been easier (subjective) to pinch off balls of the stuff and cram it in those screw holes.)

No mind. You had the correct solution, me thinks.

I absolutely agree and the goal is to extend that time for as long as possible. (But yeah, anti seize is actually a really good idea.)

Sounds like you have never had the “pleasure” of working with coax junction sealants before. It’s not too bad, but it’s also not fun either. It is very effective though.

I would personally cram in something related to COAX-SEAL into the screw holes. Having setup a few cables outside for antennas (ham radio) I have learned to never trust metal to metal connections when exposed to weather.

Coax-seal might be a bit hard to work with, so maybe some silicone caulk would work?

Remote probes are getting super cheap now, so shop around for those if you can. They are awesome for the days you want to grill a steak traditionally but most of all, it’s awesome for bone-in chicken cuts. (I prefer consistent heat on my chicken the whole time and don’t want to keep jabbing at it. Cooking with ADHD can be pure hell at first and a steady stream of data helps with that.)

I’ll use snake_case and camelCase in the same project. Fuck the system and stick it to the man. You don’t need AI for shitty code structure!

(Don’t worry. I am not a professional dev, but I know how to piss them off really quick…)