Developer, Advocate, and DevRel Expert

My core focus over the last decade has been building technical tools that are easy to use and loved by developers. Much of that work has been developer advocacy and relations. I've developed some strong opinions on the right and wrong way to do things. You can read about some of those opinions below.

I'm currently building Vewrite, a project management tool for technical writing teams.

Rami James

Thoughts on Software, Docs, and DevRel

I tend to write about my work, developer advocacy, and how we are supposed to think about the things that we do in our professional spheres. Some of these pieces have taken on a life of their own and sparked wider discussions within our community. Here you can find some of my favorites.

Reading Documentation Effectively
Reading Documentation EffectivelyReading documentation is a skill that can be learned. Let's talk about how to do it effectively so that you retain the most knowledge in the shortest amount of time.
Why Developer Relations Matters
Why Developer Relations MattersDeveloper Relations is a key part of any software company's growth strategy. Let's talk about how to build a successful DevRel program.
Docs Deserve More Respect
Docs Deserve More RespectA plea for more respect for documentation and technical writing in the software development industry.
Asking for help is a core developer skill
Asking for help is a core developer skillIntentionally or otherwise, I've been blowing up my life since last summer. It’s been less than ideal. We'll get to why in a second, but first, let's talk about everyone's favorite awful programming language and the impact of package managers, their packages, and the endless toil they create.
Package dependency hell
Package dependency hellIntentionally or otherwise, I've been blowing up my life since last summer. It’s been less than ideal. We'll get to why in a second, but first, let's talk about everyone's favorite awful programming language and the impact of package managers, their packages, and the endless toil they create.
The Work Structure Spectrum
The Work Structure SpectrumWorking on an Agile team can really suck. But, why? No structure at all sucks way more. We should talk about that, too.
Are your docs good?
Are your docs good?The primary challenge faced by technical writers often boils down to how to evaluate the effectiveness of what you write. You build some documentation and you think it is great. How do you know if you are right? How do you prove it to upper management? How do you really, really know?
Neurodiversity as software incompatibility
Neurodiversity as software incompatibilityMy days are taken up by thinking about two things: my kids and software. With neurodiverse kids, I think that they way we interact with them is akin to an API without documentation.
Use Verbose Comments
Use Verbose CommentsMigrations are the traditional way to manage the structure of your database. Supabase has a great way to manage migrations and we'll see how to use them in this article.

Recent Work

Over the past decade, I've founded or co-founded multiple startups, and have held leadership positions that helped guide products and teams towards success. Below you'll find some more in-depth descriptions of what those startups were, what they were trying to achieve, and my place within those contexts.