Developers and engineering teams are under increasing pressure to release higher quality software faster. Continuous testing has proven to be central to these efforts as it helps eliminate bottlenecks and ensures that automated testing is a constant throughout the development process, not an exercise relegated to the "last mile." The value of automated testing is more evident than ever before, with nearly half the respondents reporting that management is fully committed to automated testing and with plans to increase spending, according to the recent Sauce Labs Testing Trends for 2018 report ...
The DEVOPSdigest Vendor Forum was established to give vendors of DevOps-related technologies an opportunity to share their views with the IT community in an objective venue. All commentary in Vendor Forum blogs is intended to be objective, vendor-neutral and non-promotional content to educate and enlighten our readers.
All vendors in DevOps-related market spaces are welcome to blog on the Vendor Forum at no cost. To request a blogging account on the Vendor Forum, contact Pete Goldin, Editor and Publisher of DEVOPSdigest.
The following guidelines apply to software vendors who would like to post a blog on DEVOPSdigest. Non-vendor blogs are posted in the BIZDEVOPS Blog. If you work for or represent a company or organization that is not considered a product vendor by DEVOPSdigest, and you want to submit a blog, click here for the Editorial Guidelines.
Blogs from APMdigest sponsors are also posted in the Vendor Forum, but sponsors gain certain benefits when blogging. If you work for or represent a sponsor of APMdigest, click here for the Sponsor Blog Guidelines
Signing Up for a Vendor Forum Blogging Account
■ A request for a blogging account on the Vendor Forum must come directly from the individual whose name will be on the blogs, from that individual's corporate email address.
■ Only one representative from each vendor will be allowed to maintain a blogging account for the Vendor Forum at any particular time, if that vendor does not sponsor DEVOPSdigest. Once a company's blogger is established, that same byline must be used for all future blogs from that company. The only time the byline can be changed is if the blogger is no longer with the company; the blogger has moved to a different part of the company and no longer has any involvement with DevOps; or the blogger is no longer blogging and has not posted a blog for a long time. To change the blogger for your company, contact Pete Goldin, Editor and Publisher of DEVOPSdigest.
■ DEVOPSdigest sponsors are allowed multiple blogging accounts on the Vendor Forum. This sponsor benefit is especially helpful for companies with multiple thought leaders in the industry who would like to claim authorship for their own blogs. Click here to find out how you can sponsor DEVOPSdigest.
■ If a blogger leaves a company, moves to a new company, and continues to blog, all blogs posted by that blogger – past and present – will reference the new company. References to the previous company will be removed from the previous blogs. This would only happen if the blogger remains in the DevOps industry or a related market.
Rules for Blogging on the Vendor Forum
Please observe the following rules when blogging on the Vendor Forum:
■ Do not promote your own company, products or partners in blogs on the Vendor Forum. Topics should be general industry interest. Copy and graphics should be non-promotional and vendor-neutral.
■ One reference to your company in the blog copy is permitted when you are discussing a survey or report conducted or commissioned by your company. A reference to your company's or partner's product is never permitted in the blog copy.
■ If your blog is about a study or survey conducted or commissioned by your company, focus on the results of the survey/study, not why and how the survey/study was conducted.
■ Do not use your product names or phrases that refer to your specific product or service in a blog. Even if your company is trying to turn the phrase into an industry term, if only your company uses this term and it basically refers to your product or service, do not include the phrase in a blog.
■ A reference to open source projects is sometimes permitted, as long as the reference is to the open source project or technology itself, and not the company that founded or owns the project. DEVOPSdigest will make a determination on a case by case basis.
■ Do not criticize a company, brand or product in any blogs on the Vendor Forum.
■ Companies that do not sponsor DEVOPSdigest can only include a link to their company home page at the end of the blog – no product pages or any other pages. Even if the product has its own URL separate from the company page, this cannot be included in place of the company home page. The home page link will always be included in the "Related Links" section at the end of the blog, and cannot be substituted with a hyperlink in a marketing message.
■ Only sponsors of DEVOPSdigest can include additional links at the end of the blog. Click here to find out how you can sponsor DEVOPSdigest.
■ DEVOPSdigest removes old outdated links, but only updates outdated links for current sponsors of the site.
■ Do not place any hyperlinks in the body copy of a blog linking to your company's or any other vendor's web pages or other promotional pages. Hyperlinks in the body copy should only be to support factual points you are making. Hyperlinks in the body copy should only be to support factual points you are making. These hyperlinks can link to a supporting report or article as long as the content is not on your website or your partner's website, is not sponsored or commissioned by your company or partner, and does not promote your company or your partner company in any way. Inclusion of any hyperlinks is at the sole discretion of DEVOPSdigest.
■ Try to keep blogs between 500-1000 words. This is more of a guideline than a rule. You can include more content if you wish, but DEVOPSdigest recommends posting shorter blogs more often. If you have written a 1000+ word blog, consider breaking it into two or more blogs. You could call them Part One and Part Two, if you like. If a blog is lengthy, DEVOPSdigest may choose to post it in multiple parts.
■ 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. Vendor Forum blog posts are edited by DEVOPSdigest for spelling, basic grammar and punctuation. Vendor Forum blogs are also edited to ensure they meet DEVOPSdigest guidelines.
■ Blogs do not have to follow AP style. They can be casual in style. However, DEVOPSdigest expects blogs to be written to meet basic grammar standards. If a blog does not meet these standards, this can significantly delay posting of the blog. Blogs that are well-written and ready for publishing will be posted first.
■ A Vendor Forum blogger can either log into the DEVOPSdigest system to post their own blogs, or send copy to the editor, who will post the blog under the blogger's name. Once the blogger saves a blog in the system, it does not automatically publish. The system notifies the editor, who will review and publish.
■ The date the blog is actually published will be decided by the editor. DEVOPSdigest may provide you with an estimated date the blog will be posted, but that date cannot be guaranteed, as unforeseen priorities may push the posting date back. DEVOPSdigest sponsors have priority when blogs are posted.
■ Do not save an unfinished blog in the system. The Vendor Forum blogging system does not enable bloggers to go back into a blog and edit it later. Once a blog is saved in the system, it is considered ready to be published, assuming it meets DEVOPSdigest guidelines. So only save blogs in the system when they are ready to be published.
■ If a blogger posts their own blog, and wants to include a graphic with the blog, the graphic must be added by the editor.
■ All Vendor Forum blogs 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 re-post your blog on DEVOPSdigest, or pitch DEVOPSdigest to re-post your blog.
■ You can re-post your blogs from the Vendor Forum on your own blogs or websites, 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 such as DEVOPSdigest provides strong thought leadership credibility for the author and company.
■ Please note that these guidelines are updated periodically to ensure continued alignment with DEVOPSdigest's mission.
Topics for the Vendor Forum
DEVOPSdigest accepts Vendor Forum blogs on topics relating to DevOps, including:
■ 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.
As development speed has become a competitive advantage, the DevOps team has sought to enable continuous integration and continuous delivery (CI/CD). For the CI/CD process to be successful, it must be fast and efficient. Any potential roadblocks that delay any part of the process increase cycle times and slow down delivery ...
The top barriers to DevOps adoption involve stagnant organizational cultures; managing the jumble of legacy processes, IT infrastructure and newly created cloud environments; and growing software complexity that impacts application modernization initiatives ...
This is the third in a series of three blogs directed at recent EMA research on the digital war room. In this blog, we'll look at three areas that have emerged in a spotlight in and of themselves — as signs of changing times — let alone as they may impact digital war room decision making. They are the growing focus on development and agile/DevOps; the impacts of cloud; and the growing need for security and operations (SecOps) to team more effectively ...
Only 52 percent of developers using commercial or open source components in their applications update those components when a new security vulnerability is announced, according to new research conducted by Vanson Bourne for CA Veracode, part of CA Technologies. This highlights organizations' lack of security awareness and puts organizations at risk of a breach ...
For a few years now, it has seemed like agile developers and DevOps teams haven't been giving testing its proper due. One could almost picture them thinking, "So what if there's a bug, design flaw or performance issue. We'll fix it in the new version next week." Of course, this line of thinking has turned out to be a big mistake ...
Government IT professionals surveyed, as part of F5 Networks' State of Application Delivery report, made it clear they are heavily focused on building the foundation necessary for application-driven digital transformation. Around the world, government organizations are shifting towards digital government, and with that we see government organizations embracing the cloud, adopting automation and orchestration, and adjusting security strategies ...
The digital war room — physical, virtual or hybrid — is not in retreat but in fact is growing in scope to include greater participation from development and security. It's also becoming more proactive, with on average more than 30% of "major incidents" before they impacted business service performance. In this blog I'm providing a few additional highlights from the insights we got on digital war room organization and processes ...
Many development organizations rely on DevOps, Agile and Continuous Integration/Continuous Delivery (CI/CD) practices and tools to speed up application delivery. However, shorter release cycles and faster application development also mean more frequent database schema and logic changes. Though the application release process has been fast-tracked through modernization and automation, the database deployment process has been forsaken ...