My office looks out on the final approach into LGA, every once in a while I’ll spot a plane out of place (typically doing a go around) and spend twenty minutes with flight radar 24 and LiveATC trying to figure out why. This would make it so much easier!
Like all other problems of the future, this too can simply be solved by throwing more AI at it. The next great work of the frontier labs must not merely be to replace human labor, but also human consumption. With the ouroboros so complete, all such petty human economic concerns will cease to have relevance, as we all cleanly divide out of the equation at last.
That didn't stop any of the previous financial bubbles, financial crises, and progress-induced suffering.
If you make it through the devastation, you'll be one of the richest and most important people in the world. If not, throw a random frontman in front of the wolves and disappear into the background.
This case not withstanding, Apple regularly includes patches to the built in CLI tools in security updates, so it's a little disingenuous to suggest those tools are not really supported.
I read GP as a descriptive comment not a justification. They are showing with this issue that they don’t truly support the cli tools in a way we ought to rely on. Whether they occasionally provide some support doesn’t mean they’re supported. Only full and competent support counts, everything else counts as “it’s best-effort at best”
If you’re not upgrading your deps and rebuilding your rust project this morning, you’re pretty likely exposed to eMudhra. If your project was “done” a few years ago that’s likely not going to be easy.
Kind of, except as product manager you're held accountable for delivering the right product, while your engineering team is held accountable for things like performance, incidents, and security issues caused by their code.
It's hard to hold an LLM accountable for anything.
Accurate but manageable. Just like a pm works with properties an engineer also does. The Product person wants to deliver the right product properties so they model their process around identifying the ones they want and then creating the right framework to get them. On the engineering side its the same thing. Define what you want, give agents an environment they can succeed in, iterate.
> The Product person wants to deliver the right product properties so they model their process around identifying the ones they want and then creating the right framework to get them.
You can try model all you like, but eventually you have to go argue with finance because you work at Snowflake and your new SaaS product needs a new SKU and is slightly different than this other offering because it has enhanced security on larger storage.
Don’t forget there is a new manual process for troubleshooting this because it overlaps with another feature potential that we found in testing. You need to go make sure your Customer success team is aware of this and has at least some internal documentation.
Ah crap your sales director says they had 2 other competing features that take priority over your feature to train up Sales Engineers to cross sell. So you have meet with existing customers to try and garner interest and also work with comms to make another product release post with higher visibility.
Oops do forget to grab your next ticket for next sprint that just started from Jira, since you are a dev too.
reply