#Development #Analyses
Google’s Prompt API · Web standards should not become terms of service https://ilo.im/16cqh1
_____
#Business #TOS #Google #Chrome #AI #Browser #Privacy #OpenWeb #WebStandards #APIs #WebDev #Frontend
#Development #Analyses
Google’s Prompt API · Web standards should not become terms of service https://ilo.im/16cqh1
_____
#Business #TOS #Google #Chrome #AI #Browser #Privacy #OpenWeb #WebStandards #APIs #WebDev #Frontend
That seems a bit similar to what I currently do... ;-)
"To use an analogy about my process, compare the scenario to a senior tech writer (TW) working next to a junior TW, where the senior TW mostly provides observation and feedback (in this analogy, the junior TW represents the AI agent). The junior TW creates some docs and presents them to the senior TW, who leaves comments explaining what needs to change. The junior TW takes notes about all the feedback in a journal. By the end of the process, the junior TW has three pages of notes.
After the process finishes, those notes aren’t lost. They form the basis of the SKILL file. The next time the senior TW sits down with another junior TW (a different one, as the session changed), the new junior TW produces much better output thanks to the notes. With each iteration, the notes get more detailed — anticipating common errors, adding validation checks, laying a foundation so that each step doesn’t build from faulty information. After a dozen iterations, the senior TW finds they have less and less feedback to give.
Eventually, the senior TW no longer needs to sit next to the junior TW in close observation. The junior TW proceeds autonomously through each step in the SKILL and just shows the final result. One key difference from real mentorship, though: the AI agent doesn’t carry any memory between sessions. It reads the SKILL file cold each time. All the “learning” lives in the document, not in the agent. This makes the SKILL file itself the critical asset — if it’s vague or incomplete, the agent’s output regresses immediately."
https://idratherbewriting.com/blog/internal-skills-release-docs
#TechnicalWriting #APIs #APIDocumentation #Skills #AgenticAI #AI #GenerativeAI #LLMs #SoftwareDocumentation
My hypothesis this year around AI was that if I develop some agent skills to speed up repeatable processes, it might clear up my bandwidth and free up time for me to work on non-repeatable doc tasks. It appears to be working.
#Development #Releases
New in Chrome 148 · Lazy loading for video/audio, Prompt API, and more https://ilo.im/16cpen
_____
#LazyLoading #AI #Chrome #Browser #APIs #WebPerf #WebDev #Frontend #HTML #CSS
Alvin Ashcraft presents 'Build intelligent apps with WinUI, Phi Silica and Microsoft Foundry' at Nebraska.Code() this July.
https://nebraskacode.amegala.com/
#microsoftfoundry #ArtificialIntelligence #windows #APIs #SDK #WPFApplication #csharp #phisilica #copilot #foundrylocal #recall #Microsoft #Software
Computer Use Is 45x More Expensive Than Structured APIs
https://reflex.dev/blog/computer-use-is-45x-more-expensive-than-structured-apis/
#Development #Analyses
The duality of AI models in the browser · “I’m bullish, but also have concerns.” https://ilo.im/16cnmd
_____
#Prompting #AI #LLMs #SLMs #Chrome #Browser #PromptAPI #APIs #WebDev #Frontend