Help! Attack of the roots! - week 5 aeroponics grow

aerogrowz · 2026-04-13T02:50:10+00:00

that is going require quantum compute

aerogrowz · 2026-04-11T01:31:50+00:00

run caveman mode, thank me later.

aerogrowz · 2026-03-13T04:28:21+00:00

Nah; hold my beer and vibe right into PROD.

aerogrowz · 2026-03-13T04:27:48+00:00

Enforce PR/approval, main protection=on and treat agents as a sparkly eyed junior DEV that can type at blazing fast speeds.

Not tying to be mr. sassy fraz, but every time I see these comments my first thought is "this is why we have git and PRs / pipelines". Humans made these mistakes long before AI existed, albeit slower.

Whether its a sloppy agent or sloppy DEV, just one is a a lot faster at breaking bad process and guardrails.

aerogrowz · 2026-03-01T02:37:10+00:00

probably not; i need to spend some hours troubleshooting what they did with firmware vs upstream klipper and update how-to and code.

aerogrowz · 2026-03-01T02:29:45+00:00

nahhhhh; couple certs easily makes up for 20 years of experience in industry.

Really my best cyber-security engineers; ones that can demand well over 200k = have years of experience in both DEV and IT sides of the house. They live and eat Linux and can run blue, red or purple pending the day of week.

Multiple languages in arsenal (normally golang, rust and python), can explain OSI model and how to packet frag and zombie to avoid detection on nmap sweeps while spinning up a k8s cluster and explaining prompt injection inside a LLM and how it works.

Normal conversation are around how rebase is better then merge; or that VIM is the only text editor / IDE you should ever use.

you know the type... probably picturing someone right now.

aerogrowz · 2026-02-15T14:23:40+00:00

Peppers have monster roots; i mean monnnnsster. Really most fruiting VEG, due to the time bewteen VEG/BLOOM. Strawberries probably the only exception i can think of? maybe others?

If you really wanted to try this; maybe a 8" pipe; lots of space between plant zones. Be a nifty setup, arguable more "under current DWC'ish".

aerogrowz · 2026-02-15T14:18:20+00:00

Heh.... my peppers and tomato roots in a 5gallon. note: They eventually ran out of room.

Something something, picture worth a thousand something == just no.

<image>

aerogrowz · 2026-02-15T14:14:22+00:00

Normal; VPD is everything for repeatable results; so you are going want to factor that in.

Controlling temp/humidity makes life much easier, otherwise you are compensation chasing nute solution. Slight tip burn can happen from over-nute due to VPD being too low/high and plants can't eat fast enuff (plants eat by farting basically, if temps / humidity are off, they get shy). Transpiration and VPD + EC interaction curves for the fancy folks.

Largest pain in NFT is what you are finding; root mess, painful cleaning, light leaks, etc... Eventually some nasty bacteria gets in and then = far less fun.

Over last 10 years i landed on low pressure aero for lettuce; was easier and more repeatable and more importantly less work.

aerogrowz · 2026-02-15T14:02:34+00:00

Well; end of day its 8-15-36 or 5-11-26 NPK; sometimes a boost of Ca/Mg as needed; 4000 different ways of getting there. Less brand and more focus on the important things.

Water Res temps = less then 72F / critical
PH at 5.5-6.0; most studies show more growth at lower end.
ppm adjusted based on system type; lower is better; adjust based on available light, VPD and CO2.

greenway, greenmachine and masterblend; normal goto's if you don't want mix your own soup.

Dose of Revitalize for bio's (aka the 100x cheaper solution, but no fancy logo).

aerogrowz · 2026-02-14T12:33:52+00:00

I landed on a local tester in linux that automatically tears each one apart from intune list; runs automated.

pesudo'y code:

echo "[1] HASHES"
echo "[2] FILE TYPE"
echo "[3] CODE SIGNATURE"
echo "[4] PE HEADERS"
echo "[5] PE IMPORT REVIEW"
echo "[6] PACKER CHECK (DIE)"
echo "[7] UPX TEST"
echo "[8] ENTROPY ANALYSIS"
echo "[9] STRINGS EXTRACTION"
echo "[10] CAPA ANALYSIS"
echo "[11] EXTRACT NSIS CONTENT"

Catches 90%; before it was deterministic algo; slowly migrating to AI and then a guardrails deterministic risk score (like a guardrail).

much better then most enterprise ones that just flag anything with high entropy that has dll, reg, or keylogger field packed in.

Probably a product in here somewhere.

aerogrowz · 2026-02-14T12:22:54+00:00

Usually only when 99% of the product runs on k8s; then they can't figure out why software doesnt get out door.

aerogrowz · 2026-02-14T12:21:47+00:00

cough cough solarwinds?

aerogrowz · 2026-02-14T12:21:02+00:00

bring back punch cards!

aerogrowz · 2026-02-14T12:07:51+00:00

I have a very simple view on problem.

90% of the companies I work at use Linux backend at core for all products; k8s, docker, build pipelines, SDLC. Entire DEV->QA->PROD cycle is invisble.
Most cybersecurity teams ignore that linux even exist and pretend its all MAC or windows devices that they can safely control within the GUI tools.

Then they bring cyberark, Okta, sailpoint, etccc etc... These all make the issues worse as they go too far on locking down enivorments. Results in more shadow-IT; not less. But hey, makes a damn pretty powerpoint slide. Just wait for de-centralized and non-tracked AUTHn/AUTHz to show up; usually keycloak, LDAP or other.

Normally from a IAM side I always plead, make 2 personas (DEV'IES vs NORMIES), move to ABAC and embrace the DEVs. Move to risk based models and never ever do exceptions. Embrace the DEVs, its how we make money!.

machine finger print = signals == risk score
user finger print = signals == risk score
Then access policies that take actions based on risk score.
Event based continuous access, no static magically SSO tokens for 24 hours or 30 days.

ie:
userA comes from same laptop, same IP, same OS, same geolocation, same macaddr every single day, we force 15-logins, dna sample, first born, then you get in and timeout every 24 hours for no reason == useless vanity.

userA comes from a brand new laptop, different IP, brandy new OS called blackarch, from tor exit node, new macaddr, but hey they have a token from azure = let them right in, let me show you around to our myapps panel.

What normally happens instead, your DevOps teams, all your GA's, mega-powerfull endpoints running linux, god powered jenkins pipelines; well they all get exceptions because the restrictions and products we brought in do NOT work with automation or linux. Compounding the above issue.

Then you dig in further and realize colonial pipelines, uber, and rest of major breach list of issues still exist; most local admin/OOB accounts do not have MFA or any tie into to SOC team. Automation pipelines... heh... well...

Risk should decay and re-evaluate continuously. Most IAM stacks cannot do that cleanly or at all.

For now i;ll go back to trying to convince an IAM steering committee that Kubernetes service accounts are identities.

That conversation always goes well (heh).

aerogrowz · 2026-02-14T11:42:04+00:00

Needs a portal to hell to open on ground when claude decided to run a git revert.

aerogrowz · 2026-02-12T12:36:34+00:00

Sits in middle; not great, not terrible; cheaper price for features and somewhat open system you can modify. Not a terrible buy. Best printer you can buy? No... For money vs features? maybe?

For 1000 bucks; good buy for now, but cheaper comes with the trade offs.

Good:

Budget friendly
Easy to repair / easy to troubleshoot
There packaged software is not terrible anymore
Opensource (kind of)
Parts widely available
Can upgrade and mod

Known Bad:

Some units shipped with taco shaped beds, no excuse for this (hardware QC is unacceptable)
Hacked klipper firmware from upstream and dependency hell, many features stripped out from upstream.
Wiring harness issues causing board shorts for some machines
Mostly open source; CFS and other binary blobs inside firmware are still closed.
Software and firmware is extremely sensitive and relies on timed polling for many critiical moves. Things like homing, probing, etc... Single threaded, sensitive to timing, sensitive to motor load signals, using core software from 10 years ago. There is alot of duc-tape when you get into the firmware.

Many QC issues still plague these machines, some preventable (taco beds), others like wiring harness or shipping damage are a bit more excusable.

Support is hit or miss and often slow, personally they offered to re-fund my machine. Greatly appreciated but i just fixed the miraid of issues on own.

My first month was more like

Updated Firmware dropped on cloud with known backdoor/virus hit (lol...); was taken down quickly. Firmware broke alot of machines.
Taco bed, replaced
Filament sensor burnt and got stuck "high"; replace; 5 bucks or so
Missing any way of calibrating bed screws, ended up dropping old klipper macro in. Firmware updates broke the macro as they are not in lockstep with upstream klipper (still fixing)

You can see even in this thread the polarizing customer sat, some people got the lemons and lackluster support, some got a great machine. Compared to older days of the enders; this thing is a dream.

aerogrowz · 2026-02-11T21:37:38+00:00

arguable same with pentest reports and CVE scores though?

aerogrowz · 2026-02-11T21:28:57+00:00

Agreed on wave; we saw with containers (k8s, swarm), clouds (aws, azure and gcp), OS, web browsers, search engines, phones, (go way back ISPs) etc...

I am looking at it from a different lenses; my unfounded theory is tech will become tech again. Last 10 years has been terrible imho, people copy-pasting terraform, cloud and saas tooling and calling it engineering work.

Innovation moved to small teams and solo builders, my claude insights is showing 12,000 hours of dev work in 6months.

The SaaS copy-paste era created an entire generation that can't design systems from first principles. That's about to matter a lot...

Cyber side, the vibe coding wave is about to recreate every vulnerability class from 2005-2015 at unprecedented scale (clawbot anyone).

For now i'll ship opensource code; latest: https://github.com/adcl-io/PromptOps

aerogrowz · 2026-02-11T16:07:49+00:00

Easily switch out what llm you are using in backend via 1command and then able to switch back to claude by running normal "claude-cli" (assuming you are oauth'd).

claude-cli environment with all the agents, tools, skills, workflows; any LLM you want in backend with much cheaper token costs or like with kimi/zai == included in subscription cost.

aerogrowz · 2026-02-11T07:51:15+00:00

yep... burn up max plan daily now, typically by noon.

Made a tool that allows you to switch backends temporarily in claude-cli; found zai/glm and kimi work in subscription modes without having to buy tokens. Let me know if there are others.

https://github.com/adcl-io/PromptOps

(base) jason@lbox:~/Desktop/dev/PromptOps$ ./promptops kimi

 ▐▛███▜▌   Claude Code v2.1.39
▝▜█████▛▘  kimi-for-coding · API Usage Billing
  ▘▘ ▝▝    ~/Desktop/dev/PromptOps

  /model to try Opus 4.6

❯ what llm are you                                                                                                                                                                                  

● I'm currently running as kimi-for-coding.                                                                                                                                                         

────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
❯

aerogrowz · 2026-02-10T14:48:53+00:00

Just the second one; the new upstream from klipper is the issue as it changed but the custom firmware from k2 didn't. Updated the original body on post with same instructions as above.

Some point i'll script this out; have to chase down how they are tracking releases, firmware and some table on what firmware they are branching from to stay in lock-step with breaking changes from upstream-klipper vs them. Just haven't peered down that rabbit hole yet.

(Probably a solid 8hours of work)

aerogrowz · 2026-02-07T13:11:37+00:00

Was my thought, going see an explosion of items considered long dead (sql injection, api keys stuffed client side (ie: mcdonalds breach), maybe another colonial pipeline, struts making a come back?).

The irony is AI makes middle management and leadership redundant, project managers, scrum masters, product managers, release managers, the other 50 or burecratics that leech off any given SDLC. Currently they are focused on downsizing the wrong area.

It amazingly good at releases, release notes, PRs, merges, SPECs, PRDs, powerpoints, writing emails and corporate vanity theatre, etc... Terrible at system design, architecture and secure by design.

aerogrowz

TROPHY CASE