Recent searches

No recent searches

Search options

Only available when logged in.
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Administered by:

Server stats:

192
active users

eupolicy.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.1

#api

10 posts10 participants0 posts today
Continued thread
Alexander Hanff

So I an that opens a mixed space and anchors to the head of the user (creating a HUD effect).

Then I added wake word functionality so it would work like

Then I went back to my code and added some new compatible endpoints with

Then I connected my VisionOS app to the API... now I have a fully functioning AI Agent directly in VisionOS but that wasn't enough...

Miguel Afonso Caetano

"API documentation writers don’t just write content. We’re liaisons between client developers and in-house developers. I often say “we’re paid by the company but work for our clients.” Many think that in-house developers automatically empathize with the client developers. After all, they’re all developers, right? Right? Well, no. A surprising number of times, in-house developers are actually out of touch with clients. Why else would we be talking about having clear field names? They get tunnel vision or become myopic while in the code. This is not unique to developers. All professions have this risk. That’s our job to make sure that clarity is there for the clients. We can’t do it completely by ourselves. We need developer’s buy in. That means, one of two things.

We can push back on the in-house developers. When we see a meaningless, poor, or bad field names, for example, we have the right, if not obligation, to get it changed. Some developers may disagree. That’s OK. The truth is, the code doesn’t belong exclusively to in-house developers. It’s the client’s code. They’re the ones intended to run the code, to know which fields to pass in, with which values, and to read the response JSON. That makes it our code, too. We not only have to run the code but also to explain this to clients. We have a say in the matter."

robertdelwood.medium.com/writi

Medium · Writing for Humans: An API Documentation Writer WritesBy Robert Delwood, A Lead API Documentation Writer
#TechnicalWriting#APIs#API
zahntron

Please be gentle but I just shared my first project on #github I really want to see a #flatpak future for #DavinciResolve living on #Flathub or #bazaar Until then I'm working on a suite of add-ons specifically trying to transform #blender VSE to more closely resemble Resolve. My 1st effort is making a media browser to create bins and organize assets. Feedback & contributions are most welcome.

github.com/zahntron/VSE-Media-

#film#photo#photography
TrendingLive feeds
About