---
title: "Comment by Ian Young on \"Hi, I'm Nader Dabit, Developer Relations engineer working in web3 with Edge & Node & Graph Protocol. Ask me anything!\" | Hashnode"
description: "Nader, I&#39;ve been a big fan of your work for some time, and have benefited from a lot of your written and video content. How do you organise yourself to both"
url: "https://hashnode.com/posts/ama/61aa2f0a17b6204eb99dcb25/comment/61ae47ab9dc5a836391bb1df"
---

[Discussion](https://hashnode.com/posts/ama/61aa2f0a17b6204eb99dcb25)

Comment [Hi, I'm Nader Dabit, Developer Relations engineer working in web3 with Edge & Node & Graph Protocol. Ask me anything!](https://hashnode.com/posts/ama/61aa2f0a17b6204eb99dcb25)

[Ian Young](https://hashnode.com/@ianyoung)

[Dec 6, 2021](https://hashnode.com/posts/ama/61aa2f0a17b6204eb99dcb25/comment/61ae47ab9dc5a836391bb1df)

Nader,

I've been a big fan of your work for some time, and have benefited from a lot of your written and video content. How do you organise yourself to both learn and produce so much content on a regular basis? Do you set a strict schedule for yourself? Do have any productivity tips that you find helpful?

Was the DevRel role at AWS something you sought out or did it come about because of the amount of content you were already producing? Was it something you had previously considered moving into?

[Nader Dabit](https://hashnode.com/@dabit3)

[Dec 6, 2021](https://hashnode.com/posts/ama/61aa2f0a17b6204eb99dcb25/comment/61ae47ab9dc5a836391bb1df#reply-61ae77e49dc5a836391bb67e)

The biggest productivity hack that has worked for me is to have at least 1 moderately large deliverable per week, and ship it! This deliverable could be a blog post, reference architecture, workshop material, conference talk, or really anything.

Over the course of a year, if you ship something every week, you will have a large body of work. What you can then do is remix and repurposing some of that material - a blog post becomes a video, a video becomes a conference talk, a conference talk becomes a tweet thread, and so on and so on.

The DevRel opportunity at AWS came from someone on that team reaching out to me with the job offer, after having worked in Seattle with one of the teams at AWS teaching a React Native workshop. I had not really thought of moving into DevRel until then, though the idea of DevRel always was cool to me, and I was essentially doing it for my own company at the time (React Native Training).
