Jekyll2026-04-10T08:59:45+00:00https://www.devopsdays.dk/feed.xmlDevOpsDaysThe Danish Chapter of the DevOpsDays community conference seriesDevOpsDays DenmarkDevOps is Broken2026-03-30T00:00:00+00:002026-03-30T00:00:00+00:00https://www.devopsdays.dk/stories/devops-is-brokenWhen we ask "Is DevOps dead" we hear: "No, but it transformed into Platform Engineering". OK, but that's Ops, not DevOps. What happened to "You Build It, You Run It" and the "Break down the silos" promises?
Is DevOps dead? The organizers of DevOpsDays Denmark experienced a severe drop in interest in participating in this year’s DevOpsDays conference. It is now cancelled, and the Danish DevOpsDays Association must review its bylaws.
What is happening
Despite the fact that DoD usually pulls a decent crowd, this year’s conference showed odd signs of inconsistency and misbehavior:
We had plenty of people who wanted to speak at the conference
We had more sponsor requests than ever seen in our 8-year history
We had no sign-ups at early-bird rates
And only 7 sign-ups since the program was announced
We kicked off a LinkedIn discussion and sent out a questionnaire to 555 previous DoD attendees asking “What is happening - is DevOps dead?”
In contrast to the missing sign-ups, we got a lot of feedback. I’ll try to summarize:
DevOps is not dead, but it has transformed into platform engineering, IaC, and tool-oriented Ops rather than a Dev-focused practice, and this realm is already quite well covered and organized by the Cloud Native Foundation community.
The socio-technical systems focus that defined DevOps in the early years of the movement has no clear “new home.” The DORA agenda, together with DevX and agentic AI, each covers bits and parts of it.
Former participants mostly report that they “cannot convince managers to take two days off for a DevOps agenda”.
A few memorable (and opinionated, but probably true’ish) comments from the questionnaire:
“DevOps conferences have turned into a gathering of platform engineering people. It’s not Dev and Ops coming together it’s Ops turned into DevOps turned into Platform Engineering. It’s like pretending SAFe is Agile.”
“I don’t think DevOps is dead. I think the world is on fire and everyone worries about having a job and not about going to yet another conference.”
“To me DevOps is nowadays something I expect people to study and know about but we don’t use the word in our teams anymore. I think what is currently interesting — and will be even more with the introduction of LLMs — is the people side. People in tech.”
What is Next?
Well, first of all, we hereby announce:
The conference on April 28+29 is off - it’s cancelled.
The sponsors and the few sign-ups we had will, of course, be refunded - no questions asked.
Other than that here’s our draft playbook for the future:
The board of the Danish DevOpsDays Association will hold an extraordinary meeting on April 9 to discuss a new purpose and revised bylaws. We expect to meet again in late April or early May to formalize new statutes.
The sentiment, and what will most likely happen, is that we will rename and rebrand the association. This may include disassociation from DevOpsDays charter and organization.
The overall purpose stays “People in Tech”, and the association will continue to drive community discussions on “What the heck is going on in tech these days.”
We will transform from an annual 2-day conference into … something else. We want to lean toward smaller but more frequent events: Open Space sessions, Lean Coffee meetings, and workshops, based on our interpretation of the feedback that discussion and sharing spaces are what people need most.
It’s likely that we will put additional focus on digital content (slack content, video recordings of presentations and demos, audio recorded interviews and discussions, blog posts).
We will continue to have an annual main event - but it will be very different (details not decided yet)
We will still have presence in both Aarhus and Copenhagen.
We will still have sponsors, so we will remain in a position to drive and support the community financially and to produce high quality content.
We will remain a non-profit organization.
The content will be entirely free.
Our aim is that the events will also be entirely free for participants - occasionally with a small “catering fee”.
These are not the new purpose or bylaws - yet. But they are a glimpse into what is cooking.
If you wish to take part in - and contribute to - this transition into something new, consider joining the organizers’ team and making your voice heard there.
]]>Lars KruseCommunity Sponsor2026-03-04T00:00:00+00:002026-03-04T00:00:00+00:00https://www.devopsdays.dk/stories/community-sponsorFive employees. One Conference. A manager's best decision; Send them to DevOpsDays. Get your logo on the conference web site and get shout-outs from the official DevOpsDays profile.
Being a community sponsor is like drinking distilled good DevOps karma: Show the World that you take DevOps seriously …And in the process save more than 1000 DKK.
You get:
Five conference passes (two full days)
Your Company logo and profile page here on <devopsdays.dk>
“Unless you are already EXACTLY where you want to be in regards of Platform Engineering, utilization of Agentic AI in software development, Infrastructure as Code, DevX, shift-left mindset and Continuous Delivery, then becoming an engaged member of the DevOps community of practice is probably the best knowledge investment you could make for your team.”
The DevOpsDays is a yearly recurring two-days conference. We have been in Denmark since 2018. The conference is famous for being engaging.
We run an unconference format with short, sharp speaks (only 30 mins) and Ignite talks (5 minutes pitches) all carefully curated with the purpose of creating disturbance, insights and raising eye-brows aas well as discussions and we only do bums-on-seats until lunch. After lunch we break out in Open Space discussions, Lean Coffee discussions, workshops - and just plain mingle.
On the evening before the event we meet for an informal Drink-up and on the evening of the first conference day we all stay behind for snack food and drinks.
It sounds like the “hyggeligeste” conference ever and it is. But do not confuse this from the fact that it is the DevOPs intelligentsia attending. We talk shop for two days straight_. Participants will build professional relations for life and develop mind-blowing innovative perspectives on every-day problems.
Our community is non-profit, driven by volunteers under the international <DevOpsDays.org> brand. We are financed solely by conference guest tickets and sponsors. We ran the first DoD in Denmark eight years ago. We empty out pockets on each event and still …we’re here!
Show the World that you take DevOps serious. It both attracts talent and it makes you team members proud. Supporting this community is like drinking distilled good DevOps Karma
]]>Lars KruseBecome a Speaker2025-12-15T00:00:00+00:002025-12-15T00:00:00+00:00https://www.devopsdays.dk/stories/become-a-speakerSimon on stage at DevOpsDays 2022 - his first public speak. Schooling the community in 'DevOps for Entrepreneurs' click the image to see the full talk
At DevOpsDays we are always on the look-out for speakers that can teach us, inspire us or simply entertain us. We put on talks that balances the cultural and technical aspects of anything DevOpsy. Speakers in our community range from first-time-on-stage talents to top-dog international keynote-for-a-living.
“All accepted speakers and co-speaker will always be given a full conference pass”
Our community is non-profit, driven by volunteers and financed by sponsors. And we are a localized chapter (Denmark). This implies, that as a rule of thumb, we do not compensate speakers with actual fees. Instead we will encourage you to pledge your own employer to cover your own expenses. If that is not an option then we may occasionally step in and reimburse expenses like travel and accommodation but typically only within the region of our localized chapter.
Keynote speakers and DevOps Rock Stars
An exception to no-expenses policy is, if you are an invited professional keynote speaker, then we may well accept you usual (friendly) fee — and reimburse even longer travel distances and longer stays.
Mentor or Trainee program
“We will not judge you by lack of speaker experience but by your potential impact”
If you are a novice speaker, with no history to show, you must not hesitate to submit. Don’t be shy. Do it! We will help you!
If your topic is relevant and your urge to speak is strong, then we can offer to appoint you a mentor from among the experienced speakers in our program committee. The mentor will help by reviewing your submission, your narrative, your slides or demo - and give you tips an tricks to calm your nerves and stay relevant.
We can also offer you to utilize our community as a training field, by organizing a pre-run of your speak in a less formal meetup group, in a cozy setting, in front of a smaller audiences, with a facilitated feedback session to wrap it up.
Even if you are not a speaker yet, we will support you to become one.
In our open slack we have a public channel #speakers‑guild that we encourage all speakers to join. In this channel speakers can call always reach out to peers and ask for help, advise and feedback. This channel is also monitored by the mentors, so you will get a reply when you post here.
If you whish to get a speaker mentor - simply post your wish in the channel.
What is a good DevOps Topic
We made an separate story dedicated to that topic: DevOps Evolution. The post also contains a quite extensive glossary of tools, terms, concepts and principles that DevOps encompasses.
The short message is that:
“Maybe we don’t need to define DevOps; just reflect on what it embraces”
Contemporary DevOps spans so wide, and our community is inherently curious. So if you are in doubt if it fits, then we urge you to go with the benefit of the doubt - it probably fits.
At our annual DevOpsDays conferences we run the following formats:
Keynotes — 45-90 mins, experienced speaker
Regular presentation — 30 mins
Ignite talk — 5 mins, 20 auto-advancing slides, exactly 30 secs on each
Facilitated Workshop — 30 min workshop, audience of 10-20 people
At the DevOpsDays conferences we also run series of Open Space sessions. The topics for these sessions are suggested and dot-voted for interest at the conference itself. The ones that attract the most interest gets a 30 min slot. All the conference participants then spread out in smaller group settings to the topics that interests them. It’s quite fun. If you have never participated in an Open Space session before you’re in for a treat.
The workshops run in parallel with the Open Space sessions as alternative sessions, but in the same 30 min slots.
The type of presentations is free, and totally up to you - surprise us! I can range from:
Case study
Transformational Journey
Mastery at display
Running code from stage
Provocation
Panel discussion
F*ckUps
Perspective
…surprise us
How to get your proposal accepted
In the early days of the TED organization the accepted speakers were sent a physical stone plate as a prop. It was meant as playful reference to the biblical Ten Commandments given to Moses on Mount Sinai. But with the deliberate intent to (lightly) intimidate the speakers with the importance and seriousness with which TED treats the quality of its presentations.
Put some effort into the proposal, this is your first encounter with he program committee — and first impressions lasts. It exemplifies how you present ideas and how you convey information.
We will never reject submissions solely based on the fact they come from a vendor, But be mindful that we generally adhere to the TED commandments and especially commandment VII: “Thau Shall Not Sell From The Stage”.
While we will not accept vendor pitches disguised as talks we would love to see you as a sponsor. You will get you own booth in the venue foyer and from there you can pitch anything you want - no rules, no questions asked.
Among the active members of the DevOpsDays organizer group, we currently either collaborate with, cross-organize or co-host with the following localized MeetUp Groups:
We can effortlessly facilitate and arrange that whatever the format you want to present may be, we can setup a contact to an informal Meetup event to give it a trial run.
]]>Lars KruseDevOps Evolution2025-12-13T00:00:00+00:002025-12-13T00:00:00+00:00https://www.devopsdays.dk/stories/devops-evolution
What is DevOps — we have discussed this since the #DevOps hashtag was first used, but maybe we don't need to define it; just reflect on what it embraces
DevOps Evolution
“What is DevOps?” — we have discussed this since the concept hatched in ~2008, but maybe we don’t need to actually define it; just reflect on what DevOps encompasses and embrace it all in the our Community of Contemporary DevOps
I set out to write this post with the intent of guiding potential speakers at our conferences in the commonly asked question:
“Is my topic fit for the DevOps Conference?”
The post still serves that purpose but it also double a good read for participants at our conferences in getting a feel for what the content of our conferences could entail.
It even triples as an invite to practitioners of everyday “dev” and “ops” chores to see that their skills are indeed DevOpsy and unite with peer, masters and apprentices under our DevOps banner.
DevOps was invented as Twitter hashtag #DevOps for a conference on Agile Infrastructure in 2009 in Ghent. Already the year after, the same recurring conference was branded as DevOpsDays. And here we are!
But hey: “isn’t agile dead?” you might ask. And if that is the case isn’t DevOps dead too then?
Well; “NO! — no one died”. But it’s right to question if DevOps is the same as when it was hatched in 2008 — it’s not. DevOps has evolved a lot and you have a standing invitation to join the community and both contribute and challenge the what DevOps really is.
2008 – 2015 Branching Strategies and Automation Pipelines
Paul Duvall published a book “Continuos Integration” in 2007 and Humble and Farley published “Continuous Delivery” in 2010 The were both in A&W’s “Marting Fowler Signature Series”. And while DevOps doesn’t have an actual widely accepted manifest like the Agile paradigm have, these two books are the closest we come to a common ground the DevOps paradigm. Due to the endorsement from Martin Fowler one of the Agile Manifesto’s Founding Fathers and a widely recognized Agile movement celebrity the tie between Agile and DevOps was undeniable — especially in the early years.
“CI/CD” became a synonym with DevOps. The Jenkins CI server; Kohsuke Kawaguchi’s masterpiece of a configurable and expandible Open Source build automaton platform was the most novel concept introduced to Software Development since the introduction of Object Oriented programming. Jenkins CI was forked off of Hudson in 2011. It was a story of David fighting Goliath (Kohsuke vs Oracle). Everyone should have Jenkins Ci server.
2015 — 2020 Containerization and NUM3ER5 — The split
Docker was release in 2013, an astronomical evolution step in IT by itself. Cloud Native Foundation and Kubernetes were co-released in 2015 and it’s fair to say that the World hasn’t been the same since. The DevOps community was the first to embraces containerization as unconditionally good.
DevOps ❤️ Containers. Concepts like Configuration as Code and Infrastructure as Code became hot topics. Tools like Terraform and Helm emerged to make infrastructure programmable and reproducible, transforming how operations teams provisioned and managed cloud resources at scale.
Observability matured alongside containerization. Prometheus and the ELK stack made it possible to see into distributed systems in ways we’d never imagined. And Google’s Site Reliability Engineering (SRE) handbook in 2016 introduced a distinct philosophy that automation and data-driven operations are the path forward. DevSecOps also emerged as a trend, advocating that security couldn’t be bolted on at the end—it had to be woven through the entire delivery pipeline.
In the early days on the DevOps movement it attracted more “devs” and less “ops”. Now with the containerization and orchestration perspective, DevOps built a home in the Cloud and all the “ops” could see themselves as first class citizens there. Yet as cloud costs spiraled, FinOps emerged around 2019 as a counterbalance — reminding us that fast deployment means nothing if you’re hemorrhaging money on idle resources.
In the early days of DevOps the sentiment was that “DevOps is a culture — breaking down silos” Gene Kim was an important avantgarde for this perspective. It was also in 2015 Gene Kim release the novel “The Phoenix Projects” which won wide recognition as the “DevOps New Testament”. We would proudly parade doctrines like “DevOps is Culture” and “DevOps is not a team — It’s a way of working”
In 2018 Kim joined forces with an old DevOps celeb; Jez Humble and a new protégé Nicole Forsgren — a number-crusher magician and they jointly release a new book “Accelerate” in 2018 explaining the rationale behind the DevOps Research and Assessment institute (DORA) report which they had released annually since 2014.
DORA offered a clean lean perspective on DevOps and Continuous Delivery. Focusing on lead-times, value stream optimization, build-quality in, Throughput and Stability advocating that we should analyze and optimize our workflows based on actual NUM3ER5 pulled from the system.
During this period DevOps as a concept formed two new distinct schools - on top of the already established “DevOps is CI/CD” and “DevOps is Culture” ones. We had arrived at a somewhat ambiguous point:
“DevOps is CI/CD”
“DevOps is Culture”
“DevOps is Programmable and Immutable Infrastructure”
“DevOps is lean software development stream optimization”
A split was emerging. KubeCon and Cloud Native Foundation — although considered inherently good also offered a cleaner alternative home for all the “ops” and a good portion of them moved out of the house and never looked back.
The DevOps movement was once again in jeopardy of being a mostly “devs” community.
2020 — 2023 Serverless, Full-stack and DevX
Firebase (Google), Supabase (PostgreSQL), Cloud Functions(Azure), Lambda function (Amazon) all matured quickly in the new containerized world and soon offered a compelling NoOps alternative to servers without the need to become a Docker expert on the side. Embraced by millennials and zoomers who — in the mean time — had been thought in uni that full-stack=MERN1 stack.
GitHub release CodeSpaces in 2020, a web based NoOps extension based on devcontainers (2019) also natively supported by VS Code, and myriads of other Open Source IDE spin-offs. Containers were no longer exclusive to cloud and infrastructure nerds. They regained relevance to all developers in an emerging Developer Experience (DevX) trend. Where event the Development environment, the IDE and the workflows were containerized too. The shift to remote-first work — obviously driven forcefully by the COVID pandemic — accelerated this adoption. Teams distributed across geographies embraced containerized development environments as a way to ensure consistency and reduce friction.
Nowadays every develop can hack a Docker file, setup their own declarative pipeline in yaml and deploy to some abstraction of an infrastructure in the cloud.
The DevOps proverb “You Build It You Run It” is now widely embraced even by the new generations, although not entirely the way the boomers and Gen-X that inhabited the Devops world had anticipated. The apprentice surpass the master. But hey, isn’t that what all true masters unselfishly hope to aspire in there apprentices?
The fresh blood and young minds were welcomed into the DevOps community.
DevOps isn’t dead — it’s simply the new normal.
2024 — … I Dare You — Say ‘AI’ One More Time
GitHub released Co-Pilot for technical preview in February 2021 and it was made publicly available for subscriptions in June 2022. Already in 2024 both DORA, Stack Exchange and GitClear could reveal convincing statistical proof that AI is jeopardizing the overall quality of mankind’s joint codebase at a speed that no one could have predicted.
At the same time AI, Vibe Coding and Prompt Engineering is — apparently — enabling DevOps core values like fast feedback loops with end-users and breaking down silos, by allowing Citizen Developers and self-made hackers to produce — apparently — ruining code at a pace that also no one could have predicted.
Developers cry out – “code quality is as risk” and while the do, the LLM’s are improving at a speed that exceed even the most farfetched Science Fiction.
The “Terminator Trilogy” dystopias may turn out to be unambitious compared to real-life.
The DevOps community keep focus on Developer Experience and Continuous Delivery and DevOps core values like maintainability, security, reliability are up for being redefined in the AI era.
We take it on our shoulders to do that. We obviously don’t know what will hit us next, but we know that we will stay united.
Contemporary DevOps buzzes
Below is a glossary of some of the terms, tools, techniques and concepts that are encompassed in Contemporary DevOps
Automation / Autonomation
Process of automating repetitive tasks to reduce manual effort and human error. Autonomation (automation + autonomy) extends this by enabling systems to make intelligent decisions and self-heal without human intervention.
Automated Testing
Practice of writing and running tests programmatically — unit, integration, end-to-end—to validate application behavior continuously, reducing manual testing effort and catching regressions quickly.
ChatOps
Practice of executing operational tasks and automations through chat interfaces and bots, bringing visibility to operations work, enabling collaboration, and reducing context-switching between tools.
Citizen Development
Empowerment of non-traditional developers to build applications and automations using low-code/no-code platforms and AI assistance, democratizing software creation across the organization.
Configuration as Code
Infrastructure and application configuration expressed as versioned code rather than manual setup, enabling reproducibility, auditability, and integration into version control and deployment pipelines.
Configuration Management
Practice of systematically tracking, controlling, and applying changes to system configurations across infrastructure and applications, ensuring consistency, auditability, and repeatability in environments.
Containerization
Lightweight virtualization technology that packages applications with their dependencies into isolated, portable units. Docker revolutionized this space by making containers accessible to mainstream development teams.
Continuos Integration
A set of branching strategies and work disciplines that advocates and encourages teams to keep the main integration branch always shippable — sometimes also referred to as Trunk-based development.
Continuous Delivery
A software development practice that lends from lean principles and advocates that quality should be controlled at the source and automated one-piece flows should carry the changes all the way to actual deployment in production.
Culture and Silos
DevOps principle that technical practices alone cannot succeed without cultural shifts breaking down barriers between development and operations, enabling collaboration and shared ownership.
Dashboards / Visualizations
Real-time displays of system metrics, application performance, and business KPIs that make complex data accessible at a glance, enabling quick decision-making and incident response.
Declarative Pipelines
CI/CD approach where pipeline configuration is expressed declaratively—defining desired state rather than imperative steps—enabling version control, reproducibility, and easier maintenance of build and deployment workflows.
Developer Experience (DevX)
Holistic approach to improving developers’ satisfaction and productivity through better tooling, workflows, documentation, and environments—recognizing that developer satisfaction drives software quality.
Developer Platforms & Marketplaces
Centralized ecosystems (e.g. Backstage, GitHub Marketplace, artifact registries) that discover, share, and manage DevOps tooling, templates, and extensions — enabling knowledge sharing and accelerating adoption of community practices.
DevContainers
Development containers specification and tooling that standardize local development environments in containers, ensuring consistency across team members and with CI/CD pipelines.
DevSecOps
Integrated practice embedding security throughout the entire software delivery pipeline rather than as a bolted-on afterthought, shifting security left and making it everyone’s responsibility.
DORA Metrics
Four key metrics—deployment frequency, lead time for changes, mean time to recovery, and change failure rate—used to measure software delivery performance and organizational effectiveness.
Emulators / Digital Twins
Virtual replicas of physical systems or infrastructure that simulate real-world behavior, enabling teams to test, validate, and optimize solutions in safe environments before production deployment.
Extensions / Plugins
Ecosystem practice of extending existing platforms — e.g. GitHub Actions, VS Code extensions, Kubernetes operators, Terraform providers — allowing practitioners to contribute reusable solutions and amplify DevOps practices across communities.
FinOps
Financial operations discipline for cloud cost management, treating infrastructure spending as a shared responsibility between engineering, finance, and operations to optimize cloud investments.
FlowTech
Emerging discipline focused on optimizing developer workflows and productivity by removing friction points, integrating tools, and automating context-switching — extending DevX principles across the entire development lifecycle.
GitOps
Operational model using Git as the single source of truth for infrastructure and application configuration, automating deployments when code changes are merged, combining version control with continuous delivery.
Helm
Package manager for Kubernetes that simplifies deploying and managing complex applications by bundling manifests, configurations, and dependencies into reusable charts.
IDE Integrated AI Agents
AI-powered tools integrated into development environments that generate code suggestions, assist with problem-solving, and augment developer productivity in real-time. Represent both the democratization of coding and emerging quality concerns in the AI era.
Infrastructure as Code (IaC)
Practice of managing and provisioning computing infrastructure through machine-readable code rather than physical hardware configuration or interactive tools, enabling version control and automation.
Internal Developer Platform (IDP)
Self-service platform built by platform engineering teams that abstracts infrastructure complexity, allowing developers to deploy, scale, and manage applications without deep operational knowledge.
Kubernetes
Open-source orchestration platform that automates deployment, scaling, and management of containerized applications across clusters, becoming the de facto standard for container orchestration.
Lean Software Development
Software engineering discipline rooted in lean manufacturing principles—emphasizing waste elimination, value stream optimization, fast feedback loops, and continuous improvement. Core philosophy underlying DevOps practices and metrics like DORA.
Observability
Practice of understanding complex system behavior through comprehensive data collection—logs, metrics, traces—enabling teams to ask arbitrary questions about system state and quickly diagnose issues.
Platform Engineering
Discipline focused on building internal developer platforms that abstract infrastructure complexity, enabling development teams to self-serve while maintaining governance and security.
Prometheus
Open-source monitoring and alerting toolkit that scrapes time-series metrics from applications and infrastructure, providing a flexible foundation for observability in cloud-native environments.
Prompt Engineering
Skill of crafting effective instructions, RAGs and queries for AI language models to generate useful code, documentation, and solutions—increasingly important as AI tools become integral to DevOps workflows.
Serverless / FaaS
Computing model where cloud providers manage infrastructure, allowing developers to deploy functions or code snippets that scale automatically without managing servers or containers.
Site Reliability Engineering (SRE)
Google-formulated discipline that applies software engineering approaches to infrastructure and operations problems, emphasizing automation, data-driven decisions, and error budgets for reliability.
Social Coding
Collaborative development culture enabled by platforms like GitHub, emphasizing code review, transparent collaboration, knowledge sharing, and distributed contribution — a cultural cornerstone of modern DevOps.
Static Code Analysis
Automated examination of source code without executing it, detecting potential bugs, security flaws, and code quality issues early in development, shifting quality checks left in the pipeline.
Terraform
Infrastructure as Code tool that enables declarative definition and management of cloud resources across multiple providers, treating infrastructure provisioning as reproducible code.
Tooling & Scripting
DevOps practice of building, maintaining, and sharing custom utilities, scripts, and helper tools that operationalize workflows, reduce manual effort, and enable team-specific optimizations and automation.
Vulnerability Scanning
Automated process that analyzes code, dependencies, and running systems to identify known security vulnerabilities, enabling proactive remediation before exploits reach production environments.
You Build It, You Run It
DevOps philosophy that teams owning code also own its operational aspects and incident response, fostering accountability and enabling faster feedback loops and improvements.
MERN: MongoDB - Express - React - Node. A contemporary alternative to the LAMP stack (Linux - Apache - MySql - PHP) ↩
]]>Lars KruseOur own slack2025-12-09T00:00:00+00:002025-12-09T00:00:00+00:00https://www.devopsdays.dk/stories/slack
We’re happy to announce that we have setup our our own slack. It’s open to all, and especially conference participants are encouraged to join.
]]>Lars KruseBlogging at devopsdays.dk2025-12-01T00:00:00+00:002025-12-01T00:00:00+00:00https://www.devopsdays.dk/stories/blog-with-us
We’re happy to host or cross post your DevOps related posts here on our site. If you have written something share-worthy give it a spin here at our community page.
When we ask "Is DevOps dead" we hear: "No, but it transformed into Platform Engineering". OK, but that's Ops, not DevOps. What happened to "You Build It, You Run It" and the "Break down the silos" promises?
Five employees. One Conference. A manager's best decision; Send them to DevOpsDays. Get your logo on the conference web site and get shout-outs from the official DevOpsDays profile.
