Editorial Guidelines

Please observe the following editorial guidelines when submitting blogs to DEVOPSdigest:

Getting Started

DEVOPSdigest recommends that you send an abstract or outline of your potential blog submission to Pete Goldin, Editor and Publisher of DEVOPSdigest, before you start writing the blog, to ensure it is something we would publish.

The following guidelines apply to non-vendors — such as analysts, consultants, integrators and users — who would like to post a blog on DEVOPSdigest. Non-vendor blogs are posted in the BIZDEVOPS Blog.

Vendor blogs are posted in the Vendor Forum. If you work for or represent a product vendor, and you want to submit a blog to DEVOPSdigest, click here for the Vendor Forum guidelines.

If you are a PR or Communications Manager or Agency, click here for some tips on how to interact with DEVOPSdigest.

If you are submitting a quote for a DEVOPSdigest list, such as our annual DevOps Predictions list, click here for guidelines on APMdigest.

Original Content

All blogs submitted to DEVOPSdigest must be original content that has not been published somewhere else. DEVOPSdigest periodically may request to re-post a blog, if the content is particularly valuable to our readers, but please do not pitch DEVOPSdigest to re-post your blog.

Word Count

Standard word count for a blog is 500-1000 words. This is not a strict rule. Word counts can be longer if the topic warrants more content. If your blog is longer than 1000 words, however, you may want to consider breaking it into multiple parts. Editorial decisions relating to word count are made on a case-by-case basis.

Deadline

DEVOPSdigest does not follow an editorial calendar, and usually does not assign a deadline. We post content as we receive it.

Publication Timeframe

DEVOPSdigest posts 1-3 items of primary content — blog or feature — per week. Consequently, there is often a queue of content waiting to be posted.

DEVOPSdigest content is featured in APMdigest e-mails, which go out twice per month, and the current mailing includes content posted since the last mailing.

Topics

DEVOPSdigest accepts blogs on topics relating to DevOps including:

■ DevOps

■ Development Processes

■ Development Technology

■ Development Automation

■ Agile Development

■ Continuous Development

■ API (Application Program Interface)

■ Development Monitoring and Analytics

■ Application Performance and Quality Testing

If you are unsure whether your topic fits DEVOPSdigest, run your idea by Pete Goldin.

Content Guidelines

Blogs should be objective, vendor-neutral, thought leadership pieces. Topics should be general industry interest to educate and enlighten our readers. Please do not promote your company, products, partners or any vendor — or criticize the competition — in the blog copy or in related graphics submitted with the blog.

Author and Company Profile

If this is your first blog for DEVOPSdigest, send a one paragraph bio of the author and one paragraph profile of the company, along with the blog.

Related Links

On The BIZDEVOPS Blog, non-vendor bloggers are welcome to include links at the end of the blog to link to their home page, or other relevant information such as research or events.

Do not place any hyperlinks in the body copy of the blog linking to your company's web pages or any other promotional pages. Hyperlinks in the body copy should only be to support factual points you are making.

Approval

All blogs will be reviewed by DEVOPSdigest prior to publication. DEVOPSdigest reserves the right to edit any content submitted, and the publication of any blog is at the sole discretion of DEVOPSdigest. Related links included with the blog are also subject to DEVOPSdigest approval.

Reposting Blogs

If you contribute to DEVOPSdigest, you are free to re-post your own blog on your own website, as long as you mention that the blog was posted on DEVOPSdigest, and include a link to our site.

However, we recommend linking to the blog on DEVOPSdigest.com rather than posting the full blog on your site, to highlight the fact that the content was published by an independent third party. Publication of your blog on a respected industry site provides strong thought leadership credibility for the author and company.

The Latest

March 23, 2017

Mature development organizations ensure automated security is woven into their DevOps practice, early, everywhere, and at scale, according to Sonatype's 2017 DevSecOps Community Survey ...

March 21, 2017

When it comes to food, we all know what's considered "good" and what's "bad". We can all understand this simple rule when eating. But for many, when it comes to software development, simple rules and advice from nutritional labels aren't always there for us ...

March 20, 2017

Monitoring and understanding what software is really doing, and maintaining good levels of software quality is increasingly important to software vendors today. Even a minor bug is capable of shutting down whole systems, and there is a real risk that development cycle pressure competes with quality assurance best practices ...

March 16, 2017

More than half (54 percent) of IT professionals surveyed indicate they have no access to self-service infrastructure, according to a new DevOps survey of 2,000 IT industry executives by Quali.This means that more than half of respondents take a ticket-based approach to infrastructure delivery, impacting productivity and increasing time to market ...

March 15, 2017

Driven by the adoption of cloud and modernization of application architectures, DevOps practices are fast gaining ground in companies that are interested in moving fast – with software eating everything - between "write code and throw it across the wall" to creating more pragmatic mechanisms that induce and maintain operational rigor. The intent behind DevOps (and DevSecOps) is quite noble and excellent in theory. Where it breaks down is in practice ...

March 13, 2017

There might be many people across organizations who claim that they’re using a DevOps approach, but often times, the “best practices” they’re using don’t align with DevOps methodologies. They can say what they do is “DevOps”, but what we’ve found is that many are actually not following basic agile methodology principles, and that’s not DevOps ...

March 09, 2017

The velocity and complexity of software delivery continues to increase as businesses adapt to new economic conditions. Optimizing and automating your deployment pipelines will dramatically reduce your lead times and enable you to deliver software faster and with better quality. Here are three more most common areas that generate the longest lead times ...

March 08, 2017

Every enterprise IT organization is unique in that it will have different bottlenecks and constraints in its deployment pipelines. With that being said, there are some common problem areas that typically produce the longest lead times in your software delivery process. Here are the most common areas that generate the longest lead times ...

March 06, 2017

The findings of an independent survey of IT leaders, application developers and database administrators, conducted by IDG Research for Datical, indicate that database administrators are unable to keep up with the pace and frequency of database changes caused by the accelerated pace of application releases, thus creating a bottleneck and delaying digital transformation initiatives. An overwhelming number of databases administrators (91 percent) and application development managers (90 percent) cited database updates as the cause for application release delays ...

March 02, 2017

A "Boost Caboose" is a secondary engine pulled on a trailer for the explicit purpose of increasing the output of the primary engine. In many ways, DevOps is its own form of Boost Caboose for application of agile methodologies within the modern software factory and SDLC/ADLC processes ...

Share this