# Work With Your Own Company ![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article3.5c705a01b476.png) URL:: https://developer-advocacy.com/working-with-your-company Author:: developer-advocacy.com ## Highlights > Prejudiced developers are amazingly proud of being the delivering part of the company and consider anyone who does not code superfluous. I am sure you met these people and heard statements like “I don't know why we need designers, when we use a framework!”. It is somewhat ironic that the people whose standing in the company you try to improve are the ones that are likely to be opposed to your role. ([View Highlight](https://read.readwise.io/read/01fj37c0df2f4zg4tbg1a6a7dc)) > As stated in detail beforehand your role as a developer advocate means that you are in between classic outreach departments like PR and marketing and developers. The danger there is that these departments could see you as competition. ([View Highlight](https://read.readwise.io/read/01fj37gtr6gw6xe2a3bysq5ek6)) > **Make the company aware of the communication channels** to the outside world. ([View Highlight](https://read.readwise.io/read/01fj37q7bege5m399hjkrq30ta)) > **Share great responses from the outside world** - send out for example a newsletter of “happy social quotes” with tweets and blog posts about how a certain event or product launch was received in the developer world. ([View Highlight](https://read.readwise.io/read/01fj37r613t2cbp0xppqbc8bkb)) > As a developer advocate, you will have the hand on the pulse of technology. Not everybody has the time to keep up the same way - actually hardly anybody has. That's why an interesting part of your job is to communicate great technology finds with your company. > If you find great tools that make everybody's life easier, share them with the company ([View Highlight](https://read.readwise.io/read/01fj37rh8zekj9am90kftaqs1g)) > The big mistake there is to use your own, personal channels (blog, Twitter account, YouTube channel, Facebook page and so on) for everything ([View Highlight](https://read.readwise.io/read/01fj37w75wmkyya5mf1c8s6m44)) > **You cause a disconnect** – your channels are not where the product is built and maintained. What happens when the technology changes? Keeping the information close to the subject matter and maintained by the people who work on the product ensures that things stay up-to-date without your intervention. ([View Highlight](https://read.readwise.io/read/01fj37wzpxpyf3b6y8bav991yv)) > What you publish on your own channels should whet the appetite of your readers to go to the official place and learn more. ([View Highlight](https://read.readwise.io/read/01fj37xtycp0dqene039wxep4n)) --- Title: Work With Your Own Company Author: developer-advocacy.com Tags: readwise, articles date: 2024-01-30 --- # Work With Your Own Company ![rw-book-cover](https://readwise-assets.s3.amazonaws.com/static/images/article3.5c705a01b476.png) URL:: https://developer-advocacy.com/working-with-your-company Author:: developer-advocacy.com ## AI-Generated Summary None ## Highlights > Prejudiced developers are amazingly proud of being the delivering part of the company and consider anyone who does not code superfluous. I am sure you met these people and heard statements like “I don't know why we need designers, when we use a framework!”. It is somewhat ironic that the people whose standing in the company you try to improve are the ones that are likely to be opposed to your role. ([View Highlight](https://read.readwise.io/read/01fj37c0df2f4zg4tbg1a6a7dc)) > As stated in detail beforehand your role as a developer advocate means that you are in between classic outreach departments like PR and marketing and developers. The danger there is that these departments could see you as competition. ([View Highlight](https://read.readwise.io/read/01fj37gtr6gw6xe2a3bysq5ek6)) > **Make the company aware of the communication channels** to the outside world. ([View Highlight](https://read.readwise.io/read/01fj37q7bege5m399hjkrq30ta)) > **Share great responses from the outside world** - send out for example a newsletter of “happy social quotes” with tweets and blog posts about how a certain event or product launch was received in the developer world. ([View Highlight](https://read.readwise.io/read/01fj37r613t2cbp0xppqbc8bkb)) > As a developer advocate, you will have the hand on the pulse of technology. Not everybody has the time to keep up the same way - actually hardly anybody has. That's why an interesting part of your job is to communicate great technology finds with your company. > If you find great tools that make everybody's life easier, share them with the company ([View Highlight](https://read.readwise.io/read/01fj37rh8zekj9am90kftaqs1g)) > The big mistake there is to use your own, personal channels (blog, Twitter account, YouTube channel, Facebook page and so on) for everything ([View Highlight](https://read.readwise.io/read/01fj37w75wmkyya5mf1c8s6m44)) > **You cause a disconnect** – your channels are not where the product is built and maintained. What happens when the technology changes? Keeping the information close to the subject matter and maintained by the people who work on the product ensures that things stay up-to-date without your intervention. ([View Highlight](https://read.readwise.io/read/01fj37wzpxpyf3b6y8bav991yv)) > What you publish on your own channels should whet the appetite of your readers to go to the official place and learn more. ([View Highlight](https://read.readwise.io/read/01fj37xtycp0dqene039wxep4n))