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
Typically, teams split the code of various app components into subfolders and use Git workflow for new features or bug fixes. This approach is natural for most applications or systems developed using a monolithic architecture. System knowledge is spread across multiple repos maintained by different teams. Benefits of monorepos.
And it’s how we decided to teach secure coding to our entire engineering team at CircleCI. Who knew security training wasn’t just 90’s clip art with the bad guys wearing ski masks while typing?” During an exercise at the event, he discovered a vulnerability that was wide open on his service. How to teach security.
This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. Visit the Second Edition home page for information about the open development process, additional excerpts, and more. Whole Team. The Hole Team. Modern software development takes a lot of skills.
This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. Visit the Second Edition home page for information about the open development process, additional excerpts, and more. Developers. Collective code ownership means the team shares responsibility for their code.
The most recent Unit 42 Cloud Threat Report contains the high-level results of a red teamexercise performed against a SaaS customer’s continuousintegration and continuousdevelopment (CI/CD) pipeline. Compromising the CI/CD Pipeline.
Recently I was giving a talk to a group of wonderful people about the importance of headless development in general and for Sitecore in particular, compared to the old way of doing things with ASPNET MVC. Evolution of Web Development. In the early days of the web, web development was focused on creating websites using static HTML.
This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. Visit the Second Edition home page for information about the open development process, additional excerpts, and more. If you use continuousintegration, your team has removed most of the risk of releasing.
The human part is really important for developers. We need our personal life as everybody else and satisfy our human needs; that, in order to be awake and ready to produce code and help the team. What do people need to be good developers? Software development is more valuable when it earns money sooner and spends it later.
Small, collaborative teams iterating quickly on modular bits of code, leveraging the latest in automation tooling, deploying to production perhaps several times a day? True, the road to continuousintegration and continuous delivery (CI/CD), DevOps’ core processes, can be a long one. The Road to CD for Watchful Bank.
” “Exercise multiple times a week!” However, these are not practices designed solely to make one suffer: they are encouragements to help one develop and maintain good hygiene. How will the project team know when a new version has been released for any of the project’s software dependencies? and grown to loath.
Moreover, he explained how Continuous Verification can help software engineers avoid such pitfalls. And I am a developer advocate for LaunchDarkly. It’s sometimes referred to as the bad apples management principle. Watch Casey’s full talk. FULL TRANSCRIPT: Yoz Grahame: April the 30th 2020. My name is Yoz Grahame.
They go on to report that 70% of the cases of these 7 chronic illnesses are preventable through lifestyle change: diet, exercise, avoiding cigarettes and what not. So it is with IT projects: an extremely efficient IT project will still fail if it is blindsided because a market doesn’t materialise for the solution being developed.
This camp values practices such as test driven design, continuousintegration, co-located and cross-functional teams, short development iterations, and frequent releases of software. How can anybody expect that deterministic project planning will keep pace with changes and discoveries made during development?
Kent Beck concluded , Measure developer productivity? He says a measurement based approach generates relatively weak improvements and significant distortion of incentives. I walked them through an exercise right there on the CEOs dining room table. But its still an interesting thought exercise. Not possible. Lets dig in.
Secure continuousintegration and continuous delivery (CI/CD) pipelines with, for example, strong IAM, log audits and secrets management. and New Zealand, comes about a month after these same agencies published a joint advisory about Volt Typhoon aimed at IT and OT security teams. Australia, Canada, the U.K.
This is a pre-release excerpt of The Art of Agile Development, Second Edition , to be published by O’Reilly in 2021. Visit the Second Edition home page for information about the open development process, additional excerpts, and more. Whole Team. Agile teams understand failures are inevitable. Second Edition cover.
In her forthcoming book Platform Engineering , Camille Fournier notes that platform engineering has been used to mean anything from an ops team wiki to dashboards to APIs to container orchestration with Kubernetes. What’s needed is a new set of abstractions that allows both developers and operations staff to move to a higher level.
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