ARTICLES WRITTEN FROM
REAL PROJECTS
INSIGHTS FROM THE STUDIO FLOOR.
VERTICALS COVERED FROM AI TO
OPS
AVERAGE READ — LONG-FORM, NO
FILLER
Notes from people who ship. Case studies, technical deep-dives, opinion pieces and playbooks — written by the team that builds, not a content marketer who doesn't.

Ruslan Krylov
Editor · krylov®
Writing is how we figure out what we actually believe
A short showreel of the work behind the words
Every article on this page started with a problem we hit in production. We publish what we wish we'd read before the bug, the rebuild, or the rewrite.

Ruslan Krylov
Editor of the krylov® journal
FOUR THINGS WE WRITE — AND NOTHING ELSE.
No SEO landfill, no AI slop. Every piece is written by someone on the team who actually shipped the thing it's about.
Jump to the archiveMANIFESTO
Long-form is a commitment to thinking. If we can't explain it in 2,000 words, we don't understand it well enough to ship it.
Beats we keep returning to.
Four beats we keep returning to. Each topic compounds — read the latest, then dig back into the archive when you want the full thread.
The full shelf — filter by topic.
Sorted by recency. Filter the list to a single topic, or scroll all of them. Article-level deep-links open in the same view.
News from the studio
and our companies
Announcements, milestones and partnerships — what is happening at Creative Ventures and across our portfolio companies.
Releases worth
your attention
Product launches, version bumps and public betas coming out of our client work and in-house experiments.
Selected portfolio
of recent work
Projects we have shipped end-to-end — from the first research call to production deployment and growth.

Trywishboard case study: multiplayer collaboration without killing focus

Last-mile logistics software case study: replacing spreadsheets with realtime dispatch

Privacy-first social app case study: Blured, from whiteboard to 12,000 users
Parsewise: AI-Powered E-commerce Assistant

AI Chief: AI-Powered E-commerce Assistant

Roguelike CLI: Turn Your Backlog into a Dungeon Crawl
Research, essays
and playbooks
Longer-form writing on product, engineering and the craft of running a studio — lessons, playbooks and postmortems.
What readers wrote back.
Replies, not metrics. Unsolicited notes from engineers, founders and PMs who took the time to send a paragraph back.
· On Evals
Their write-up on agent eval suites saved us a quarter of trial-and-error. Sent it to everyone on the team the same afternoon.
· On Architecture
I read three of their posts before our discovery call. Felt like the team already knew us — because the posts knew the problem.
· On Hiring
Honest about what didn't work, which is rare. The retro on a failed migration was more useful than most postmortems I've read.
· On Process
No fluff, no SEO bait, no thought leadership theatre. Just engineers thinking out loud — exactly what I subscribe for.
A journal kept honest — by the people who wrote it.

Average article length — long-form by design

Of pieces written by someone who shipped the project
About the journal — questions we get most.
Roughly twice a month. We hold pieces back rather than ship filler — when there's nothing worth saying, we say nothing.
Get the next one in your inbox.
One email per published piece. No marketing, no roundups, no nag campaigns — unsubscribe with one click whenever.
Email newsletter
One short email each time a new piece lands. Plain text, no tracking pixels, no growth-hack drip.
/02RSS feed
Full-content RSS at /resources/rss.xml — pipe it into your reader of choice and skip the inbox entirely.
/03Follow the studio
New pieces also cross-posted on LinkedIn and X. Same writing, slightly louder presentation.
/04Write back
Reply to any newsletter, or email the editor directly. We read everything — half the posts started as reader notes.
















