devotd.
About devotd
devotd is a technical blog about IT, AI, LLMs and local AI. Articles connect a new development to its practical consequences: what changes in an API, which costs matter, or what an operator should check before upgrading.
An argument readers can follow
We start with public evidence and explain why a detail changes the decision. Official statements and vendor measurements stay attributed. Recommendations follow from the stated conditions; reading documentation does not count as running a test.
Conditions belong beside the claim
A beta release, a planned rollout and a service already available are different things. Community experiences remain personal reports. Calculations state their inputs; actual experiments state their method and limits.
Dates that keep their meaning
Original publication and language-edition dates are preserved. Meaningful edits carry an updated time. Source-check times change only after a real source check. Timestamps use UTC.
Four complete editions
English, Korean, Simplified Chinese and Japanese articles share the same facts, caveats and sources. Useful reporting determines publication; there is no article quota.
Issue dates and actual publication
Our issue calendar uses Asia/Seoul (KST). A retrospective entry is assigned to an earlier coverage day and clearly labeled; it was not first published on that day. Articles retain their actual UTC publication and source-event dates. Feeds deliver stories by actual publication time.
Analytics and your choice
Google Analytics (G-R3KBJRM68D) loads only after you allow it. Google receives public page views and basic browser/device information; its network connection also exposes your IP address. We use host-only analytics cookies for up to 180 days and remember your choice on this browser for 180 days. We send canonical public page URLs without query strings or fragments and omit the referrer. Analytics stays off on previews, unknown pages and URLs with query parameters. We do not add advertising features, User-ID, profile fields or custom form events. Declining leaves reading and navigation unchanged. Withdraw in Cookie settings at the bottom of any page to stop collection and remove these cookies; already sent data is not recalled. Google may also process standard session and engagement events according to the property settings.