184 karma · joined January 21, 2025
Creator of Vigilance.
vigihq[dot]com phended[dot]com
Passing the buck to the Federal Government is not understanding the problem.
Which is one of MANY problems OT faces. IT best practices don’t suffice in OT and even when they do, most of these orgs are too resource hamstrung to do anything about all of the fires they have to put out.
Not to mention all of the OT vendors who flooded the market with tools instead of people being taught the boring process driven work.
Water is the most underserved sector for resources and yet it is the most critical for life. Unbelievable that it has gotten to this point and no one is sounding the alarm and doing anything about it.
What I found was pretty brutal. Companies asking for 4 years of agentic AI experience… pardon?
Then it hit me.
Oh they are all making shit up now and have no bar that anyone can hit because they are believing in the hype without understanding the fundamentals.
GREAT. Even as I climb the AI-Native ranks, I apparently am unqualified for any AI-Native job.
We are the virtuous ones that need to make the safest model for humanity, because we care more than “they” do. While at the same time saying that “coding is solved” but they still ship bugs themselves, and creating something that is capable of fucking up someone else’s infrastructure. It’s too far gone y’all.
Also, use cases? I’m a little lost after nailing down all the movement.
Can’t use for commercial purposes. Can’t opt out of training. Data retained.
Also this doesn’t take into consideration one of the ugliest sides of SSC which is M&A. Sure on a completely greenfield piece of software, seems like it would be a solution (although over engineered tbh). But that doesn’t really exist in closed source systems as they are Frankenstein pieces of software that get new stuff bolted onto them.
Most critical infrastructure orgs don’t have the budget to hire consultants, and even if they do, the deliverable is a deck, or a spreadsheet, or a PDF. We want to help any org of any size create a security regimen outside of these stale and disparate docs. For FREE.
Plus we have additional tools that we are building on top of the free software that will help in other areas besides policies and procedures. Like OSINT of any orgs operational and physical footprints.
For every one person that says they mind, it adds likely an additional margin of error AND time to their day. So I really disagree with making people’s lives harder. That’s why technology exists…
And more and more of these systems are on device models, not cloud compute. So I don’t see that argument either
I went through an acquisition as a Canadian software developer getting acquired by an American company. They wanted us to be called engineers like the rest of their SWEs but in Canada it’s a protected namespace. It’s illegal to call yourself an engineer without having the ring and the papers. Which personally I can appreciate.
Also I find that on greenfield, babysitting is a must, but once you have established your house style of patterns, abstractions, and baselines, you can let any of them roam free cause they will look for examples before going forward.
I agree with the sentiment though that if you let a swarm design and code your whole codebase, you will be lost in how it fits together. More feature bloat than code bloat though from my experience
AI is definitely on a scale of magnitude more but it has inherent value outside of “scarcity”. It’s actually quite the opposite with sheer supply/demand balance. Also investing in crypto made me less money than investing in myself by using AI to learn and challenge myself to think differently.
The guy uses Claude Code, same as me… it’s like a highly skilled mason with a chisel, against me with a chisel. I’m not going to produce the same masterpiece, because there is SME that underpins the accelerant.