Content Is Code

Talk transcript

1. 0:00

   So if you've ever created content, you know it can be hard. And what's often most hard is choosing a medium for how you'd like to communicate. Do you write a blog post?

2. 0:09

   Do you create a video? Do you go out and speak at a conference? And even of these things, you're likely to select something that you're good at or you have experience doing.

3. 0:17

   But the idea I want to present to you today is that increasingly, code is becoming the way that we communicate. Now, this might seem obvious in twenty twenty-six, but I want to point out that even a couple of years ago, this was wild because the only people that were writing code to create content were professional software engineers.

4. 0:34

   And often, professional software engineers are spending their time doing mostly engineering and are not getting that deep on content. Now, what do I mean when I say content? Well, I'm talking mostly about technical communication, and that could be documentation, it could be things like changelogs, emails, product marketing.

5. 0:51

   It could be video, which I create a lot of. Um, and it could be other things associated with a typical DevRel motion, but it's not restricted to DevRel, right?

6. 1:00

   Content or technical communication is the act of communicating what a, what problem a product really solves, and that can be done by anybody. That might mean really complete accurate documentation that covers every part of the data access framework.

7. 1:14

   It could be changelogs shipped timely, um, with robust assets that cover all areas of a product. This is something that's often overlooked. This is actually really hard because to have an accurate changelog, you have to have an accurate diff of your product.

8. 1:28

   Or you could just have someone that spends a lot of their time combing through PRs to try to figure out what was shipped. It could be things like timely product updates, emails which kind of follow from a changelog, right?

9. 1:40

   If you understand what changed, you can then summarize that over time for your users. It could be something as simple as a homepage product tour instead of a static screenshot.

10. 1:53

    These are all ways that we're communicating products. We're communicating what this thing does or how it's changed via either written content, um, uh, free-- via code, via distinct assets.

11. 2:09

    It could also be something like video overlays, right? Something like, uh, adding a bit of, um, engaging material to the content that you create. But increasingly, where I think this is headed is entire product surfaces and entire videos generated via code.

12. 2:26

    And in front of me, I have a product tour for Conductor that was built entirely with React and Remotion. So basically, I recreated the product surface. I used a Remotion scene to recreate the product and do a full walkthrough, um, of a sample user flow.

13. 2:43

    Now, it's not perfect, it's a little buggy, and the flows aren't quite there yet, if I'm being honest, but I think we're moving towards a world where this is normal.

14. 2:52

    So my name is Matt. I was previously a data engineer, then I led DevRel at Replit, and now I lead developer experience at Conductor. And today, I wanna talk about how content is shifting left to code as the source of truth.

15. 3:07

    And so I think there are three distinct eras we can think about here. Era one, the handcrafted era of content. Era two, an era where code existed, but it was quite expensive.

16. 3:17

    And era three, where code exists, but it's very cheap, and that's where we are today with AI. So in the handcrafted era, right, everything is manual. The only levers we really have are time and money and skill.

17. 3:31

    And so if I want something, I either need to create it myself, but there are only twenty-four hours in a day, so likely I'm gonna go out and seek an expert, someone that does know how to create this thing.

18. 3:40

    Maybe that's an agency or someone who creates these assets professionally, if I'm thinking about, like, motion graphics, for example. Now, post era one, when we had expensive code, code and cloud are mature assets.

19. 3:55

    These are things that have existed for a while and most professional software engineers know how to use. Engineering is now the bottleneck. This is like Zerp era. Everybody's paying a lot for engineers, and to get anything done, you really need professional software engineers.

20. 4:11

    So you'd better pay someone, maybe not an agency, but an engineer. And that included things like, you know, um, robust documentation or even just a website, right? You-- Back in the day, it's hard to imagine before AI, you wanted a website, a good website, you needed a front-end engineer or, like, a low-code website service, but those weren't

21. 4:29

    any good to begin with. So you needed a professional engineer to have a really nice website. And what that meant was that content is really not the priority, right?

22. 4:38

    Because if you're a professional engineer, you have better ways of spending your time. And I think this is reflected by, um, libraries like Remotion, frameworks like Remotion, um, not proliferating the way that they are today.

23. 4:51

    Because really, who has the time and energy to put into these things? There aren't a ton of what I'd call content engineers. Now, in era three, most of these things, you're not paying a human, you're paying Anthropic or OpenAI or whoever, right?

24. 5:05

    You can create videos with Claude. You can create documentation with Claude. You can design websites with Claude, and you can create motion graphics with Claude. Now, the problem is that none of the-- all of these things are good, right?

25. 5:16

    We'll talk about that later. But if you know what you're doing, if you have an engineering mindset, if you understand the systems, you can create high-quality assets with these systems.

26. 5:24

    And I'm gonna talk about how to do that in the rest of this presentation. So today, code is cheap, and we talk about code as communication. So code is communication.

27. 5:36

    The fastest way to build an asset today is through code. And it's not just to build software, right? It's really to build anything. If I want to prototype a video, a website, slides, um, I mean, really any asset, any creative thing that I can think of, images, video, the fastest way to do that is gonna be through

28. 5:58

    code or code generation. And I was thinking about this presentation. I was thinking about how I was going to create all the assets for this presentation, and I realized that my favorite medium is actually TypeScript.

29. 6:10

    Aside from recording myself talk or writing, every ancillary asset is React or TypeScript. And I just want to take a moment because that is the most insane statement to hear myself say if I was thinking about this two or three years ago, right?

30. 6:26

    I don't even really know [chuckles] how to write that good of TypeScript, you know. My background's in data engineering. I come from Python land. Well, I better learn TypeScript. I better learn React because the best way for me to get these high-fidelity assets is React, TypeScript, CSS, um, and HTML, and that's wild.

31. 6:44

    That's wild to say. So if code is inexpensive, what is the expensive thing? Now, you might think I'm gonna say taste here. I'm not gonna say taste because everybody says taste.

32. 6:53

    Structure is expensive. This is maybe a bit of a contrarian set- statement here because the hard thing is maintaining a very structured code base, maintaining brand guidelines and keeping those guidelines consistent, keeping design tokens in your project, separating even front-end code from back-end code from these design tokens.

33. 7:15

    Merging really clean PRs, which, like, nobody does, right? Tagging PRs, PR descriptions, knowing what's a feature and what's a bug fix, knowing if you reverted a PR. How many organizations do this?

34. 7:25

    I've worked at a number of organizations. None, right? And maintaining accurate internal documentation so that anybody can accomplish anything. Even if you have really good agents, they're not gonna know how to solve these problems if they don't have documentation or skills, right?

35. 7:40

    And so structure often is the difference between AI purple gradient slob, right, and something that looks professional and polished. And I would even go a little bit further and I would say that this is conscientiousness.

36. 7:55

    And the dictionary of definition for conscientiousness is the quality of being meticulous, careful, and guided by a strong sense of moral or professional duty. And so it's less about comp-- like software engineering skill today.

37. 8:09

    It's less about the skill of being able to create these, these assets and more about the meticulousness and care given to making sure that an outcome matches your expectations.

38. 8:23

    And that, you know, increasingly with each model generation is not predicated on being the smartest person in the room or being the s- the person in the room with the most technical skill.

39. 8:34

    So what does AI reward? AI rewards conscientiousness. AI rewards organizational excellence. AI rewards structure. And ultimately, these are the things that go into good AI skills.

40. 8:51

    There's a lot of, like, not very good AI skills out there. Um, and most of them are just generated without any regard for what's in their contents or, or how they're structured.

41. 9:01

    And so all the assets that I showed you at the beginning of this video are a byproduct of design tokens, structured code, um, structured assets, and they get exponentially harder to create when we lack those things.

42. 9:16

    And so code, again, is communication, and we're seeing a shift left movement for content where content is moving to code. And if code, right, is the source of truth, if our code base is the source of truth, we have to have a structured source of truth in order to create content from code.

43. 9:37

    In order to communicate, we need structure and conscientiousness around the way that we create code. And again, this only works with organizational excellence. And so I think what we'll see in twenty twenty-six and the years beyond is that the highest performing, the best communicating teams are the ones that are able to instill discipline and rigor

44. 10:01

    into the process of creating software and then shift their content left towards the code through content engineering. And so twenty twenty-six, I think, was the year of the creative technologist, at least in the DevRel space.

45. 10:18

    This is the term that got thrown around a lot. I think twenty twenty-seven is the year of the content engineer, and I'll close on that because I think what we're gonna see next year are declarative and robust content pipelines capable of producing content walkthroughs, capable of producing documentation, screenshots, product updates.

46. 10:38

    All of the things that were really manual can now be created through code, through React, and ultimately because of AI. Again, I'm Matt with Conductor. Thanks for sticking around for my talk.

47. 10:51

    I'll catch you next time. Peace.