I welcome this "scriptability" improvement. I often have to do some bulk updates across a few dozen files and while I can whip up python or sed - I'd rest assured there's a more stable interface. but more importantly it opens doors to integrations with applescript and claude and whatnot
Tool calls with middleware. If you deploy an agent into a production system - you design it to use a set of curated whitelisted of bespoke tool calls against services in your stack.
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.
I spent 10 years in perl and created a lot in it - it taught me a lot about code as a culture,importance of tests, TIMTOWTDI, etc. I think I owe a lot to it.
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!
Maybe cmd.exe launch into "your terminal" - styled with starship or whatever, your shell aliases but taking the user into your (code?) projects' directories that they can have a nosey around with (mirroring github repos?)
Umm, the front-loaded 8k hours might not have much return if you were sedantary in the later decades (arguably the years where exercise helps stave off metabolic disease) as much as sustained levels of exercise all through life.
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.
I like the idea but I live in Europe and that and some skill issues couldn't get a route planned.
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.
Yeah, no EU support yet :S. I'm sorry for that. I'm working on it but for the EU it's really hard since i need to overlap the elevation DEMs (which countries make so hard to find high quality ones, and for EU it's split between all the countries). then that has to be overlayed onto the osm data and then finally computed into nodes etc.
But working on it! Schools also starting up soon so yeah, give me a bit :)
Nice! We'll link to this for our internal consultancy work.
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.
reply