If you can automate something away quickly, you should do it. Writing the article is the part that provides value, and scheduling provides a way to write about things so that you don't need to do it on demand.
Internet attention works in such a way, that it's good for you if you get traffic. Increasing the amount of attention grabbing you can do with no extra effort is therefore valuable.
As a builder, this is also a fun hobby project to have while the baby is sleeping.
Most of the effort was for the implementation was looking for the right buttons to obtain tokens on LI's page, which made me feel like a archeologist looking at ancient ways of work. We also implemented an email-notification system that notifies me when tokens to various integrations are about to go stale, and I need to go clicking around to obtain new ones. I may outsource that to traditional browser automation when I get the 1st email in about 40 days.
Kalle Tolonen
10.9.2026
From my blog dashboard, a published article gets a pending LinkedIn row. One click asks our app to talk to LinkedIn - LinkedIn either accepts the post or returns an error. On success we record posted and move on. There are also drafts and a state machine that handles scheduled posts on a cronjob. We're Linux enthusiasts after all. Every software product ends up having a state machine at some point of its lifetime.

Could not find a sandbox for LinkedIn, so went straight to production and to the real people I know. A few bugs later works like a charm.
Well, obviously moar is moar, so dev.to and others are still to come.
No published comments yet.
Your comment is held for review before it appears publicly.