Ship the article on the same schedule as the launch.
Write it once in Ocoya and DEV gets a real article — your first line as the headline, your post as the article, your hashtags as tags — published at the hour you picked.
gridlines
Posted just now · 6 min read
We deleted our cache layer and got faster
The read path was the problem
Every request hit Redis before it hit Postgres, and Postgres was answering in 1.2ms anyway.
A caption in, an article out.
DEV is where developers go to read, not to skim a feed. A post there is a full article, and the composer you already use becomes one: your first line is the headline, the rest is the article, and your image becomes the cover at the top of it.
- Headings, code samples and lists arrive intact
- Your headline is not repeated at the top of the article
- Write your own headline instead and your post is left alone
Hashtags that would be rejected, fixed on the way out.
Tags are how readers find anything on DEV, and DEV is fussy about them — four at most, letters and numbers only. Write hashtags the way you write them everywhere else and Ocoya tidies them up on the way out, rather than letting DEV turn the article down over a dash.
DEV tags cannot hold a dash, so #web-dev becomes webdev instead of being thrown away. DEV takes four, so the fifth is left off rather than the whole article being turned down.
An article, with an article's rules.
These are DEV's own rules, not ours — worth knowing before you plan a series around it.
Connecting takes a key you copy from your own DEV settings, under Extensions — DEV does not offer a sign-in button the way the social networks do. One thing worth planning around: DEV only accepts one article every thirty seconds, so spread a batch of scheduled articles out rather than stacking them on the same minute.
One draft, the article and its announcement.
The long version goes to DEV, the short version to X, LinkedIn and Mastodon — each under its own limit, each at the minute you choose. The write-up and the posts pointing at it stop being two separate jobs.
How publishing worksTurn releases into articles
A feed trigger and an AI agent are enough to draft the write-up for every release, ready for you to approve and publish on the schedule you set.
See WorkflowsYour next write-up, already scheduled.
Connect DEV.to and queue an article in a minute.



