I’ve been considering pivoting my career toward developer advocacy. I’m a decent developer with great customer service skills, and I can see myself doing well in such a position. In order to do that, I need to have a stronger idea of what I believe the role will entail. When I’ve established that, I’ll know which jobs to apply for.
In this post, I am attempting to answer two questions: what do developers actually do, and how can an advocate help them do that?
What is the point of a developer?
In previous blog posts I have discussed the role of Knowledge Management in an organization. That role is the consistent application of the organization’s ideology. Put it another way, the organization has a certain way it needs to run, and to think about things, and Knowledge Management helps with that process.
So, what is the role of the developer? When we start talking about developers, we quickly move from a very general business context to a much more specific one. Software can do many things, but in a lot of ways a developer is a developer. The offhand answer is, of course, that a developer develops software. This