I also feel like calling the LLMs "Robots" is needlessly confusing. "AI" or "Agent" would have been more fitting.
They are just computer programs.
Why on earth is IT so bereft of creativity that it needs to invoke "robot". Robot is derived from a Czech word for forced labour or even slave. These things don't go "diddly diddly deep" like Twiggy, nor whatever R2D2 beeps. They are certainly not physical, which is attribute one for a "robot" (it's a thing not a non thing).
If you replace the word robot with the word wankery, the article really starts to make sense. When you encounter various declensions and conjugations and so on, be careful to keep it real.
This kind of isolation is nice. Next logical step would be some way to prevent Fly from having access to the tokens.
fly.io should keep building great UX because robots will evolve in a direction of behaving more like humans - for example with more and more browser use.
The main area of divergence that’s emerged so far is auth (mentioned) & no doubt there’ll be others but it’s still 99% overlapping.
Making things nice for humans also makes it easier to audit your agent’s actions later.
To the folks at fly.io - don’t take focus off the UX/DX because it’s a decent chunk of the RX. And because we love it.
Indeed, is it kind of joke which is not joke from Fly.io perspective? Humans who have learned CS for 5 years and can create JIT compilers cannot understand systemd?
On the other hand, I'm still in a shock after realizing that you can't expect Frontend dev guy will be able to clearly explain which CORS headers and values they do need - they just keep saying "CORS not working, fix infrastructure!" and not learning MDN by heart.
