264 karma · joined February 24, 2019
As a DevOps Engineer, I never once saw before the advantage of using a classifier. Now I see multiple parts of the stack where a better level of expressiveness will be useful (PR validations, Blue/Green validation, notification router for alerts, quick smoke tests, etc).
Nobody will give us the time and budget to build a custom classifier for these use cases, but a simple API call yes.
It's the killer feature from me personally, often when wanting to troubleshoot for example things like Kubernetes workloads. LLMs are now really good at it, but we doesn't want them to like delete a pod.
Other harnesses like Codex have often on static rules, like the allow/deny of claude code, that can filter out based on regex. It's quite good already, but sometimes the model can find a way to write something that wasn't anticipated, or in a convoluted way.
After, I guess it's something that can be added in an open-source harness like Pi, and add like this new Jev model or something else equivalent
If the money could flow back to the real economy instead of the AI economy, it might be healthier for the whole system.
I didn't knew about that rationale. I thought Defense-in-Depth was all about that, preventing security incidents even when an attacker start to get some elevated privileges on the system?
If not, that's quite a practical reference for future CyberSec meetings.
The main goal is PoE or PvP, but actually I ended up fully playing for the economy.
You can get a job with its own leveling system, like a farmer, cutting crops, collaborate with a baker who will make you a cut so that he can get baker xp, and then sell the bread in an auction based local marketplace for player to buy and heal.
You can as well just arbitrage: buy something cheaper in one town, and sell it in an another where it was more popular.
I ended up with a tone of paper notes, just calculating the margin of different product, e.g jewellery, so that I can buy the materials, calculating the risk of loss during the building process, partner with someone for some materials, and then finding where to sell the end product
For example, we never had time to learn well for example CI/CD in my years.
It's something that takes time to build (feedback loop is around 10 to 20 min for pipelines, instead of 1 min when coding something), and become quite costly for trial and error in term of time.
But it's now 60% of my work as DevOps Engineer, and a big part of other devs/lead devs work. They are a lot of good and bad practices.
We could imagine a class to learn about how to build proper CI/CD pipelines and experiment --> philosophies, different patterns, testing different caching strategy, etc
Oil + GPS + Web Search --> "LLM > You have 50 Km of autonomy. You can go today to this cheaper oil station, at 20 km, on your GPS road, instead of the one near your home. The one at 10Km is closed as well due to a local strike, I will avoid it too"
You can of course script all the scenarios + only use a TTS model. However, when plugging different systems together, I feel that it's the sweet spot where LLM is shining --> no need to pre-plan every scenarios that the user will ask, it can be done on the fly
- People that didn't read the manual (actually almost all of us), like: explain a warning signal
- Or integrate different systems together: `I saw that on your GPS you want to go to this place, but in 2 hours it will be snowing heavily there. Please remember to bring your snow chains'
It's more a reward for a competition-style work mindset.
I think as well there is currently the following: AI still needs an operator, in the same way than a bulldozer needs a bulldozer operator. And like with bulldozer, there are always something that business stakeholder wanna dig, now that digging is faster.
Meta would really benefit from work done on this front, however their model Llama Guards are quite lagging compared to the competition.