Newsletter Subject

Improve Your Software Quality and Speed of Delivery. Learn How at InfoQ Live on July 20th.

From

infoq.com

Email Address

industry-notices@mailer.infoq.com

Sent On

Mon, Jun 14, 2021 10:38 AM

Email Preheader Text

Virtual Event on July 20 How can modern DevOps practices accelerate your software delivery without t

[InfoQ Live Logo]( Virtual Event on July 20 [View in browser]( How can modern DevOps practices accelerate your software delivery without the quality issues? Every development team needs to improve the speed of software delivery to meet business needs. But traditional approaches tend to impact quality, introduce bugs and technical debt, creating more work for software engineering teams. Learn how Automation, Continuous Testing, and Supply Management Techniques can improve Software Quality and speed of delivery. Get valuable insights from [world-class domain experts]( at [InfoQ Live]( on July 20th. Register and get a gift pass you can share with someone on your team or a friend. You’ll also get exclusive access to all talks on-demand after the event so you can revisit any of the sessions or watch any of the talks you missed. Tickets for InfoQ Live are only $19.95. [Book your spot!]( *We are donating 100% of net revenue tickets (minus taxes, credit card fees, and processing fees) for this event to organizations working towards diversity, equity, and inclusion in the technology industry. “The topics and the way they are presented by people with current experience really improves my visibility in the field. The answers from the presenters during the Q&A reveal details that otherwise will be learned the hard way by my own mistakes.” Ognyan Dimitrov, Former InfoQ Live Attendee Turn advice from world-class software professionals into immediate action items you and your team can implement. InfoQ Live Session Spotlight: [Piranha: Reducing Feature Flag Debt @Uber]( by Murali Krishna Ramanathan, Staff Software Engineer @Uber Feature flags are commonly used in the software development process as they provide flexibility w.r.t gradual rollout of features, enable A/B testing and provide the ability to toggle features on production instances. An often overlooked part of this development model is the introduction of tech debt due to stale feature flags. The presence of code due to stale flags can adversely affect application reliability and increase software development costs. At Uber, reducing this debt without imposing significant additional overheads on the developers necessitated the design of novel tools and automated workflows. “In this talk, I will describe my experiences with building and deploying Piranha, an automated code refactoring tool to delete code corresponding to stale feature flags. The Piranha workflow has been used continuously at Uber since early 2018 to help delete more than 4K stale flags (> 200KLoC) across Java, ObjectiveC, and Swift code. It has also inspired open source contributions in the form of extensions to JavaScript and Go.” [Murali Krishna Ramanathan] Murali Krishna Ramanathan Staff Software Engineer @Uber [Software Supply Chains for DevOps]( by Aysylu Greenberg, Tech Lead of GCP Container Analysis @Google Several recent high-profile security incidents were due to compromised software supply chains. Software Supply Chain is a collective term used to describe the stages of software lifecycle from source to deployment through CI/CD pipelines, and all the static and dynamic analyses in between. In the world of microservices and cloud computing, trust in your company’s supply chain is critical, as most of the tooling and dependencies are from open source and vendor projects. When the code hits production, it’s essential to have enough observability to detect and investigate the problem and get to the root cause and mitigation as quickly as possible. With software supply chain attacks, not only is the newly deployed code under suspicion, but also all the tooling used to produce it becomes a potential attack vector, so an efficient and effective way to verify the integrity of the supply chain is paramount. “This talk will discuss what information needs to be collected to allow DevOps to inspect and verify the integrity of the supply chain, the challenges of having the right level of detail to reduce mean-time-to-detection and mean-time-to-understanding, some of the existing solutions and open problems in this space." [Aysylu Greenberg] Aysylu Greenberg Tech Lead of GCP Container Analysis @Google Co-located events: InfoQ Roundtables (sponsored) Ask your own questions in these live panel discussions and accelerate your learning. [Dealing with Technical Debt in 2021]( [Technical debt continues to be a burden on development teams. Recent studies have found that developers can spend upwards of 23% of their time dealing with technical debt. The impact to developer morale and organizational flow from technical debt can be overwhelming. Making space to pay down the debt can be a challenge as weighing the value of the debt versus other business priorities is not straightforward. Join this InfoQ panel to hear from different industry leaders as they share how they identify technical debt, how they make room to invest in paying debt down, and how they approach work to minimize future debt.]( A roundtable sponsored by:   [The Journey to Continuous Testing in DevOps]( [Continuous testing focuses on automated testing as often as possible within all stages of the life cycle. With the pace of change in software development cycles, testing needs to be thorough and reliable. However, teams face challenges implementing effective test automation to truly enable DevOps. In this InfoQ panel, hear from industry leaders as they discuss their journeys to integrating quality into development, including the obstacles they faced, how they managed the change, and their plans for integrating testing deeper into development.]( A roundtable sponsored by: Get your complimentary pass for the InfoQ Roundtables on July 20th [Register for the Roundtables]( Sponsors [launchdarkly]( [Mabl](   Follow InfoQ on: [Twitter]( [Facebook]( [Youtube]( [LinkedIn]( You have received this email because you opted-in to the "InfoQ Industry Email Notices" box when you registered to InfoQ.com, where we send infrequent notices on behalf of our partners, user groups, conferences, etc. To unsubscribe to the InfoQ Industry Email Notices, please click the following link: [Unsubscribe]( - - - C4Media Inc. (InfoQ.com), 2275 Lake Shore Boulevard West, Suite #325, Toronto, Ontario, Canada, M8V 3Y3

Marketing emails from infoq.com

View More
Sent On

16/10/2024

Sent On

10/10/2024

Sent On

03/10/2024

Sent On

02/10/2024

Sent On

01/10/2024

Sent On

27/09/2024

Email Content Statistics

Subscribe Now

Subject Line Length

Data shows that subject lines with 6 to 10 words generated 21 percent higher open rate.

Subscribe Now

Average in this category

Subscribe Now

Number of Words

The more words in the content, the more time the user will need to spend reading. Get straight to the point with catchy short phrases and interesting photos and graphics.

Subscribe Now

Average in this category

Subscribe Now

Number of Images

More images or large images might cause the email to load slower. Aim for a balance of words and images.

Subscribe Now

Average in this category

Subscribe Now

Time to Read

Longer reading time requires more attention and patience from users. Aim for short phrases and catchy keywords.

Subscribe Now

Average in this category

Subscribe Now

Predicted open rate

Subscribe Now

Spam Score

Spam score is determined by a large number of checks performed on the content of the email. For the best delivery results, it is advised to lower your spam score as much as possible.

Subscribe Now

Flesch reading score

Flesch reading score measures how complex a text is. The lower the score, the more difficult the text is to read. The Flesch readability score uses the average length of your sentences (measured by the number of words) and the average number of syllables per word in an equation to calculate the reading ease. Text with a very high Flesch reading ease score (about 100) is straightforward and easy to read, with short sentences and no words of more than two syllables. Usually, a reading ease score of 60-70 is considered acceptable/normal for web copy.

Subscribe Now

Technologies

What powers this email? Every email we receive is parsed to determine the sending ESP and any additional email technologies used.

Subscribe Now

Email Size (not include images)

Font Used

No. Font Name
Subscribe Now

Copyright © 2019–2025 SimilarMail.