Notes from people who ship this stuff

The developers who ship the work. They go out under a Codewerk Team byline rather than personal ones, because most of them come out of a project several of us touched. We use AI assistants while writing, the same way we use them while coding, and someone who has actually done the thing signs off on every claim. When an article says we tried something, we tried it.

There is no schedule and we will not pretend there is. Articles appear when a project throws up something worth writing down. Look at the dates on this page and you can see the real rhythm: clusters, then quiet weeks. Client work comes first, always. A blog that ships on a content calendar is a blog written to fill a content calendar, and you can usually tell within two paragraphs.

Yes — send the question you actually have to info@codewerk-it.com. Several pieces here started as a question from someone who was not a client. Two caveats: we do not promise to write it, and we will not write it as a favour to somebody's product. If the answer turns out to be short, you simply get the answer in a reply, which is usually what you wanted in the first place.

We can, but read the piece first. These are written so that a competent in-house developer can do the work without us, and often that is the cheaper answer: the migration checklist and the caching articles are things a decent team can follow on their own. Hire us when the problem is bigger than the article, when the shop is already bleeding, or when nobody in-house has the time to own it.