Press and media

Credentials, briefings, and coverage requests.

The editor is available for event coverage, vendor briefings, product launches, technical analysis, and interviews. The publication’s focus is software architecture, AI in production, security and privacy, fintech, startups, and technology history.

For press contacts

Publication: RoamingPigs Field Manual
Editor and publisher: Cisco Caceres
Email: editor@roamingpigs.com
Phone: +1 (702) 907-7411
Mailing city: Las Vegas, NV
RSS: /field-manual/feed.xml
Newsletter: Sunday digest, double opt-in, one-click unsubscribe.

Editor

Cisco Caceres, editor and publisher. Toggled his first program into an Altair through front-panel switches in the late 1970s and ran BBSs at 300 baud in the 1980s. US Navy veteran (USS Missouri BB-63, Desert Shield and Desert Storm). Built the CMS behind MSNBC in the 1990s, and worked AS/400 and ES/9000 mainframes in RPG, COBOL and FORTRAN through the consulting years. Ran a 60-server data center in his basement before AWS existed. Scaled a push platform to 3,000 cloud instances in the 2010s. Spent roughly twelve years in speech recognition, including voice AI for federal agencies in the 2020s. Holds patents in context-sensitive sites, data encryption, walkie-talkie network analytics, and adaptive speech recognition. 45+ years in software. Full masthead at about.

Where the name comes from

The editor and his late wife, the artist Mariajuanita “MJ” Guzman (1982–2025), donated everything they owned and travelled the world together for over eight years. They called themselves the RoamingPigs because they loved to travel and eat. The publication exists partly to help fund the Mariajuanita Guzman Art Foundation, which supports emerging and financially disadvantaged artists.

Publication stats

Independence

No advertising. No sponsored content. No paid placement or affiliate links. No parent vendor. RoamingPigs, Inc is a Delaware C Corporation owned by the editor.

The editor runs other technology ventures, and any article touching a company he has an interest in carries an inline disclosure. All outside interests are listed at disclosures. Consulting work lives on a separate site, ciscocaceres.com, and the Field Manual carries no CTA for it.

Corrections are made in the article itself, at its original URL, so the published piece is always the accurate one. Report an error to editor@roamingpigs.com.

Representative articles

Credential applications

For event organizers reviewing media credentials: the Field Manual is independent (no parent vendor, no advertising), published continuously since 2024, and has a documented editorial policy covering sourcing, fact-checking, and corrections. Coverage is published under a named byline at a stable URL, indexed by search engines, syndicated via RSS and the Sunday digest.

Sample credential application language:

I’m requesting media credentials to cover [event] for RoamingPigs Field Manual, an independent technical publication. Expected deliverable: a 1,500 to 2,500 word analysis article within 7 days of the event, plus interview notes if relevant. Editor of record: Cisco Caceres. Archive: roamingpigs.com/field-manual/. Editorial policy: roamingpigs.com/editorial-policy/.

Press kit

Everything a desk normally asks for is on this page already, so the download is a convenience rather than a gate. The zip contains the publication logo (SVG, white-on-dark SVG, and PNG at 256, 512 and 1024), the editor headshot, the editor bio, five sample articles as plain HTML, a contact card as both text and vCard, a summary of the editorial standards, and a letter-of-assignment template.

Download press kit (zip)

Letter of assignment

Independent and staff-of-one publications are turned down for credentials more often over a missing assignment letter than over anything about the publication itself. The editor issues his own; the fillable version is in the press kit, and it can also be requested directly at editor@roamingpigs.com with the event name and dates. Expect it the same day.

What we cover, what we don’t

In scope: AI conferences, cybersecurity events, developer conferences, fintech and crypto events, startup and founder events, SaaS and product launches, cloud and infrastructure events, vendor briefings and analyst days, technical product reviews.

Out of scope: entertainment, sports, politics, lifestyle, consumer reviews unrelated to engineering. If your event sits outside the coverage areas above, the answer will usually be no.