Independent Advocate
Hi, I'm Paul. I act independently to create content that drives awareness of products, features and services.
On this page you'll find information about my approach to Product Marketing, Developer Advocacy... and a little something I like to call Bundles.
About Me
I've held various positions in and around Advertising, Tech and Product Development in both full-time, and freelance positions since 2005.
I sit somewhere between Product Marketing and Developer Advocacy. I specialize in the creation of technical content for educational and promotional purposes.
You can read more about me on the About page.
It's Not About Me!
I'm not a tech influencer and I'm not interested in building my own online brand.
I'm passionate about technology and I liked being an Engineer but, what I really LOVE to do is: design, develop and write.
Bundles
Usually it takes a team to create go to market assets, but since I'm multi-disciplined, I'm able to take your marketing message and bring it to life using a number of different techniques.
Bundles consist of, but are not limited to:
- Written Content
- Demo site / application
- Open-source GitHub repository
Extra Small Bundle
Written content with code snippets as part of the article or post.
Content can be published on either your company blog, or by a suitable external publisher.
- Smashing Magazine
- Getting Started With Neon Branching
Small Bundle
Written content with sample code publicly available on GitHub.
Content can be published on either, your company blog, or by a suitable external publisher.
- Open-source Repository
- https://github.com/PaulieScanlon/neon-edge-analytics-astro-sample
Medium Bundle
Written content with production code publicly available on GitHub and a demo site/application deployed to your domain.
Content can be published on either, your company blog, or by a suitable external publisher.
Case study: How to use Postgres at the Edge- Neon Blog
- How to use Postgres at the Edge
- Open-source Repository
- https://github.com/neondatabase/ping-thing
Large Bundle
Written content with production code publicly available on GitHub and a demo site/application deployed to your domain.
Content can be published on either, your company blog, or by a suitable external publisher, with additional supporting content that mentions, and links back to other assets from the Bundle.
Case study: What Is the CockroachDB Cloud API- Cockroach Labs Blog
- What is the CockroachDB Cloud API and why should you use It?
- Smashing Magazine
- How To Create Dynamic Donut Charts With TailwindCSS And React
- Open-source Repository
- https://github.com/cockroachdb/demo-cloud-api
Extra Large Bundle
Written content with production code publicly available on GitHub and a demo site/application deployed to your domain.
Content can be published on either, your company blog, or by a suitable external publisher, with additional "how to..." supporting content that mentions, and links back to other assets in the Bundle.
Case study: The Art of Data Residency and Application Architecture- Cockroach Labs Blog
- The Art of Data Residency and Application Architecture
- The New Stack
- How to Create a Multi-Region Node.js Lambda API
- Open-source Repositories
- https://github.com/cockroachdb/demo-data-residency
- https://github.com/cockroachdb/demo-data-residency-api
- Social Assets
- https://x.com/CockroachDB/status/1682529684032987137?s=20
- https://x.com/CockroachDB/status/1661032283694940161?s=20
Sample Vs Production
You may have noticed in the Bundle descriptions I've used the terms; Sample code and Production code.
They are different, and here's why.
Sample Code
Sample code repositories contain just the code that matters, and are usually quite ugly to look at.
They can be used for educational purposes but are less suitable for promotional purposes.
Sample code will be hosted on my personal GitHub account. Links will use a default, ".app" URL.
For Example:Production Code
Production code repositories contain all the code that matters plus, everything that makes a demo look pretty!
They can be used for promotional purposes but are less suitable for educational purposes.
Production code will be hosted under your company's GitHub account. Links will include your domain name.
For Example:Deploying a demo to your domain is made possible by using a Proxy Redirect. You can read more about how this approach works, here: What Is a Proxy Redirect?
Which route to take will be determined by the project's primary objective. Both have their place in the world and I'll work with you to figure out which way to go.
Independently Different
Generally speaking, developer content looks like it was created by a Developer, and whilst Developer Ready is fine, Production Ready is better!
If your product or service is aimed at JavaScript developers, we should talk!