Coolblue Behind the Scenes | Niels Abels - Continuous Delivery.

•

0 likes•396 views

This document discusses continuous delivery at Coolblue. It outlines their back office development, focus on creating great software, and approach to continuous delivery. Their continuous delivery approach includes: releasing code as soon as possible after it is merged; taking small, frequent steps; and making it easy to correct mistakes. Key aspects of their approach include heavy testing, code quality practices like reviews, automating processes as much as possible, and monitoring systems. The document emphasizes the importance of great teams over any specific tools.

Software

CONTINUOUS DELIVERY.
At Coolblue.
By Niels Abels

AGENDA.
What’s up doc.
• Back office development.
• Great software.
• Continuous Delivery.

GREAT SOFTWARE.
Just end-user things.
• Helps the user.
• Is software the user can rely on.
• Is easy to learn.
• Should be shiny. Really shiny.
• But how?

• Your text goes here.
POKA-YOKE.
Keep it simple, baka.

THE MANTRAS.
A little bit better every day.
• Make it available to the end users as soon as possible.
• Small steps. Release every time code gets merged.
• Make it easy to correct missteps.

OUR APPROACH.
Coming to non-functional terms.
• Testing, testing, testing.
• Code quality.
• Automate, automate, automate.
• Monitoring.

1. TESTING, TESTING, TESTING.
When you’re in doubt, you didn’t test it.
• Unit-, integration-, regression- and end-to-end testing.
• When you fix a bug, you add the missing test.

2. CODE QUALITY.
Build for today, but don’t get in the way of tomorrow.
• Have a consistent view on quality.
• Code reviews keep code great.
• Use and provide shared code.

3. AUTOMATE, AUTOMATE, AUTOMATE.
Because the best developer is a lazy developer.
• No manual intervention beyond a code review. Ever.
• Aim for coded software, -testing and -infrastructure.
• Self-documents your entire process.

4. MONITORING.
Because log ﬁles are overrated.
• Make your system visible.
• Continuously improve on your monitoring.
• We use Application Insights.

TAKEAWAYS.
What do you need?
• TeamCity
• Octopus
• GitHub
• NCrunch
• Visual Studio
• CodedUI
• PRISM
• NDepend
• Roslyn Analysers
• .NET 4.6
• C# 6
• Code Reviews
• Resharper
• Application Insights

TAKEAWAYS.
What do you really need?
• Great developers, product owners and designers.
• Put your software live ASAP…
• … in an environment that’s forgiving to mistakes.

The document discusses continuous delivery at Coolblue. It outlines their back office development, focus on creating great software, and approach to continuous delivery. Their continuous delivery approach includes: releasing code as soon as possible after it is merged; taking small, frequent steps; and making it easy to correct mistakes. Key aspects of their approach include heavy testing, code quality practices like reviews, automating processes as much as possible, and monitoring systems. The takeaways are that the most important things are having great team members and putting software live quickly while also having a forgiving environment for mistakes.

Coolblue Behind the Scenes | Pat Hermens - On the shoulders of giants.

Coolblue

The document discusses the evolution of Coolblue's legacy system called Vanessa over the past 15 years as the company has grown from processing around 1 order per day to over 12,000 orders per day currently. As Vanessa aged it became more difficult to maintain and adapt to new business needs. Coolblue transitioned Vanessa to a microservices architecture using C# and RabbitMQ for messaging to address challenges around agility, reliability, and integrating new systems. Key parts of the new architecture include using RabbitMQ for background jobs, intra-service communication, and sharing data between new and legacy systems through message triggers.

Coolblue Behind the Scenes | Jeffrey Simons - The UX nerd and you.

Coolblue

This document discusses how designers and engineers can work together effectively. It notes that designers and developers often have different perspectives that can cause conflicts. However, through developing a shared understanding of each other's roles and a shared vision of adding value to the product, these conflicts can be resolved. Specific recommendations include using a common language without jargon, collaborative techniques like pairing, and focusing project work on solving business problems and delivering value to users through user stories.

Agile tour agile development

Tom Klaasen

Tom Klaasen has 10 years of experience developing software using Java/J2EE and more recently Ruby on Rails and iOS. He co-founded 10to1 in 2006 which uses an agile development process with 4 highly skilled passionate developers. They focus on communication through daily deployments and meetings with users, prioritizing developing workable applications over extensive testing or documentation. Their agile approach is influenced by the conventions of Ruby on Rails and aims to be flexible rather than following rigid rules.

PyCon UK 2013 "Python Adventures in Startup Land"

rwillmer

This document discusses using Python for startups and minimum viable products. It explains that startups aim for minimum viable products and continuous change rather than long-term plans. The Lean Startup methodology advocates building products iteratively based on customer feedback and pivoting if needed. Python is well-suited for startups because it allows for fast development and integration with external services commonly used by startups.

Continuous Updating

Robert Reiz

We've being shifting

paulosuzart

This document discusses the evolution of computing technologies over time. It notes that as technologies become outdated or limited, the industry shifts to new approaches. Specifically, it outlines shifts from low-level machine instructions to high-level languages and virtual machines, desktop applications to web applications, and distributed components to web services and service-oriented architectures. The document suggests that cloud computing is the current shift and poses questions about what may come next, such as full utilization of business process management, mobile integration, and more distributed and scalable operating systems and frameworks.

UX Process

harsai kron

The document discusses the importance of adopting a proper UX process for product development rather than rushing into an "instant design", which provides a poor user experience. It states that creating a perfect product, like a specialty coffee, requires following professional processes with precise timing, temperature and steps. The UX process should be gradually adopted over time by showing stakeholders its value and importance through empathy and understanding their objectives.

This document discusses lessons learned from launching a Ruby on Rails application. Some key points include: using Resque for background jobs provides more control than DelayedJob; background jobs can significantly impact database load so it's important to monitor and optimize them; indexes can greatly improve database performance so don't let Rails generate inefficient queries; and serialization can hurt performance so use database relations instead of storing serialized objects. Overall, expect issues and don't get complacent - optimize asynchronously processed tasks and write efficient SQL.

Devops in with the old, in with the new

Jan Collijs

The Big Wave of Indian Startups - Almost Effortless Entrepreneurship Using Ruby

Pradeep Elankumaran

The document discusses Intridea, a web and mobile services company based in Washington DC. It summarizes their products, including Presently an enterprise microblogging platform and Grub.it, a new mobile app for reviewing dishes at restaurants. The majority of the document provides tips for launching a web product fast and cheap, including choosing the right tools like Ruby on Rails, deploying to Heroku, and establishing analytics and feedback systems. It concludes by asking for audience input on challenges of doing startups in India such as finding entrepreneurial talent and lack of mentorship.

How Early DevOps Investment Greased the Wheels of Acquisition

Michael Heijmans

Transforming operations into devOps iteratively

Outlyer

(Best) Practices for the Solo Developer

Michael Eaton

You are the only developer in your company. Maybe you’re an independent consultant. Maybe you work from home, maybe not. Any way it goes, being the lone developer can be tough. Whether you work in a cube or the comfort of your home office or the local coffee shop, there are many challenges facing the solo developer. Project management, estimation, testing and even writing code all change when you work alone. In this session, I will discuss many of the lessons learned and practices I’ve developed working almost exclusively as a single developer for the past ten years.

Seven Jobs You Should Be Running #sqlsat126

Mike Hillwig

This document discusses 7 SQL Agent jobs that should be running to monitor a SQL Server environment. It provides background on the presenter, Mike Hillwig, and introduces the topic of using SQL Agent to automate monitoring processes. Example monitoring jobs discussed include checking for auto shrink being enabled, verifying backups are running successfully, and alerting on failed SQL Agent jobs. The presentation aims to provide both introductory information on SQL Agent and specific monitoring jobs and scripts that can be implemented.

Api Days Berlin - Continuous Updating

Robert Reiz

The document discusses the importance of continuous updating of software libraries and dependencies to ensure applications have the latest bug fixes and security updates. It notes that with agile development, the software development lifecycle has accelerated, but dependencies are still often overlooked. Left unmanaged, outdated dependencies can introduce security vulnerabilities and breakages over time. The document advocates using a tool like VersionEye to automatically detect outdated libraries, track used licenses, and ensure continuous integration of updates through automated migration paths. This prevents issues and saves developers time and money from manual updating processes.

The Five Stages of Chef Grief: My First 6 months with Chef, and Getting Aroun...

DevOpsDays Austin 2014

Chef can be difficult to learn at first and may cause frustration as there is a learning curve. It is important to start small with basic cookbooks, follow tutorials, and ask questions. Over time, as experience with Chef grows, so does understanding of its capabilities. Chef is constantly evolving through an active community, and what seems challenging now will become clearer. While the learning process may involve stages of denial, anger and feeling overwhelmed, acceptance that difficulties are normal helps to appreciate Chef's power for automating infrastructure.

The new challenge of Open - OSCAL 2015

Christian Heilmann

This document discusses the benefits and challenges of open source work. It notes that working openly allows sharing workloads and creating enduring projects, but also means constant feedback and adherence to best practices. While open source powers the web, companies prioritize marketing and revenue over technology. True openness requires giving work away freely and supporting the community. The document calls for celebrating small steps toward openness and focusing on education rather than confrontation.

Choosing Javascript Libraries to Adopt for Development

Edward Apostol

"Sorting out the JS Mess" was the title of my sample presentation I led at @Red Academy, talking about how the history of the development workflow with Javascript and how it influences what tools, libraries and steps we take to develop web and mobile apps. I featured a demo using React, and discussed Angular 2, JQuery, Meteor, and other Javascript libraries and frameworks from the context of my development experience.

Build it and they will not come: Being a programmer in 21st century - Nathan ...

Codemotion

In a world of open source, open ideas, and open collaboration, incredible opportunity exists for programmers that know how to grasp it. Participating in open source and the worldwide discussion of ideas can be a powerful way to boost your career, improve your skills, and lead a more fulfilling programming life. Succeeding in this world can be a struggle – the well known phrase "build it and they will come" could not be more false. Success requires you to grow in many new ways. For those willing to push their boundaries, the rewards are worth the effort a hundred times over.

Tac Timetable

guest3980b7

The document outlines the agenda for the Actionscript Conference over two days. Day 1 includes sessions on Adobe Flash Collaboration Services, audio processing in Flash, multi-touch capabilities in Flash Player, developing with Adobe AIR, and sneak previews. Day 2 covers topics such as the ultimate Flash development environment, Papervision 3D, web development with Gaia Framework, model-driven development with ColdFusion and Flash Builder, and using Flash Lite, phone APIs and touch input. The conference provides attendees opportunities to learn about the latest Actionscript and Flash technologies from industry experts.

Why Enterprises Are Embracing the Cloud

Randy Shoup

After being deeply involved in public cloud for the last several years, as both a provider and a consumer, I have been very pleasantly surprised at the rate at which large enterprises are rapidly moving to the cloud. For all the right reasons, even the most regulated and risk-averse of industries -- banking, for example -- are rapidly moving workloads out of their own owned data centers. Public cloud is not just for the "unicorns", but for the "horses" as well. This short vignette, presented at the GOTO Aarhus 2014 conference, tries to explain why this trend will continue and accelerate, and why we should be excited about it.

Makerbot

Kay Gregg

The Six Pitfalls of building a Microservices Architecture (and how to avoid t...

J On The Beach

Thinking of moving to Microservices? Watch out! That quest is full of traps, social traps. If you are not able to handle it, you may be blocked by meetings, frustration, endless challenges that will make you miss the monolith. In this talk, I share my experience and mistakes, so you can avoid them. Creating or migrating to a Microservices architecture might easily become a big mess, not only due to technical challenges but mostly because of human factors: it’s a major change in the software culture of a company. In this talk, I’ll share my past experience as the technical lead of an ambitious Microservices-based product, I’ll go through the parts we struggled with, and give you some advice on how to deal with what I call the Six Pitfalls: The Common Patterns Phobia The Book Club Cult The Never-Decoupled Story The Buzz Words Syndrome The Agile Trap The Conway’s Law Hackers

Lightning talk invest stories - public

Ashley Frieze

Hacker News Meetup April 2014

Dan Quine

Building High Quality Android Applications

Leif Janzik

Random thoughts and dev practices / advices to build a great product

Guillaume POTIER

Wilko Nienhaus - continuous delivery release the right thing, done right, at ...

DevConFu

Want to know how to release software better? Heard about Continuous Delivery before, but didn't know where to start? Continuous Delivery is a strategy for improving the software delivery process, through various development practices and a strong focus on automation. Come and find out what value Continuous Delivery brings to agile development teams and how you can release high quality software more often. There will be a practical demo too, showing some of the tooling and mindset that makes it possible.

How to maintain a perfect product architecture in a non-stop start-up

Adam Kariv

What's hot

Lessons from Branch's launch

aflock

Devops in with the old, in with the new

Jan Collijs

The Big Wave of Indian Startups - Almost Effortless Entrepreneurship Using Ruby

Pradeep Elankumaran

How Early DevOps Investment Greased the Wheels of Acquisition

Michael Heijmans

Transforming operations into devOps iteratively

Outlyer

(Best) Practices for the Solo Developer

Michael Eaton

Seven Jobs You Should Be Running #sqlsat126

Mike Hillwig

Api Days Berlin - Continuous Updating

Robert Reiz

The Five Stages of Chef Grief: My First 6 months with Chef, and Getting Aroun...

DevOpsDays Austin 2014

The new challenge of Open - OSCAL 2015

Christian Heilmann

Choosing Javascript Libraries to Adopt for Development

Edward Apostol

Build it and they will not come: Being a programmer in 21st century - Nathan ...

Codemotion

Tac Timetable

guest3980b7

Why Enterprises Are Embracing the Cloud

Randy Shoup

Makerbot

Kay Gregg

The Six Pitfalls of building a Microservices Architecture (and how to avoid t...

J On The Beach

Lightning talk invest stories - public

Ashley Frieze

What's hot (17)

Lessons from Branch's launch

Devops in with the old, in with the new

The Big Wave of Indian Startups - Almost Effortless Entrepreneurship Using Ruby

How Early DevOps Investment Greased the Wheels of Acquisition

Transforming operations into devOps iteratively

(Best) Practices for the Solo Developer

Seven Jobs You Should Be Running #sqlsat126

Api Days Berlin - Continuous Updating

The Five Stages of Chef Grief: My First 6 months with Chef, and Getting Aroun...

The new challenge of Open - OSCAL 2015

Choosing Javascript Libraries to Adopt for Development

Build it and they will not come: Being a programmer in 21st century - Nathan ...

Tac Timetable

Why Enterprises Are Embracing the Cloud

Makerbot

The Six Pitfalls of building a Microservices Architecture (and how to avoid t...

Lightning talk invest stories - public

Similar to Coolblue Behind the Scenes | Niels Abels - Continuous Delivery.

Hacker News Meetup April 2014

Dan Quine

Building High Quality Android Applications

Leif Janzik

Random thoughts and dev practices / advices to build a great product

Guillaume POTIER

Wilko Nienhaus - continuous delivery release the right thing, done right, at ...

DevConFu

How to maintain a perfect product architecture in a non-stop start-up

Adam Kariv

Agile, DevOps & Test

Qualitest

Continuous everything

TEST Huddle

STAQ Development Manual (Redacted)

Mike Subelsky

This deck represents our current thinking about the best way to build enterprise SaaS software in 2015 - using a variety of techniques from several disciplines. Since I wrote this I have also become very interested in resilience engineering and the notion that web developers are primarily engaged in the construction of socio-technical systems. When I rewrite this I plan to talk about how we should try to minimize mean-time-to-recover (MTTR) instead of mean-time-between-failures (MTBF), and how continuous deployment grows a safety culture around your operations. I redacted most of the examples that illustrate these points because they use sensitive code examples or URLs. If you want to see the rest of slides, join us!

Continuous delivery is more than dev ops

Agile Montréal

Introduction to Agile Software Development - Eric Wu - MBAX6360 New Product D...

Eric Wu

This document discusses agile software development and is presented by Eric Wu, co-founder of Bracket Labs. It outlines some of the key problems with traditional waterfall software development processes, such as unpredictable requirements and costs. It then introduces agile development principles from the Agile Manifesto, including an emphasis on working software, customer collaboration, and responding to change. Finally, it provides an example of an agile process incorporating sprints, demonstrations, retrospectives and stand-up meetings, and notes how agile practices have evolved and expanded beyond just software development over the past 10 years.

Continuous Delivery: releasing Better and Faster at Dashlane

Dashlane

Gartner Infrastructure and Operations Summit Berlin 2015 - DevOps Journey

Kelly Looney

The document discusses the DevOps journey of a large online gaming company with separate sports betting and poker/casino divisions that were merged. It outlines the challenges of integrating different code bases and cultures. Key steps taken include adopting Agile, moving to Git/Jenkins, implementing monitoring with AppDynamics, and moving to containers. Automating testing environments and adopting continuous delivery principles helped improve quality and allow smaller, more frequent changes. Monitoring provided visibility and helped identify issues and refactoring needs. The changes helped bring development and operations teams together.

Igor Stojanovski

The document discusses concepts related to continuous delivery of software projects including continuous integration, continuous delivery, and continuous deployment. It defines these terms and describes prerequisites and best practices for each. Continuous integration involves regularly merging code changes and running automated tests. Continuous delivery means software can be released to production at any time if it passes testing. Continuous deployment automates the entire delivery process including direct deployment to production. The document outlines example tooling and technologies that can be used to enable these practices for open source Java projects, including code repositories, CI servers, artifact repositories, and deployment targets.

Continuous Delivery for Open Source Java projects

Tricode (part of Dept)

Agile Gurgaon 2016 | Thinking Beyond :: Marry Agile and DevOps for Phenomenal...

AgileNetwork

This document discusses marrying Agile and DevOps approaches to get phenomenal results. It begins with an introduction of the author and their experience. It then poses common questions around when to adopt Agile vs DevOps and how they relate. The document outlines differences between traditional and Agile/DevOps mindsets and practices. It provides examples of lessons learned and challenges overcome during one organization's transformation journey. Finally, it discusses steps to get started with a DevOps approach and lists examples of effective DevOps practices.

Agile engineering practices

Mustafa Savaşcı

Enabling your DevOps culture with AWS-webinar

Aaron Walker

In this presentation shows you how the benefits of AWS technologies can be combined with a new approach to Development and Operations. It’s all about delivering new features and functionality faster, without compromising reliability, stability and performance. * Understand the challenges faced by traditional Development and Operations teams * Apply Continuous Integration/Delivery processes and tools to enable change * Appreciate how various AWS technologies can be used to facilitate DevOps

Supersize me: Making Drupal go large

Tom Phethean

Continuous Updating with VersionEye at code.talks 2014

Robert Reiz

These are the slides from the "Continuous Updating with VersionEye" talk at code.talks 2014 in Hamburg. Nowadays modern software development without open source is almost impossible. In average a modern software project has 100 open source components. How do you keep track of these open source dependencies? How do you know that they are still alive? How do you manage the licenses for these dependencies? These are all important questions which get answered in this talk.

Driving application development through behavior driven development

Einar Ingebrigtsen

This document discusses Behavior Driven Development (BDD) and how it can be used to drive application development. It introduces BDD, focusing on behaviors of the system rather than tests. It discusses key aspects of BDD like Gherkin, units, test doubles, writing testable code, frameworks like SpecFlow and recommended reading. The overall message is that BDD changes the way software is developed by shifting the focus to behaviors and improving collaboration.

Similar to Coolblue Behind the Scenes | Niels Abels - Continuous Delivery. (20)

Hacker News Meetup April 2014

Building High Quality Android Applications

Random thoughts and dev practices / advices to build a great product

Wilko Nienhaus - continuous delivery release the right thing, done right, at ...

How to maintain a perfect product architecture in a non-stop start-up

Agile, DevOps & Test

Continuous everything

STAQ Development Manual (Redacted)

Continuous delivery is more than dev ops

Introduction to Agile Software Development - Eric Wu - MBAX6360 New Product D...

Continuous Delivery: releasing Better and Faster at Dashlane

Gartner Infrastructure and Operations Summit Berlin 2015 - DevOps Journey

Continuous Delivery for Open Source Java projects

Agile Gurgaon 2016 | Thinking Beyond :: Marry Agile and DevOps for Phenomenal...

Agile engineering practices

Enabling your DevOps culture with AWS-webinar

Supersize me: Making Drupal go large

Continuous Updating with VersionEye at code.talks 2014

Driving application development through behavior driven development

Recently uploaded

E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies

Quickdice ERP

Unveiling the Advantages of Agile Software Development.pdf

brainerhub1

Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris

Neo4j

ALGIT - Assembly Line for Green IT - Numbers, Data, Facts

Green Software Development

SWEBOK and Education at FUSE Okinawa 2024

Hironori Washizaki

8 Best Automated Android App Testing Tool and Framework in 2024.pdf

kalichargn70th171

Graspan: A Big Data System for Big Code Analysis

Aftab Hussain

We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs. We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations. These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18. - Accepted in ASPLOS ‘17, Xi’an, China. - Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17. - Invited for presentation at SoCal PLS ‘16. - Invited for poster presentation at PLDI SRC ‘16.

Need for Speed: Removing speed bumps from your Symfony projects ⚡️

Łukasz Chruściel

No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception. In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed. We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.

What is Augmented Reality Image Tracking

pavan998932

GraphSummit Paris - The art of the possible with Graph Technology

Neo4j

2024 eCommerceDays Toulouse - Sylius 2.0.pdf

Łukasz Chruściel

Vitthal Shirke Java Microservices Resume.pdf

Vitthal Shirke

Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition

Envertis Software Solutions

Odoo ERP software Odoo ERP software, a leading open-source software for Enterprise Resource Planning (ERP) and business management, has recently launched its latest version, Odoo 17 Community Edition. This update introduces a range of new features and enhancements designed to streamline business operations and support growth. The Odoo Community serves as a cost-free edition within the Odoo suite of ERP systems. Tailored to accommodate the standard needs of business operations, it provides a robust platform suitable for organisations of different sizes and business sectors. Within the Odoo Community Edition, users can access a variety of essential features and services essential for managing day-to-day tasks efficiently. This blog presents a detailed overview of the features available within the Odoo 17 Community edition, and the differences between Odoo 17 community and enterprise editions, aiming to equip you with the necessary information to make an informed decision about its suitability for your business.

KuberTENes Birthday Bash Guadalajara - Introducción a Argo CD

rodomar2

AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App

Google

AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App 👉👉 Click Here To Get More Info 👇👇 https://sumonreview.com/ai-fusion-buddy-review AI Fusion Buddy Review: Key Features ✅Create Stunning AI App Suite Fully Powered By Google's Latest AI technology, Gemini ✅Use Gemini to Build high-converting Converting Sales Video Scripts, ad copies, Trending Articles, blogs, etc.100% unique! ✅Create Ultra-HD graphics with a single keyword or phrase that commands 10x eyeballs! ✅Fully automated AI articles bulk generation! ✅Auto-post or schedule stunning AI content across all your accounts at once—WordPress, Facebook, LinkedIn, Blogger, and more. ✅With one keyword or URL, generate complete websites, landing pages, and more… ✅Automatically create & sell AI content, graphics, websites, landing pages, & all that gets you paid non-stop 24*7. ✅Pre-built High-Converting 100+ website Templates and 2000+ graphic templates logos, banners, and thumbnail images in Trending Niches. ✅Say goodbye to wasting time logging into multiple Chat GPT & AI Apps once & for all! ✅Save over $5000 per year and kick out dependency on third parties completely! ✅Brand New App: Not available anywhere else! ✅ Beginner-friendly! ✅ZERO upfront cost or any extra expenses ✅Risk-Free: 30-Day Money-Back Guarantee! ✅Commercial License included! See My Other Reviews Article: (1) AI Genie Review: https://sumonreview.com/ai-genie-review (2) SocioWave Review: https://sumonreview.com/sociowave-review (3) AI Partner & Profit Review: https://sumonreview.com/ai-partner-profit-review (4) AI Ebook Suite Review: https://sumonreview.com/ai-ebook-suite-review #AIFusionBuddyReview, #AIFusionBuddyFeatures, #AIFusionBuddyPricing, #AIFusionBuddyProsandCons, #AIFusionBuddyTutorial, #AIFusionBuddyUserExperience #AIFusionBuddyforBeginners, #AIFusionBuddyBenefits, #AIFusionBuddyComparison, #AIFusionBuddyInstallation, #AIFusionBuddyRefundPolicy, #AIFusionBuddyDemo, #AIFusionBuddyMaintenanceFees, #AIFusionBuddyNewbieFriendly, #WhatIsAIFusionBuddy?, #HowDoesAIFusionBuddyWorks

UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem

Peter Muessig

openEuler Case Study - The Journey to Supply Chain Security

Shane Coughlan

Using Query Store in Azure PostgreSQL to Understand Query Performance

Grant Fritchey

How to write a program in any programming language

Rakesh Kumar R

socradar-q1-2024-aviation-industry-report.pdf

SOCRadar

SOCRadar's Aviation Industry Q1 Incident Report is out now! The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers. SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.

Recently uploaded (20)

E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian Companies

Unveiling the Advantages of Agile Software Development.pdf

Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris

ALGIT - Assembly Line for Green IT - Numbers, Data, Facts

SWEBOK and Education at FUSE Okinawa 2024

8 Best Automated Android App Testing Tool and Framework in 2024.pdf

Graspan: A Big Data System for Big Code Analysis

Need for Speed: Removing speed bumps from your Symfony projects ⚡️

What is Augmented Reality Image Tracking

GraphSummit Paris - The art of the possible with Graph Technology

2024 eCommerceDays Toulouse - Sylius 2.0.pdf

Vitthal Shirke Java Microservices Resume.pdf

Why Choose Odoo 17 Community & How it differs from Odoo 17 Enterprise Edition

KuberTENes Birthday Bash Guadalajara - Introducción a Argo CD

AI Fusion Buddy Review: Brand New, Groundbreaking Gemini-Powered AI App

UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem

openEuler Case Study - The Journey to Supply Chain Security

Using Query Store in Azure PostgreSQL to Understand Query Performance

How to write a program in any programming language

socradar-q1-2024-aviation-industry-report.pdf

Coolblue Behind the Scenes | Niels Abels - Continuous Delivery.

1. CONTINUOUS DELIVERY. At Coolblue. By Niels Abels

2. • Niels Abels. • ~9 years as a Software Developer at a lot of places. • Now a Lead Developer at Coolblue (~1,5 years). ME.

3. AGENDA. What’s up doc. • Back office development. • Great software. • Continuous Delivery.

4. BACK OFFICE.

5. <<PRODUCTSPECIALIST>> ONCE UPON A TIME.

6. 24.

7. 4.

8. GREAT SOFTWARE. What’s that?

9. GREAT SOFTWARE. Just end-user things. • Helps the user. • Is software the user can rely on. • Is easy to learn. • Should be shiny. Really shiny. • But how?

10. CONTINUOUS DELIVERY. But..whatisit?

11. • Your text goes here. POKA-YOKE. Keep it simple, baka.

12. OUR STACK. Our highway to Production.

13. THE MANTRAS. A little bit better every day. • Make it available to the end users as soon as possible. • Small steps. Release every time code gets merged. • Make it easy to correct missteps.

14. OUR APPROACH. Coming to non-functional terms. • Testing, testing, testing. • Code quality. • Automate, automate, automate. • Monitoring.

15. 1. TESTING, TESTING, TESTING. When you’re in doubt, you didn’t test it. • Unit-, integration-, regression- and end-to-end testing. • When you fix a bug, you add the missing test.

16. 2. CODE QUALITY. Build for today, but don’t get in the way of tomorrow. • Have a consistent view on quality. • Code reviews keep code great. • Use and provide shared code.

17. 3. AUTOMATE, AUTOMATE, AUTOMATE. Because the best developer is a lazy developer. • No manual intervention beyond a code review. Ever. • Aim for coded software, -testing and -infrastructure. • Self-documents your entire process.

18. 4. MONITORING. Because log ﬁles are overrated. • Make your system visible. • Continuously improve on your monitoring. • We use Application Insights.

19. AUTOMATE, AUTOMATE, AUTOMATE.

20. TAKEAWAYS. What do you need? • TeamCity • Octopus • GitHub • NCrunch • Visual Studio • CodedUI • PRISM • NDepend • Roslyn Analysers • .NET 4.6 • C# 6 • Code Reviews • Resharper • Application Insights

21. TAKEAWAYS. What do you really need? • Great developers, product owners and designers. • Put your software live ASAP… • … in an environment that’s forgiving to mistakes.

22. QUESTIONS.

Coolblue Behind the Scenes | Niels Abels - Continuous Delivery.

Recommended

Recommended

More Related Content

What's hot

What's hot (17)

Similar to Coolblue Behind the Scenes | Niels Abels - Continuous Delivery.

Similar to Coolblue Behind the Scenes | Niels Abels - Continuous Delivery. (20)

Recently uploaded

Recently uploaded (20)

Coolblue Behind the Scenes | Niels Abels - Continuous Delivery.