This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
There are a few qualities that differentiate average from high performing softwareengineering organisations. In my experience, the culture is better and the results are better in orgs where engineers and architects obsess over the design of code and architecture. They prefer to work in isolation and just deliver.
For instance, it is in the CISO’s best interests to help set up the compliance and security tests to ensure the software being rolled out is as secure as possible, especially if you want continuousdelivery. And this does not just include development teams; the Paved Road weaves through multiple departments. Conclusion.
Lean was introduced to software a couple of decades ago. The Nature of Software “Do not go where the path may lead, go instead where there is no path and leave a trail” -- Ralph Waldo Emerson It’s May 27, 1997. I show that these models derive from opposing assumptions about the nature of the software-debugging task.
In many organizations, automated testing lags behind and becomes a bottleneck for successful continuousdelivery. Either tests do not provide enough confidence or companies take a very traditional approach, resulting in releases either introducing substantial risks or becoming costly.
In companies with many teams and many millions of lines of code, including a lot of legacy, there are endless things that can be improved in the product, software, and organization. Choosing where to focus is a balancing act: delivering new products, fixing legacy software, and improving engineeringculture.
Functional monitoring is a crucial part of any successful ContinuousDelivery implementation. We often see development teams having difficulty striking the right balance between different kinds of monitoring, focusing on observability primarily in terms of technical metrics like error rate.
Software testing, especially in large scale projects, is a time intensive process. Test suites may be computationally expensive, compete with each other for available hardware, or simply be so large as to cause considerable delay until their results are available.
I picked some of my favorite books at my company, Semaphore — books that have profoundly influenced the company’s engineeringculture. This list contains a mixture of classic, timeless texts and a fair share of modern game-changing publications, aimed at senior engineers and devs.
Delivery?—?A A fully-managed continuous-delivery system of pipelines, continuous integration jobs, and end to end tests. Each subsystem addresses a different concern of a service and can be deployed independently through a purpose-built managed ContinuousDelivery process. Productivity?—?Local
To me, this story is what DDD is really about: developing the design mindset of a modeller to drive product innovation and enable continuousdelivery of value, involving frequent collaboration with domain experts. Our project was to build software to track and support this whole process. fixing somebody else’s mess.
Modern software systems are complex, with services distributed across data centers, in many zones, all around the world. Managing that interaction with the cloud is part of what cloud engineering is all about. To deliver applications cleanly, you need to manage infrastructure with pipelines just like you manage continuousdelivery.
finding good softwareengineers takes so long and requires so much effort… but it doesn’t have to. If you like the ideas in the post, then why not come and join me at Navico and help us to build a highly-innovative engineeringculture and a brilliant place to work. Hiring is so hard?—?finding
At the November Test in Production Meetup in San Francisco, LaunchDarkly’s Yoz Grahame (a Developer Advocate) moderated a panel discussion featuring Larry Lancaster, Founder and CTO at Zebrium, and Ramin Khatibi, a Site Reliability Engineer (SRE) and infrastructure consultant. I guess is what I would say. That’s great. Larry: Yes.
Conclusion When building a platform be aware that you can not change how an organization works and software is developed just by bringing in new tools and technical capabilities. But this vastness of opportunities in itself can present a challenge. Build a pl atform b ased on an actual need. Carefully consider these factors before proceeding.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content