Does this extremely funny case count? Regular malware that asks claude what it should steal from your workstation, using your claude credentials. (This is the only thing remotely resembling an AI powered attack I'm aware of and its very silly)
x0rcist
joined 1 month ago
I see this kind of attitude on lemmy in privacy spaces a lot, and honestly I think that it reflects on being more interested in security and privacy as an abstract concept than as something that actual humans need to practice.
The thread is going very well, someone decided reading was hard and that asking claude was easier
Highlights:
So I asked ChatGPT 5 Thinking, Claude Sonnet 4.5 with Extra Thinking, and Claude Opus 4.1 with Extra Thinking whether the article linked to multiple times provides any hard evidence of DHH being anything implied by the name-calling or by the outright name-calling seen in this thread.
Turns out the machines say there is no such evidence. It’s just an opinion piece.
The zone has indeed always been flooded, especially since its a title that collides with "integration architect" and other similar titles whose jobs are completely different. That being said, it's a title I've held before, and I really enjoyed the work I got to do. My perspective will be a little skewed here because I specifically do security architecture work, which is mostly consulting-style "hey come look at this design we made is it bad?" rather than developing systems from scratch, but here's my take:
Architecture is mostly about systems thinking-- you're not as responsible for whether each individual feature, service, component etc is implemented exactly to spec or perfectly correctly, but you are responsible for understanding how they'll fit together, what parts are dangerous and DO need extra attention, and catching features/design elements early on that need to be cut because they're impossible or create tons of unneeded tech debt. Speaking of tech debt, making the call about where its okay to have a component be awful and hacky, versus where v1 absolutely still needs to be bulletproof probably falls into the purvey of architecture work too. You're also probably the person who will end up creating the system diagrams and at least the skeleton of the internal docs for your system, because you're responsible for making sure people who interact with it understand its limitations as well.
I think the reason so much of the advice on this sort of work is bad or nonexistent is that when you try to boil the above down to a set of concrete practices or checklists, they get utterly massive, because so much of the work (in my experience) is knowing what NOT to focus on, where you can get away with really general abstractions, etc, while still being technically capable enough to dive into the parts that really do deserve the attention.
In addition to the nice markers and whiteboard, I'd plug getting comfortable with some sort of diagramming software, if you aren't already. There's tons of options, they're all pretty much Fine IMO.
For reading, I'd suggest at least checking out the first few chapters of Engineering A Safer World , as it definitely had a big influence on how I practice architecture.