When a song gets a remix it's still a song.

Anything could change: genre, lyrics, instruments, melody – there aren't really any rules except one: it is derived from the original. Its essence remains intact.

You can think of your content the same way – once you release it, does it deserve a remix?

Remixing developer content could:

  • Target a different persona (genre)
  • Use a different SDK (lyrics)
  • Change the angle of approach (tone)

Let's say you just published Getting Started with XState and React. In this case, the essence is an introductory tutorial that covers the basic concepts of XState and aimed at people who are already familiar with XState.

Remixes could be:

  • Better State Management with React – Change the persona to someone who isn't aware of XState yet and is frustrated by whatever state management they're using (hopefully not XState, hah!)
  • Getting Started with XState and Angular – Change the SDK being used
  • XState and React, swipe left or right? – Change the tone of voice or angle

Some ideas for when remixes could make sense:

  • Remix popular content to reach more audiences
  • Remix a past piece that didn't resonate into a better targeted one
  • Remix after refreshing your brand strategy

Remixed content may be tweaked or changed – but you'll always hear Britney Spears.

Remixing content

Wouldn't more devs using your tool be lovely?

I'm a consulting developer experience engineer and educator who helps developer tools accelerate adoption. I can lower your initial learning curve so developers can get to Hello World faster and start building cool stuff with your APIs and SDKs.
Get Daily Tips