Spyke

Replies

Comment on

Works going full AI crazy. 10x the amount of projects, only half work

Reply in thread

It comes down to knowing what a UX is, and how everything underneath works together. This is "computers" all over again. Growing up alongside the evolution of the stack gives you a special background in what goes wrong, why it goes wrong, and how to fix it. Jumping into it when it's gotten so abstracted it's not possible to understand the stack from the ground up is where this sort of slop comes from.

Comment on

CVE Tracker

Reply in thread

Isn't it? They were always there, but now they're visible and being fixed (hopefully), and aren't available for exploitation in the future. Up to now, it was security by obscurity.

pics

Comment on

Sandy gave herself a hat. I did not appreciate it lol.

Sorry to hear about the puppers. What did they get into, if you don't mind me asking?

On the horses, every time I get off my QH gelding after a ride or cow move and take off his halter in the pen, he has to roll around in the mud and shit to get the stank of human off him to feel better. Then he looks at me like "you made me do this, asshole". He's always a mess when I get him to go to work, sometimes I think I should try to get him used to a pressure washer...

Comment on

For users with public facing services: How does the current explosion of AI-discovered vulnerabilities affect your threat model and willingness to be public facing?

I have my ops agent constantly checking SBOMs against current CVEs and if something triggers, I get a report with severity and repair options researched. I can then decide how I want it to proceed. I'm much less concerned about internal only services. SBOMs are refreshed after updates for future checks.