Calling Them What? And that is the question. If you are marketing to developers, you already know that there is no generic “developer.” Undoubtedly, your tool or service is meant to be wielded by a very specific developer persona. But thanks to DevOps, that persona may be employing multiple tools. So when your persona also identifies as DevOps, what does that mean? Why should you care? To understand this, Developer Media posed a very simple question on CodeProject.com: “Are you a DevOps engineer?” Yes, But... At least one developer responded, “Yes, but I don’t want to be one.” Harrr. [...]

We recently posed the question to the CodeProject.com audience: “How often do you shoot down product tool choices your manager / team lead presents to your team?". From this, we learned that 34.5% of the developers who responded very often, often, or occasionally reject the choices the purchaser has already made. In addition, approximately 30% never have to reject a product from on high because they choose their own tools! However, this first survey did not dig into the reasons why developers had rejected or disliked tool selections made by their manager, team lead, or other leaders in their organization. [...]

Most people agree that developers of all job descriptions have tremendous technical power at their fingertips. However, particularly in large organizations, many software and programming tool developers have been focusing on the purchaser as the customer. More often than not, that is not the developer who will be implementing the tool purchased. The C-suite, project managers, or lead engineers may seem like the best target audience. But what about the developers they will delegate implementation to? How do developers influence tool purchases? To understand this, Developer Media posed a very simple question on CodeProject.com:   “How often do you shoot [...]