unop
Joined 8 years ago
Joined 8 years ago
Also, You should never connect an agent directly to a sensitive database server or an order/fulfillment system, etc. Rather, you'd use "middleware proxy" to arbitrate the requests, consult with a policy engine, log processing context, etc before relaying the requests on to the target system.
Also consider subtleties in the threat model and types of attack vector. how many systems the agent(s) connect to concurrently. See the lethal trifecta https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/
I found myself defending it more and more online against the folks who were nay sayers - those who complained about its syntax and it's quirks - but that wasn't a problem for unixers who used sed/awk/vim and all the other arcane tools. Perl wawa means to and end and it was the best tool to reach for (the glorious Swiss army knife).
I guess there was an infection period - the brain drain to python and Ruby meant it was harder to find decent quality libs on CPAN anymore as folks would only do things in python. And Yea, while CPAN is still rich, it's not the first hit on Google anymore.
Today, the map-sort-map Schwarzian transform is still the easiest to do in perl than any other language and it helps me whip up the throwaway scripts quick. Wouldn't change the language - I really love it!
Hey claude, help parse .. Ohh wait.. claude says I've spent up all my weekly credits (twat!).
Gemini.. Hey.. Go to school on this one...
"Do you know how much the world outside a small group of people hates* AI?"
I mean, we all know of the university budding sports star types who probably invested in many hours training and trying to break into their sport professionally but not quite cutting it - and then "retiring into mediocrity" with the regular 9-5,2 hour commute, 3 kids and the diet to match. They exercise no differently to the regular Joe and suffer all the maladies the same.
It takes a certain adaptation to reach this level of fitness - and it should be no guess how you get there.
It would be nice if the route start and end selections could be from points ona map (for the outdoorsy types like me) as the text fields find nothing for me.
The landmark and node Explorer modes didn't show any results.
It'd be nice to show the other dimension of the git branching strategies to apply. Github flow/feature-branches vs per-env branches of main vs git flow. How and when to apply changes in different environments - before vs after PRs, etc.
I.E. A code/solution review must also consider the documentation alongside the feature or solution.
This implies that the documentation is (held beside) source code too and can be diffed/compared e.g. Markdown for text, mermaid/graphviz for diagrams and that this can be built, rendered or published easily/readily (Hugo, zola, etc)