Reach the Editors for Technical Commentary and Partnerships

The Right Place to Start a Conversation

Most contact pages read like a switchboard from approximately 2003. Pick a department, fill a form, wait three weeks, get a templated reply signed by someone whose job title contains the word "engagement." We don't do that here.

worldofbs is a small editorial operation focused on engineering culture, software architecture, developer tooling, and the occasional pointed opinion. The contact surface matches the size of the team. There is one email, and a real person reads it.

If you've landed here because something we published was wrong, useful, infuriating, or worth a follow-up — good. That's exactly the traffic this page is designed for.

Primary Contact: Garrett Vance

Garrett Vance runs editorial direction and handles incoming correspondence personally. No assistant, no triage layer, no auto-acknowledgement bot pretending to be polite.

Response expectations

Replies typically arrive within two to five working days. Thoughtful messages get thoughtful answers. Mass-blasted pitches with the wrong publication name in the salutation tend to sit in the queue until someone has coffee and patience at the same time.

What helps us reply faster

• A subject line that describes the actual subject.
• Context in the first two sentences — who you are, why you're writing.
• Links instead of attachments where possible.
• No follow-up nudge before day five. We saw the first one.

Business Inquiries That Are Worth Sending

We field a steady stream of business mail. Some of it leads somewhere. Most of it is recycled from a sales tool that auto-generates personalization tokens. Here's the rough split of what gets a real response.

None of this is meant as gatekeeping. It's an honest signal about what gets read versus what gets archived.

Press and Media Requests

Journalists and producers occasionally reach out for commentary on developer tooling, platform engineering debates, or the latest round of layoffs dressed up as efficiency. We're happy to engage when the topic overlaps with something we've actually written about.

Useful information to include

Send the publication or outlet, the deadline, the rough angle, and whether you need written commentary or a recorded conversation. If quotes need to clear a desk before publication, mention that up front — we'd rather know in the first email than the fifth.

What we won't do

We don't provide blanket endorsements of products we haven't used. We don't comment on companies under active litigation. And we don't recycle quotes given to one outlet for another a week later. That's not principle, it's just lazy on our part if we did it.

Partnerships Without the Buzzword Fog

Partnership is one of those words that has been used to mean everything from "co-authored research" to "please give us a free banner." When we say partnership, we mean a defined arrangement with a clear scope, a written agreement, and an end date.

Recent examples of arrangements that worked: a multi-month editorial collaboration with a tooling vendor where they supplied raw telemetry and we retained full editorial control, and an ongoing review-access relationship with two open source maintainers who let us road-test releases before public cut.

What we look for

• Editorial independence preserved. Non-negotiable.
• A defined scope. "Let's just see where it goes" is not a scope.
• Disclosure willingness. If it's paid or comped, readers will be told.
• Subject relevance. If the topic doesn't fit one of our engineering culture, software architecture, developer tooling, or industry opinions verticals, the answer is probably no.

Partnership conversations work best when the first email contains a concrete proposal rather than a request for a call to discuss possibilities. The discovery call is faster when there's something to discover.

What This Contact Page Is Not For

A short, honest list. We get these weekly and they all go to the same folder.

• Technical support for third-party products. We write about tools. We don't run their helpdesks.
• Account or login issues on other platforms. Wrong building entirely.
• Legal threats over coverage you didn't enjoy. Send those to counsel; ours will read them eventually.
• Recruitment outreach for unrelated roles. No, we are not hiring senior Salesforce architects.
• Generic link insertion requests. The answer is no, and it will continue to be no in six months when you follow up.

If you're unsure whether your message fits, send it anyway. A short note is better than a long apology for sending the wrong thing.

Before You Send Personal or Company Information

Email is convenient and decidedly not a secure channel. Avoid sending credentials, customer data, or anything covered by an NDA you'd rather not breach. For sensitive material, mention in your first message that there's something to share, and we'll work out a safer handoff.

How we handle information you send us is covered in the Privacy Policy, and the broader terms of engaging with the site live in the Terms of Service. If you'd like more background on who's behind the publication before writing in, the About page has the longer version.

Otherwise, the inbox is open: [email protected]. Write something worth reading and you'll get something worth reading back.