upvote
Imho the fundamental problem here is software & system complexity has grown to a scale where people (read: developers, system admins & the like) can't fully understand the tools they deploy. Or the implications of a failure somewhere.

That's okay if components are small, have well-defined boundaries / dependencies, are easy to inspect, and all that is rigidly enforced.

Obviously that's not where we are.

On the bright side: in most cases that complexity is self-inflicted, unnecessary, and can be side-stepped if so desired. Problems we're seeing don't occur by necessity: they occur because we've complicated many jobs more than those jobs need to be complicated.

Go back to first principles, cut bs wrappers around everything, and move on.

reply
It is exceptionally easy to make things secure if you are developing conservatively.

Kind of like how permissions model of deno. If you make everything closed by default and selectively open it is very easy.

Not putting credentials to everything in jira isn’t related to using of ai for hacking imo

reply