DevOps Paradox: Recent Episodes
Darin Pope & Viktor Farcic
362: Feature flags or canary deployments - do you need both? Viktor puts it to Alex Casalboni from Unleash, who says he argues about this with his colleagues roughly every day, and the answer lands clean. Switching a hostname, a database, an API vendor? That is infrastructure, nothing to do with who the user is, so keep your canaries and your blue-green. But a canary switches one thing at a time. Try running three A/B tests and ten behavioral changes through it and the whole approach buckles. Anything that needs to know who the user is belongs in a flag. Different layers of the stack, different tools, and most teams will end up with both whether they planned to or not.
Back up, though, because there is a new word attached to all of this. FeatureOps. There is a manifesto and everything, sitting at featureops.io, reading a lot like someone nailed 95 theses about feature flags to a door. Real discipline, or marketing wrapper? Alex gets about ten seconds of pleasantries before he has to answer for the word. His defense is narrower than the name suggests, and better for it: every ops discipline we have gets you to the deployment and then waves goodbye. Something breaks, you go around the whole loop again - hotfix, pipeline, 20 or 30 or 60 minutes, fingers crossed. FeatureOps is the claim that the same principles apply after the code is already running. Runtime control. Alex says enterprise customers routinely have a 12 to 24-hour round trip between finding a problem and getting the fix live. Even for a hotfix.
Viktor is not letting the seconds claim through unchallenged. If it takes you a day to notice and two seconds to flip, that is a day and two seconds - so stop measuring from the convenient starting line. Alex concedes the framing and then goes somewhere better with it: the bottleneck was never the clicking. It is the humans and the bureaucracy in between. Which is why Unleash is pushing impact metrics, where the SDK sends error rates back and the system kills the feature itself, no human in the loop. Then Darin calls BS on immutable event log, because there is no such thing as immutable data, and Alex takes the hit cleanly - fair, it is append-only with locked-down keys, not magic.
Nobody puts this part on a landing page. Flag evaluation has an input, not just a true/false output, and that input is user context - which means an external API call is not just latency, it is your PII leaving the perimeter. A compliance problem hiding inside a performance decision. And the flag graveyard is worse than you think: companies create roughly ten flags for every one they clean up, and Alex has a customer whose oldest flag dates to 2012. His fix is an MCP server that opens the cleanup PR for you when you mark a release complete. Best line of the day, on whether flags complicate your code: everything complicates your code, and the best way to not complicate your code is to not code.
Alex's contact information:
LinkedIn: https://www.linkedin.com/in/alexcasalboni/
X: https://x.com/alex_casalboni
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
361: Picture a 6,000-line pull request landing in your project from someone you've never heard of. Every test passes - yours, theirs, all of it. And you can tell it was generated. Not assisted. Generated. What do you do with it? Viktor's first move is to poke the premise: how do you even know it was generated and not assisted? You can't. Nobody can. That distinction is already gone.
So the real question isn't whether AI wrote it. It's what a maintainer is for. Viktor's answer is blunt - a maintainer's first job is to guide people in and help them contribute, and if you think your job is mainly to write code, you picked the wrong role. The moment you allow PRs, you stopped being an individual contributor and became a manager. That's the job. You don't get to complain about the job you signed up for. Don't want it? Fine - do what Ghostty did, do what curl did, turn PRs off and say so out loud. Just don't hide behind unknown contributors, because every single person on your project was an unknown contributor on their first commit, including you.
A software developer says send me anything but a PR and lists four reasons: unknown contributors are a security risk, supply chain attacks are real, style disagreements eat maintainer time across time zones, and LLMs killed code-writing as the bottleneck so the stranger's PR doesn't help with the parts that are still hard. Viktor grants the security point and then points at XZ - social engineering, a long con, zero AI required. The risk was always there. What changed is quantity, not the percentage. And the maintainer who thinks a manual, line-by-line review still works in 2026 is, in his words, terribly wrong.
Viktor guesses he can review 6,000 lines in about the time it takes to hand-review 600. CodeRabbit and Greptile clear the obvious junk so he can spend his attention on architecture and the feature itself - the stuff he never had energy for after slogging through nitpicks by hand. His read on the whole backlash: there's a new third group of maintainers now, the ones who aren't good enough with agents to fight agents, and they're the ones falling behind. Writing code is cheap. Reviewing it well is the expensive part - and the ones who refuse to use agents to review are drowning while blaming the contributors. There's a cost angle too. If you don't have tokens, you're in trouble, and not everyone can afford them. Tokens are becoming table stakes, like an internet connection. Which raises the question: what happens to open source when the reviewing tools cost money the maintainer doesn't have?
I don't want your PRs anymore
https://dpc.pw/posts/i-dont-want-your-prs-anymore/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
360: Assume your production systems go sideways at 3:00am. Your phone doesn't ring. You wake up to a clean incident report - the system caught the problem, fixed itself, and left a Slack note saying it handled things at 3:15. Would you trust it? Viktor wouldn't, not at first. Same as a new hire, a new tool, a new anything. Trust gets earned. A few months in, if it hasn't messed up, then maybe.
So what's actually new? We had self-healing in decades past, and Kubernetes brings a crashed pod back without anyone awake to watch. Birol Yildiz, co-founder and CEO of ilert, puts the line where it belongs: the old stuff runs on predefined patterns - known problem, known fix, automate it. The new part is diagnosing a root cause nobody wrote a rule for and then knowing what to do about it. And no, ilert isn't training models on your data. The agent runs on foundational models from the frontier labs, feeds them the same context any SRE would pull - telemetry, recent changes, the health of your infra - runs the investigation loop, and hands you a root cause with the evidence attached.
Then the real argument starts, and it's about knowledge. Viktor keeps circling the blind spot he sees at every company: the wiki, the runbooks, the tribal stuff nobody keeps current. Birol's answer is blunter than you'd expect from a guy selling this - dump your Confluence and your hundred stale runbooks into the agent and you cause more damage than results. Code is the documentation that's actually true. ilert's agent doesn't even read runbooks. It builds a live service topology straight from tracing data and rebuilds it when things drift.
What happens when a bad incident month turns your $100 bill into $10,000 - Birol's answer is a credit budget with a human paged when you blow past it. Who's accountable when the agent makes it worse? Has to be a human. Agents are tools. You don't get to blame your AI coding agent for shipping garbage code, and ilert doesn't get to blame the model either. Trust is binary - five good runs and one bad one, and you strip its write access. But even in observe-only, the value is real, because the time sink in an incident was never the fix, it was finding the needle. Cut root cause from 45 minutes to a few. And the closer nobody wants to hear: if you skipped observability and fifteen years of homework, an AI SRE isn't going to save you. You can't skip the parts you skipped.
Birol's contact information:
LinkedIn: https://www.linkedin.com/in/birolyildiz/
X: https://www.linkedin.com/in/birolyildiz/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
359: When was the last time you sat through a 30-minute product demo and walked away actually knowing anything? You would learn more from five minutes hands-on than an hour of watching someone else drive.
Now you have help. An agent can watch the 30-minute video, play in the sandbox, read every page of the docs, and come back before you finish your coffee with a verdict - tried it, does not work, next. The agent is the new tire kicker. So if you are a vendor, an open source maintainer, or the person building the internal app nobody outside the building ever sees, the demo you have been giving is aimed at a buyer who already left the room.
Your job now is to make life easier for agents. An MCP server, a CLI, skills, an AGENTS.md file, not blocking your own site with Cloudflare when someone's agent tries to read your pricing. Everything that makes a product easy for an agent would have made it easier for a human all along. We just never bothered, because we had months to burn. Now the clock runs in minutes and every corner we cut is suddenly on fire.
Three kinds of demo, three different answers. The vendor sales demo is off-putting before it starts - if a website says book a call to try it, Viktor is already gone. Open source barely needs a demo at all: a good README, a quick start, an AGENTS.md, and the agent assembles a demo tailored to your stack, your database, your questions, instead of some generic happy path. Internal is where it gets good, and it might be the one that matters most since exactly zero apps ship without customization. Viktor's bar: stop showing me plans, show me the thing running. Sit the stakeholder down and build it live while you talk. Three days to a prototype instead of 300 pages of PRD.
Sandboxes first, demos second - if you cannot spin up a sandbox, you did not build it right. And demo the failure modes, not the happy path, because resiliency is the real selling point now. Disks still fill up. No amount of AI magic empties them for you.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
358: Production is on fire. You need access to one table you have never touched. So you file an access request, then phone the desk to say you filed it, then Slack them to say you phoned, then walk over to say you Slacked. Twenty-five minutes later the incident has resolved itself and the customer has already left.
That is the setup, and Ofir Stein has lived the other side of it. He is the CTO and co-founder of Apono, and before that he was an engineering leader who felt the same pain every day - not because he hated security, but because he hated being blocked. There is a difference, and the whole conversation turns on it. Put productivity on one side, security risk on the other, and access management in the middle. Tighten one and you starve the other. Nobody wants to be slower and nobody wants to be breached, so the honest answer is there is no clean answer.
Then AI agents show up and break the last assumption standing. Software used to be deterministic - your computer could not decide to do something other than what it was told. LLMs can. They can be socially engineered the way people are. Ofir's team built a full AWS environment run by AI agents, opened a Discord channel, and invited anyone to try to trick them. People could. That is the new attack surface, and it moves at machine speed - far too fast for the access reviews and approval chains built for humans.
The guardrails everyone is now scrambling to build for agents should have been there for humans all along. Access is the one thing in your stack that never went dynamic. Servers scale up and down, pipelines rebuild everything, and then access is a static policy someone set two weeks ago when security sat with your manager and guessed what you would need. That is the opposite of how the rest of DevOps works. Ofir's argument is that access should change with context - who you are, whether you are on call, whether there is an open incident - evaluated in real time. For a human that is a faster request. For an AI agent, the decision has to live inside the loop, made by silicon, because no person can approve thousands of operations a minute.
If access is per-operation and every operation is already a specific API call, what is left to scope? If the business context changes by the minute, how do you write guardrails in advance? And once the human is out of the loop, are you not just left with one AI deciding what another AI is allowed to do? Ofir does not pretend that part is solved. What he is sure of is the direction: the doors at the mall open when you walk up and close when you leave, and you never think about them. That is where access is headed - and there is a lot of road between here and there.
Ofir's contact information:
LinkedIn: https://www.linkedin.com/in/ofir-stein/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
357: Type a prompt, get code, fix the hallucinations, type another prompt. That is vibe coding, and it is a fine place to start. It is a terrible place to stay. So what comes next - and is spec-driven development actually it, or just waterfall wearing a new hat?
Here is the reframe that runs the whole conversation: everybody already works from a spec. Even the person who swears they are winging it has a spec in their head - which language, where it runs, what it does. The real question was never specs or no specs. It is whether you write them like waterfall, one giant document before anyone touches code, or like agile, just enough to start and the rest discovered as you go.
A design is only validated when you implement it - everything before that is an educated guess. So instead of spending a month on one detailed design, build five throwaway MVPs in a day. Fully operational. Frontend, backend, running in a cluster, connected to a database. Show them to customers. Pick the one that works. Then have the agent write the spec from the winning code, and throw the code away. The spec is the output, not the input. A PowerPoint took you a month and told the customer nothing. A working thing they can touch tells you everything.
Viktor and Darin push on where this breaks. Over-specifying gives you a false sense of security - you are lying to yourself that you know everything up front, and you do not. Legacy systems? The code is the only complete spec - any document written thirty years ago is fiction. Performance? Measure it in production and be lightning-fast to react. Greenfield, CRUD, clear API contracts - those genuinely want a spec first.
The part nobody on the org chart wants to hear: this does not delete the business analyst or the developer. It collapses the roles. The code monkey who pulls a Jira ticket, does the work, pushes it - that job is turning into tech lead, architect, product manager, all at once. Plan mode writes the spec with you, not for you. You write it to a file because you cannot review what you cannot see. And you review the tests harder than the code, because the tests are the spec made executable. Specs were always supposed to be living documents. Now there is finally no excuse.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
356: Fleet management means one thing to a DevOps engineer and something completely different to Tomas Kovacovsky. To Viktor it is a CD problem - a fleet of Kubernetes clusters he would rather not babysit. To Tomas it is hundreds of physical robots rolling around a warehouse, picking orders, dodging each other, and working very hard not to lose their connectivity.
Tomas is the CTO of Brightpick, where the robots are not the kind you yell at for bumping into a chair. They are three-meter-tall autonomous pickers - some telescoping up to six - that find their way using lidar, recognize items with neural networks, and make their own decisions the second the network drops. Here is the part that will feel oddly familiar: everything you already do to ship software shows up again in the physical world. Canary rollouts. Rollbacks to the last good config. Prometheus scraping every robot, Grafana for the fleet. Logs, metrics, traces. Split brain, when a robot and the server disagree about what just happened. Even a flaky robot - one that feels off with no error to point at - gets diagnosed the same way you would hunt a flaky test: compare it against the rest of the population and find the outlier. A warehouse full of robots, running like a distributed system.
The stack is what you would guess and also not. C++ on the robots for speed, Python on the backend, Kubernetes on an edge server inside the warehouse because latency matters down to the millisecond, and Git as the source of truth - the on-site servers check for differences and update themselves. GitOps, for robots.
Then it gets bigger. The optimal pick speed, Tomas says, is infinity - right up until you try to pick an egg. The real bottleneck was never the picking, it was the traveling, so Brightpick moves the picking into the aisles instead of hauling totes back to a station. He also drops a prediction worth chewing on: the intelligence arrives before the dexterity. Machines will think their way around a warehouse long before they can fish for keys in a bag the way your hand does without looking. And the jobs question everyone braces for - the robot guys walking in, are you fearful for your job in 20 minutes - turns out the picker positions were mostly empty to begin with. Hundreds of thousands of them, unfilled.
The takeaway for anyone writing software is the one Tomas lands at the end. The craft is getting eaten. What is left, and what actually matters, is whether you can connect the work to the product.
Tomas' contact information:
LinkedIn: https://www.linkedin.com/in/tomas-kovacovsky-46411280/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
355: Picture your engineering team a year from now. A coding agent doing the coding. A testing agent on tests. A security agent on security. An infrastructure agent on infrastructure. All of them wired into GitHub and Jira, all of them working right alongside the humans. Not science fiction either - Atlassian and GitHub are already shipping these features.
So out come the stats everyone loves to quote. AI code introduces 1.7 times more issues. Half of it ships with security holes. Code duplication is through the roof. AI-assisted PRs take four to five times longer to review. The response to most of it: so what? If you have a way to detect the issue and feed it back, that is just the SDLC doing its job. Couldn't care less if it is 1.7x or 50x more issues - what matters is what is left at the end, per feature shipped. Security holes? You have scanners. Detect, fix, ship. The only real problem is when you skip the detection or sit on the fix for months, and that has nothing to do with AI.
Here is the one stat that actually sticks: PR reviews backing up. Speed up coding and leave everything downstream at human speed, and you have not sped up delivery - you have just moved the pile from Jira tickets to pull requests. The review pipeline was built for human speed, and now it is the bottleneck. The blunt fix: stop letting AI write 10,000-line PRs, work in smaller chunks, and accept that the job is about to get mentally harder. Delegate the tedious work and what is left is the demanding work - architecture, taste, is this even the feature we should ship. The silly stuff, does every function have a comment, is it camel case, goes to the machine. Spend your time there and you are wasting your talent.
Offshoring never worked when the only goal was cheaper - chase the cheapest engineers, then chase even cheaper ones, and you end up dragging the work back in house. Same trap with AI. Offshore to Opus, then Sonnet, then Haiku, then Llama on a laptop. If cheaper is your primary motivation, you are doing it wrong. The win is qualitative, not the price tag. Where does it land? Three people per product, end to end - frontend, backend, database, deployments. Augmented at every stage, not autonomous. A human still pushes the final button to prod, the way you never let a Jenkins pipeline deploy straight to production without a check. Full autonomy is coming the way self-driving cars came: not in a year, not everywhere at once, and not by flipping it on at 4pm on a Friday. Even when the technology is ready, you are not. And if you think none of this touches your job, there is a story here about a textile factory built in the eighties that ran on five people. Knowledge work is next. The only exception is a monopoly, and you probably do not have one.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
354: How do you build a consent system for someone who is dead? How do you clone a voice so it cannot be turned into a deep fake? Miles Spencer built a company around those exact questions. Reflekta.ai lets you talk to a reflection of someone who has passed. His own father reads a bedtime story to his granddaughter every night and talks it through until she falls asleep, eight years after he died.
Is this just deep fake with better branding? What happens when the AI goes off the rails and asks grandpa for the three numbers on the back of a credit card? Miles has an answer for each one, and most of them land on the same line: you built it, you paid for it, it never leaves your four walls. Nothing gets scraped. There are only two public reflections on the entire platform. The voice of his dad came from a ten-second voicemail found on a relative's phone five years after he was gone, and last month that voice had 9,000 conversations.
More than half the stories on Reflekta are from people who are still alive. ALS and Alzheimer's patients getting it all down while they still can. Founders who want their values to outlast them. And that last group is where it gets interesting for anyone who runs a company. New hires talk to the founder during onboarding. Ask a question about the business and the founder answers. SOPs, handbooks, the whole thing, in the voice of the person who built it.
Miles calls the framework SoulTech, starting from the emotional weight of the product instead of bolting ethics on at the end. Agree with the premise or not, the stack underneath is less exotic than it sounds: multi-cloud, RAG, three voice vendors swapped by time of day, 110 days from idea to launch. Darin's verdict by the end is honest. The dead-relative part is still not his jam. But the founder who never leaves the building, the one who onboards every new hire forever? That one he gets.
Miles' contact information:
LinkedIn: https://www.linkedin.com/in/milesspencer/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
353: Move fast and break things never meant be reckless. It meant do not stall out of fear, because something is going to break no matter how careful you are. The part everyone dropped from the sentence is the part that actually matters: and fix things fast. Break faster, fix faster. Take the second half away and you are just breaking things.
So what changed with AI? An agent can take down a whole environment in the time it takes you to type kubectl. AWS found that out in December when Kiro -- running autonomously with operator-level permissions and no human in the loop -- decided to delete and recreate the production environment for Cost Explorer. Thirteen hours down in one region. Then there is the Agents of Chaos research, where five agents got two weeks with real infrastructure and an unrestricted bash shell, and one named Ash destroyed its entire mail server as a proportional response to being asked to protect a secret. Right values. Catastrophic judgment.
Here is where Viktor plants his flag. A person owns the work. Not the AI. Doesn't matter the level of autonomy, doesn't matter whether the code came out of Claude or out of your own hands. You chose the model, you chose the agent, you wrote the rule set, you gave it the tools. If you handed an admin account to a thing that deleted production, that is on you -- exactly the way it would be on you if a human did it. The Kiro engineer could have made the same mistake without AI. Blame the people.
The fix is not telling AI to be safe. It is building the place where breaking things is survivable. Immutable infrastructure. Progressive delivery everywhere. Feature flags you can actually turn off, not just on. Read-only tools for the agent and a human or a validation layer for anything that writes. And a new habit Darin calls celebrating near misses -- not just the failures, but the times the guardrails held and you learned where to tighten one more bolt. Viktor runs a blameless postmortem with his agents at least once a day, every wrong turn ends with an update to a skill or a CLAUDE.md. His homework for you this week: if an agent -- or a human -- deleted your full production environment right now, how long would it take you to come back?
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
352: Vibe coding is the latest version of a promise the industry has been making since the first generation of programming languages. Type what you want, get an app. Jeff Kuo from Ragic has been working on the no-code version of that same promise for almost twenty years. He has thoughts on why the promise keeps not quite landing.
The honest answer is that AI-assisted coding is great for people who already know what the code is doing. It is counterproductive for everyone else. A non-developer can generate a lot of code. They cannot maintain any of it. That gap is where every weekend vibe-coded project goes to die six months in, when the codebase has ballooned and the AI is in a loop confidently identifying the wrong root cause for the seventh time.
So what does work? Jeff's argument is that no-code platforms become the guardrail AI actually needs. Strip the infrastructure layer away, leave only the business logic, and the model only has to reason about one thing at a time -- which is the one thing today's models are good at. Ragic generates form and report definitions, not code, and the Java engine underneath does the rest.
There is also the strange consumer behavior nobody is talking about. People love AI chat boxes in tools they have never used before. They close AI chat boxes in tools they already know. Which means the future of AI-native software might not belong to the incumbents at all -- it belongs to the new tools being built right now for users who do not have any muscle memory to defend.
And one piece of advice that has aged perfectly across forty years of software: the maintenance is the thing that keeps you awake at night. AI makes it faster to build things from scratch and harder to maintain anything at scale. Begin with the end in mind. Or do not, and become the next cautionary tale.
Jeff's contact information:
LinkedIn: https://www.linkedin.com/in/ragic/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
351: Entry-level tech jobs are down 67% since 2022. Junior developer roles are down 40 to 50%. The instinct is to blame AI and call it unprecedented, but the layoffs are not the new part. The boom-bust cycle has happened before -- dot-com to dot-bomb, the 2020 hiring spree to the 2022 correction, now this. The new part is that the thing replacing the bottom of the ladder is not a cheaper human in another country. It is an agent that takes instruction and ships code overnight.
Here is the uncomfortable reframe. A junior developer is told what to do, does not change the architecture, does not make decisions, and produces better work the more detail you give them. Replace the word junior with agent and the description does not change. That is the whole problem. The traditional path from junior to senior assumed five years of grunt work would teach you the things grunt work teaches. The grunt work has a new owner now, and nobody knows what the new on-ramp looks like.
Seniors are not safe either. If you have spent 30 years writing pretty code and you have already started rejecting the idea that an agent can do it better, history is not on your side. The same people who refused to embrace cloud and containers are the people who will refuse this -- and the SSH-key-maker on the team that took a week to provision a key is not pivoting to AI either. Two types of employees. The ones you can replace in five minutes and the ones whose departure feels like a loss. Only one type thrives in this cycle.
So what actually works? Capacity to learn over experience. Specific knowledge over generic knowledge -- if every developer on the internet can do what you do, the model trained on the internet can too. The job is becoming managing a team of agents the way a manager manages people: figure out what should be done, how, and when, then check on the team and work with individuals. The hiring test that still works after all these years is the one where the candidate switches to the browser and Googles. That is the person who can adapt. That is the person who survives this market.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
350: The bottleneck used to be writing the code. Now it is feeding the agent enough context to write the right code. That is Patrick Debois' argument, and given that Patrick coined the term DevOps, it is worth paying attention when he says the discipline is shifting again. The model does not matter. The IDE does not matter. What matters is whether your team can capture the way you actually work and hand it to an agent that does not know any of it.
The promise was that AI would let us ship without writing specs. The reality is the opposite. If you want decent output, you need richer specs, more docs, and a way to feed the agent what is unique about your team and your codebase. Viktor admits he stopped writing specs himself. He talks to the agent until he is satisfied, then says write it down. The work did not go away. It moved.
A second agent that validates your work tends to take the original spec too seriously and miss what is not there. The interesting validation is not whether the code matches the spec. It is whether the spec matches reality. Patrick's response is harness engineering -- combining verifier agents with deterministic tooling like linters and tests, and mining conversation logs for the moments a user says this is wrong so the missing context can be saved and reused. Memory, hooks, skills, registries -- all just delivery mechanisms for the same underlying thing.
Patrick's number one piece of advice if you are starting today is brutal in its simplicity. When the agent does the wrong thing, write it down in your AGENTS.md or claude.md. Do not just re-prompt and move on. Build the context file. That is the new job. Code moved to context. Context, eventually, moves to knowledge -- the way your organization actually works, captured somewhere an agent can use it. Whoever owns that layer wins. The model does not.
Patrick's contact information:
LinkedIn: https://www.linkedin.com/in/patrickdebois/
X: https://x.com/patrickdebois
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
349: Every platform you already own is about to have AI baked into it. Not next year. This year. That is Ben Wilcox's blunt prediction, and Ben is the CTO and CISO at ProArch, so when he says shadow AI is going to make shadow IT look quaint, it is worth slowing down to figure out what that actually means. The data leaves your stack through tools you already paid for, through features the vendor shipped without asking, through copilot agents nobody filed a ticket for.
Here is the uncomfortable part. This is not a new problem. It is the exact same retroactive-security failure pattern that broke DevSecOps, just with higher stakes and a faster clock. A pen test done six months ago is already obsolete because the app added AI in the meantime. Models get deprecated on seven-month windows while frameworks still get years of support. The whole "we will deal with it at the end" approach that worked badly for cloud and worked worse for containers is going to be catastrophic for AI.
The fix is older than the problem. Landing zones. Well-architected frameworks. A storage account that already has the right policy. An API gateway already in front of the API. The developer should not be picking from twenty checkboxes to figure out which combination is secure -- that decision should already be made before the ticket lands. Stop forcing developers onto the security team. Stop running security reviews while the head developer sweats through his shirt right before release. Build the foundation up front and let the developer deploy into it.
Then the harder question. The leaders making these calls today are the same engineers who lived through every prior cycle of this exact pain. Why are they letting another generation eat it again? Viktor's answer is one line: "It's my time now, baby." Ben does not disagree. PE pressure, VC timelines, race-to-market everything -- the budget exists, the tools exist, the patterns exist. What is missing is the will to invest two weeks up front so the last two months do not turn into panic. Ben's practical advice for any leader dipping a toe in: do not do it alone, inventory everything, talk to sales and finance and the developers, and assume the conversation you are having today will be obsolete in six months.
Ben's contact information:
LinkedIn: https://www.linkedin.com/in/ben-wilcox/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
Something flipped this year. Chatbots were a toy. Useful sometimes, but a toy. Agents are not. Agents take actions, hold credentials, write code, move Kanban cards, and run on cron schedules. The window between "this is interesting" and "this is existential" has closed faster than cloud, faster than Kubernetes, faster than any prior shift.
Viktor's read is blunt. One person can now build a bigger business than most mid-size companies have ever managed. That is not hyperbole -- that is a description of what is already happening with a handful of solo-built projects shipping in weeks what used to take a hundred-person org years. The thesis: panic. Not because the sky is falling, but because larger companies cannot turn around overnight, and the gap between the people who get this and the people who are still scheduling meetings about scheduling meetings is widening every week.
The conversation walks through what each big provider is actually doing. AWS is not pretending to compete on models -- they want the inference revenue. Microsoft is lost in Copilot button-stuffing. Google is quietly winning on three layers at once: TPUs, models, and inference infrastructure. Anthropic is on the path to becoming the next defining IPO, while OpenAI looks like a place to take money out of, not put more in. The Linux Foundation's new Agentic AI foundation got Anthropic's MCP, Block's Goose, and OpenAI's AGENTS.md spec. Viktor's reaction: those are heavy hitters donating not very much.
Then it gets practical. Vendor-provided agents are like hiring a genius engineer who knows nothing about your company. Public skills are mostly nonsense -- if it is in public training data, the model already knows it; what is missing is everything specific to you, which is exactly what no public skill can provide. OWASP just published an Agentic AI Top 10 and most of it is least-privilege rebranded for agents. The cost story is also not what the marketing says: a 00 monthly subscription will not last a day for anyone working full-time with agents. There is a true story in here about a leaked token that turned a 00 monthly spend into 5,000 in two days.
The hardest part of the episode is the part nobody likes hearing. If your output stays the same in 2026, you are in trouble. If you multiply your output, you are fine. Companies have always wanted to do more than they could afford to do. Now they can. The middle is where careers used to live. The middle is where the cuts are going.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
347: Andrei Kvapil has been around Kubernetes since the early days. Contributor to Cilium, Kubevirt, and a handful of other projects you probably use without realizing it. He is also the maintainer of Cozystack, a CNCF sandbox project, and the CEO of Aenix, the company behind it.
The thesis: Kubernetes should be boring. Not exciting, not cutting-edge, not the thing everyone argues about. Boring like the Linux kernel is boring. Something that sits underneath everything and nobody needs to think about. Viktor takes it one step further and says it should be invisible -- developers should never need to know Kubernetes exists, any more than they need to know what kernel their laptop is running.
Cozystack is Andrei's answer to a specific problem. ISPs, banks, finops shops, anyone in Europe who cannot or will not put their data in AWS -- they all want to offer managed databases, managed Kubernetes, object storage, the whole stack. Building that from scratch is hard. Running OpenStack requires a dedicated team that does nothing but tune networking. Cozystack bundles the pieces (Kubevirt, CloudNative Postgres, Cilium, etc) into one product with an aggregation API layer on top of Kubernetes itself. Helm becomes the extension language. The platform becomes a product.
Then the conversation takes a turn. Andrei is the CEO of a bootstrapped company and he says flatly that without AI the company would not exist. Claude Code is moving Kanban cards. Clients send files generated by their AI agent and Aenix feeds those files to their AI agent to generate the response. Andrei's only wish is for this middle step -- him -- to stop existing. Let the agents talk to each other and call him when something actually matters.
There is a hiring question in here too. If the next generation of engineers starts their career with AI on the first commit, do they ever build the mental model that lets them guide the agent when it goes wrong? Andrei thinks you still need deep understanding for anything serious. Viktor agrees. Speed versus quality is still a choice, and juniors who skip the "write it three times until it stops being garbage" phase are going to feel that gap eventually.
Andrei's contact information:
LinkedIn: https://www.linkedin.com/in/kvaps/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
346: Drive-by PRs, AI slop, maintainers burning out -- the open source world is having a meltdown and everyone wants to blame the robots. Viktor isn't buying it.
The real problem started long before AI. Contributing to most open source projects has always depended on tribal knowledge and obscure docs nobody reads. AI didn't break that. It exposed it. When contributions were trickling in, you could get away with onboarding people via vibes. Now that contributions are a firehose, you can't.
Viktor's take cuts in a direction that will annoy a lot of maintainers: your primary job is empowering contributors, not gatekeeping. And if a 20,000-line PR is drowning you, the answer isn't to block everybody. The answer is to change the whole review cycle -- because yesterday you were complaining about not enough contributions and today you're complaining about too many. That's a great problem to have. Solve it.
Here's the part that will upset people. Viktor reframes what a developer's job actually is. If you think your role is typing on a keyboard, you're going to be disappointed. Your role is becoming a product manager. Asking the agent did you look at this, are you sure, what about that. Your job is no more. You just didn't receive the memo.
There's also a thread running through the episode about auditing. Can you actually assess the health of an open source dependency you depend on? Viktor dares Darin to audit Kubernetes. Or curl. Or anything. Humans can't do it at all. AI can -- imperfectly, but better than nothing. Which means the old enterprise model (pay Red Hat, they'll handle it) starts to wobble when the value of someone else handling it drops because the tools can handle it for you.
And there's a prediction. Right now when you ask AI to build something, it picks libraries based on training data. But what happens when the agent actually goes shopping -- analyzing projects, reading docs, deciding which dependencies to pull in? That changes the open source landscape in a way nobody is ready for.
The episode ends somewhere quieter. Contributors, human or AI, should be cherished and trained over time. The hostility toward AI contributions is coming from maintainers who forgot that investing in new contributors is the job. The tools will make a mess. Then they will make less of a mess. Eventually we will be arguing about whether the feature should exist at all -- not whether the code compiles.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
345: Vibe coding works fine until your project gets complicated. That's the gap Amit Patel and his team at AWS built Kiro to fill. The tool launched with about six people in mid-2024, hit GA around October 2025, and the team still fits in a single room -- maybe a seven-pizza team by Darin's math.
The core idea is spec-driven development, but not the kind where business analysts disappear for five years and come back with a document nobody needs anymore. Amit's version: you tell the agent what you want in a chat prompt, it writes the spec for you, and you iterate on it. Twenty minutes of back and forth and you've got requirements, a design, and a task breakdown. Then the agent executes. Two to three days later, working software.
Here's where it gets interesting. Amit frames the human role as bookends. At the front, you define intent -- what needs to exist and why. At the back, you verify that what got built actually matches. Everything in the middle? That's where the tooling lives. And that middle is getting wider every month as agents run longer, handle more turns, and start working in parallel.
But the gap between 'I can build it' and 'I built it right' is real. Amit's S3 example nails it. Ask an LLM to build a file upload app and you'll get one that works. Encryption at rest, encryption in transit, KMS, bucket policies -- none of that shows up unless you know to ask for it. The LLM will generate all of it on request. It just won't volunteer it. That's the experience gap, and it's why junior developers still need to become senior developers the old-fashioned way.
One story that landed: a product manager on Amit's team used Kiro to go from conversation to working prototype overnight. Not a wireframe. Not a doc. A demo the engineering team could put into production. The roles aren't disappearing -- they're getting more fluid. The value was never in the writing. It was always in knowing what needed to be built.
Kiro is now widely adopted inside AWS, with both an IDE and a CLI. Where it's headed next: agents that run in the background, handle multiple tasks at once, and get verified with formal methods instead of just hoping the output is right. But Amit's honest about the limits -- steering file adherence is, in his words, an art in itself. Non-deterministic LLMs will ignore your rules sometimes. Just like humans.
Amit's contact information:
LinkedIn: https://www.linkedin.com/in/amit-patel-040453/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
344: Kubernetes is boring now. That's the whole point. KubeCon EU 2026 in Amsterdam -- likely the biggest KubeCon ever at more than 13,000 attendees -- made one thing extremely clear: the container orchestrator is done being interesting on its own. Every keynote, every new sandbox project, every vendor announcement pointed the same direction. AI. Inference. Agents.
NVIDIA donated a DRA driver for GPUs to CNCF. Google open-sourced their cluster autoscaler and shipped a DRA driver for TPUs. Red Hat brought LLM-D for disaggregated inference. NVIDIA contributed the KAI Scheduler for AI workloads. The Gateway API now has an inference extension in beta -- model routing baked directly into the Kubernetes networking layer. And here's the thing Whitney pointed out that should make everyone pause: you can't even run inference workloads in containers. They can escape. You need micro VMs. So the container orchestrator is orchestrating things that aren't containers.
The platform engineering conversation shifted too. The bottleneck isn't technology anymore -- it's culture. Getting teams to work together differently. And if your company can't trust its own employees to make decisions, good luck trusting agents. Viktor's take on the determinism objection was blunt: agents aren't deterministic, but neither are you. You just think you are.
One thread that kept surfacing: agents as first-class platform users. Not agents doing agent things -- agents as the users your platform serves. Viktor sees it in real time -- pull requests created by agents, reviewed by his Claude, responses written by the submitter's agent. Humans aren't even in the conversation anymore.
The new CNCF sandbox projects tell the story too. LLM-D, KAI Scheduler, Higress (AI-native gateway). And then Velero -- the Kubernetes backup tool that everyone assumed was already CNCF -- finally donated by Broadcom. Which raises a fair question: is CNCF becoming a dumping ground for projects companies don't want to maintain? Probably some of both.
Viktor compared the current state to the first five years of Kubernetes -- everyone focused on low-level components, trying to figure out how to combine 57 different tools. The next wave will be higher-level platforms that bundle all of it. And somewhere underneath it all, the mainframe keeps running. Viktor's bet: it'll outlive AI.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact
343: Here's the thing about your company's APIs -- they were built for your own engineers to use inside your own software. Nobody designed them to be the front door. But that's exactly what's happening. Matt DeBergalis, CEO of Apollo GraphQL, makes a pretty compelling case that AI agents are turning internal APIs into the actual interface between companies and customers. Not the website. The APIs themselves.
And most of them aren't ready for that. At all.
Think about what happens when you point a model at a typical REST API. GitHub's API returns hundreds of fields for a single repository object. Fine when another service is calling it. But a model? All those extra fields are context you're paying for, and they make the model hallucinate. Matt says you need something between the model and all those backend services -- an orchestration layer that takes one request and handles the mess underneath. That's where GraphQL comes in.
He draws a parallel that'll land immediately if you've been in this space a while. APIs right now are pets -- handwritten, named, carefully managed. But AI-generated code is about to produce way more microservices, which means way more APIs. They're going to become cattle. And just like containers needed Kubernetes, APIs are going to need declarative infrastructure to manage them at scale.
The conversation takes an interesting turn when Darin pushes back on the idea that developers are becoming architects. His take: we're becoming product managers. Matt says both. Viktor throws in code reviewers. Matt's own story backs it up -- he codes more as CEO than he did as CTO, because AI handles the parts he never had time to learn. He doesn't know modern React. Doesn't need to.
One more thing that should make any tech company uncomfortable: if AI agents are how customers find you now, what happens to your docs-page-driven acquisition funnel? Apollo's already made the shift -- their first audience for documentation is the models, not the humans.
Matt's contact information:
LinkedIn: https://www.linkedin.com/in/debergalis/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
342: Most companies have plenty of documentation. The problem is almost none of it is findable, current, or true. Between what's documented, what's actually true, and what people actually do, there are gaps wide enough to kill any AI initiative before it starts.
Viktor makes a distinction that reframes the whole problem: there are two types of documentation. Why something was done -- that's eternal. How something works -- that's outdated the moment someone changes a config and forgets to update the wiki. The information about that change probably exists somewhere -- in a Zoom recording, a Slack thread, somebody's head -- but it's not where anyone would think to look for it.
The running system itself is the most accurate documentation any company has. Your Kubernetes cluster tells you how many pods are running right now. Git tells you how many you wished you had. Those aren't the same thing, and pretending Git is the source of truth is a comfortable lie most teams tell themselves daily.
RAG won't save this. Not the way most people imagine it -- point an agent at your docs and let it answer questions. That fails for the same reason Google's old enterprise search appliance failed. What could work is a continuous process that watches every information source, extracts what matters, and updates a central location intelligently. We have the pieces for this. Nobody's built it yet.
The practical path forward: audit what you have before building anything new. Instrument your documentation the way you instrument applications -- find out what people search for and can't find. Design for retrieval, not storage. Build feedback loops. And stop treating documentation as a project with an end date. The companies that treat this as a strategic advantage instead of a chore are the ones that will actually make AI work for them.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
341: Nobody's arguing about whether you need feature flags in 2026. That debate ended years ago. But the code flowing through those flags? That's a different story. AI is writing more of it than ever, review times are climbing, and delivery throughput has actually declined. Trevor Stuart, co-founder of Split.io and now running Feature Management & Experimentation at Harness, calls it the six-lane highway ending in a two-lane bridge.
The bottleneck didn't disappear. It moved. Coding got faster, but everything downstream -- reviews, security scans, delivery pipelines -- stayed the same width. Viktor points out this is the exact same pattern from the early agile days: his team shipped every two weeks, but testing still took six months. Different era, same structural problem.
Feature flags are part of the fix, but not the way most people use them. Teams are now stuffing prompts, token limits, and temperature settings inside feature flag configurations and running A/B tests on AI agents in production. That's a long way from changing button colors on a marketing page, which is where experimentation started 15 years ago.
The culture problem is harder than the tooling problem. Trevor has watched teams run one experiment, see it fail, and quit experimenting entirely. The fear of admitting failure kills more experimentation programs than bad data ever will. Meanwhile, the companies getting real results -- a fast food chain generating millions from kiosk experiments, a global bank driving hundreds of millions in customer acquisition -- are the ones treating experimentation as a permanent operating model, not a one-off project.
The conversation also covers Trevor's path from co-founding Split to running it inside Harness post-acquisition. He stayed -- which doesn't happen as often as you'd think. Harness runs what he calls a 'startup within a startup' model, and he breaks down what that actually looks like from the inside, what was hardest to let go of, and why finding your 'why' matters more than any exit.
Trevor's contact information:
LinkedIn: https://www.linkedin.com/in/trevorbstuart/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
340: The smartest ops people are often the most likely to resist new technology -- and they're not wrong. If you don't change anything, nothing breaks, and nobody blames you. That's a completely rational choice. It's also the one that guarantees you fall behind. Bare metal to VMs, VMs to cloud, cloud to Kubernetes -- every time, the teams that played it safe ended up scrambling to catch up two years later. The safe bet isn't safe. It just feels that way.
It gets worse when you look at where the tools come from. Kubernetes? Built by developers. Terraform? Developers. Containers? Developers. The tools ops teams depend on were made by a different tribe. So the pushback isn't really about whether the tech is ready or whether the risk is too high. It's about identity. 'Not my people' is a harder objection to overcome than 'not ready yet,' because no amount of documentation or proof-of-concepts answers it.
And about proof -- everyone wants it before they'll move. But the proof already exists. It's the tool someone on your team has been running in shadow IT for a year without any official support. If it survived that long on its own, that's stronger evidence than any pilot program. That's your roadmap. And the way in is small chunks, not grand plans. Move one service. Learn something. Adjust. Repeat.
AI in ops follows the exact same pattern. A tool that gets you 50% of the way there for free means you can focus your expertise on the other 50%. That's a win. But the people waiting for AI to be perfect before they'll touch it? They're making the same mistake as the teams that waited for perfect proof before migrating to the cloud. Different decade, same trap.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
339: DNS has been around since the 1980s. Nobody's writing blog posts about how it changed their life. But every single thing on the internet depends on it -- including all those AI tools everyone's excited about.
Anthony Eden has been in the DNS business since the late nineties, when he was CTO of one of the first seven domain registrars after the .com deregulation. In 2010 he started DNSimple, and he did it without a dime of venture capital. Sixteen years later, his 20-person team runs a global DNS infrastructure with 14 edge nodes and 9 origin servers spread across multiple continents.
The conversation covers the mistakes companies make with their domains -- running production DNS on a registrar that was never built for it, sharing logins with no access control, zero documentation on why records exist. Anthony breaks down how DNS actually works at scale (unicast vs anycast, the onion layers of resolvers), why your email deliverability problems are probably a DNS problem, and what the www vs no-www debate looks like in 2026.
On AI tools, Anthony's take is practical. They're giving his engineers more time to think about problems instead of typing out solutions. But he's not buying the vibe coding hype -- when you run critical internet infrastructure, everyone on the team needs to understand the systems they're building. And for AI startups hoping to cash out? Most will fail. The twist you put on somebody else's model won't be a moat. It'll just become a feature for something bigger.
Anthony's contact information: X: https://x.com/aeden Bluesky: https://bsky.app/profile/anthonyeden.bsky.social LinkedIn: https://www.linkedin.com/in/aeden/
YouTube channel: https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/
Slack: https://www.devopsparadox.com/slack/
Connect with us at: https://www.devopsparadox.com/contact/
338: Every company adding AI coding tools runs into the same wall. Developers produce more code, but features don't ship any faster. The bottleneck just slides downstream -- to QA, to security, to legal, to whoever comes next in the pipeline. And the team that got faster? They don't even realize the people upstream could be feeding them more work.
Viktor's take: the fastest possible setup is one person carrying a feature from idea to production. Not one person doing everything alone -- a system designed so nobody waits. Tests run in CI. Deployments happen through Argo CD. Security scanning is automated. There's a real difference between wiring up a light switch and hiring a butler to flip it for you.
None of this is new. The same thing happened with punch cards, client-server, cloud, Kubernetes. One group adopts the new thing, everyone else says it doesn't apply to them, and the market eventually forces their hand. Meanwhile, every team in every company says they'd love to change if only the rest of the organization would get on board. Every team says this. So who's actually blocked?
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
337: Time series databases have become essential infrastructure for the physical AI revolution. As automation extends into manufacturing, autonomous vehicles, and robotics, the demand for high-resolution, low-latency data has shifted from milliseconds to nanoseconds. The difference between a general-purpose database and a specialized time series solution is the difference between a minivan and an F1 car - both will get around the track, but only one is built for the demands of real-time operational workloads.
The open source business model continues to evolve in unexpected ways. While companies like Elastic and Redis have seen hyperscalers fork their projects, a new partnership paradigm is emerging. Amazon Web Services now pays to license InfluxDB and offers it as a managed service, signaling a shift toward collaboration rather than competition. This approach benefits everyone: vendors maintain development velocity, cloud providers get workloads on their platforms, and customers receive better-supported products.
Evan Kaplan, CEO of InfluxData, joins Darin and Viktor to discuss the trajectory from observability metrics to physical world instrumentation, why deterministic models matter more than probabilistic ones when your robot might run over your cat, and what it takes to build a sustainable open source company over a decade-plus journey.
Evan's contact information:
X: https://x.com/evankaplan
LinkedIn: https://www.linkedin.com/in/kaplanevan/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
336: The workplace is on the verge of a transformation as significant as the Industrial Revolution. Just as Bring Your Own Device policies emerged after the iPhone disrupted corporate mobile standards, we are now entering an era where employees may arrive with their own AI teams in tow. The question is no longer whether AI will change hiring and employment - it is how quickly companies will adapt before being left behind by competitors who embrace this shift.
Current AI productivity gains remain largely individual rather than organizational. Writing code twice as fast means nothing if the deployment pipeline stays the same speed. But within five to ten years, entire industries face disruption - from primary care physicians to transportation to knowledge work. Companies clinging to restrictive AI policies today risk driving away top talent who have already integrated these tools into their workflows. The intellectual property implications alone - who owns an AI stack trained on company processes when an employee leaves - will require entirely new frameworks for employment law.
Darin and Viktor explore these scenarios through the lens of a hypothetical job interview where a candidate brings their own team of AI agents. The conversation surfaces uncomfortable questions about compensation models, corporate governance, and whether we are witnessing the emergence of a new kind of talent that blends human expertise with digital capabilities.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
335: Observability tools have exploded in recent years, but most come with a familiar tradeoff: either pay steep cloud vendor markups or spend weeks building custom dashboards from scratch. Coroot takes a different path as a self-hosted, open source observability platform that prioritizes simplicity over flexibility. Using eBPF technology, Coroot automatically instruments applications without requiring code changes or complex configuration, delivering what co-founder Peter Zaitsev calls opinionated observability—a philosophy of less is more that aims to reduce cognitive overload rather than drowning users in endless metrics and dashboards.
The conversation explores how Coroot differentiates itself in a crowded market with over a hundred observability vendors. Rather than competing head-to-head with cloud giants like Datadog and Dynatrace, Coroot focuses on developers who need answers fast without building elaborate monitoring systems. The platform combines systematic root cause analysis with AI-powered recommendations, using deterministic methods to trace how errors propagate through microservices before handing off to LLMs for actionable fix suggestions.
Darin and Viktor dig into Coroot's business model with Peter, examining why the company chose Apache 2.0 licensing instead of more restrictive options, and how staying bootstrapped with minimal angel funding allows them to play the long game without pressure to chase every hype cycle.
Peter's contact information:
X: https://x.com/PeterZaitsev
Bluesky: https://bsky.app/profile/peterzaitsev.bsky.social
LinkedIn: https://www.linkedin.com/in/peterzaitsev/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
334: The debate over whether AI saves developers time misses a fundamental truth: coding was never the hardest part of software development. Writing code is mechanical work - the real challenges have always been understanding problems, designing solutions, communicating with stakeholders, and navigating organizational complexity. AI is now forcing a reckoning with this reality, pushing developers at every level to reconsider what skills actually matter.
The traditional separation between architects who design and developers who implement is breaking down. AI enables a return to something like pair programming, where the person thinking through problems can now work alongside a fast executor without the old bottleneck of slow human typing. This shift means developers need stronger communication skills - the ability to explain technical decisions to non-technical stakeholders and translate business requirements into technical direction. For juniors, the opportunity is unprecedented: you can upskill faster than ever in the history of software, but only if you balance building things with actually understanding how they work.
Darin and Viktor explore what this means for developers at every career stage, from juniors who should focus on fundamentals and end-to-end understanding, to seniors who are becoming more like editors and supervisors of AI-generated work. The developers who will thrive are those who combine real experience with a willingness to embrace change - and that combination has always been the winning formula.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
333: Pete Hunt, CEO of Dagster and early React team member, explores the evolution from Facebook's early React development through trust and safety infrastructure at Twitter, to building modern data orchestration tools. The conversation reveals how similar infrastructure problems plague every industry - whether you're launching rockets or managing porta-potties, the core challenges remain consistent: late data, quality issues, and mysterious errors that require both automated solutions and human oversight.
The discussion dives into the technical realities of scaling systems, from the microservices complexity trap to the current AI adoption wave. Hunt shares candid insights about leadership challenges, including how well-intentioned technology recommendations can backfire, and why most data projects fail despite sophisticated multi-agent orchestration. The conversation touches on career advancement pressures that drive unnecessary complexity and the importance of focusing on actual user adoption rather than technical sophistication.
This episode features Pete Hunt in conversation with hosts Darin and Viktor, covering everything from regular expression nightmares to the future of data infrastructure and the lessons learned from building products that people actually use.
Pete's contact information:
X: https://x.com/floydophone
LinkedIn: https://www.linkedin.com/in/pwhunt/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
332: AI adoption in enterprise software development is accelerating, but operations teams are lagging behind. While application developers embrace AI tools at a rapid pace, those on the ops side remain skeptical—citing concerns about determinism, control, and a general resistance to change. This mirrors previous technology waves like containers, cloud, and Kubernetes, where certain groups initially pushed back before eventually adapting. The prediction for 2026: AI will not see widespread adoption in operations despite its growing presence elsewhere in the software lifecycle.
The bigger challenge facing organizations is not just adopting AI but transforming entire processes to take advantage of it. Improving just one piece of the software delivery pipeline—like development speed—only creates bottlenecks elsewhere. Companies cannot hand developers AI tools while keeping everything else the same and expect transformational results. The future points toward a world where experts bring their own AI agents to companies: personal toolsets trained on their experience and best practices that integrate with organizational systems.
Perhaps the most provocative insight centers on the value of writing code itself. The argument: writing code is the easiest and least valuable part of software development. The real cognitive load comes from thinking through requirements, architecture, and design. Developers who simply translate instructions to code without deeper engagement may find themselves in real danger as AI continues to advance. Darin and Viktor explore these predictions and more as they look ahead to what 2026 might bring for DevOps, platform engineering, and the evolving role of developers.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
331: At the end of 2024, predictions were made about what 2025 would bring to the tech industry. A year later, on New Year's Eve, it's time to look back and see what actually happened. The prediction episode from January 1st covered four major topics: rug pulls from companies switching to business source licenses, the rise of WebAssembly adoption, a wave of company acquisitions, and AI becoming embedded in existing tools. Some predictions hit the mark while others missed entirely, but what emerged was something nobody fully anticipated.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
330: In this short episode, Darin and Viktor reflect on the holiday season.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
329: Vibe coding - the practice of casually prompting AI to generate code solutions - has become increasingly popular, but its limitations become apparent when applications need to scale beyond personal use. While AI-assisted development can be powerful for proof of concepts and small internal tools, the transition from vibe-coded solutions to production-ready applications often requires experienced engineers to rebuild from scratch.
The conversation explores three distinct levels of software development: personal tooling, internal applications, and public-facing systems. Each level demands different approaches, with vibe coding being most suitable for the first category but potentially problematic as complexity increases. The analogy of cooking illustrates this well - anyone can make a simple meal, but feeding hundreds of people requires professional expertise and proper infrastructure.
Technical debt in the AI era presents new challenges and opportunities. Traditional software engineering principles like DRY (Don't Repeat Yourself) and clean code practices may matter less when AI can quickly refactor and improve code. The future likely involves hybrid teams where business experts work alongside experienced engineers, with AI agents handling implementation details. Darin and Viktor examine how pair programming is evolving from developer-to-developer collaboration to human-to-AI partnerships, fundamentally changing how software gets built and maintained.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
328: The build versus buy decision isn't as binary as most companies think. Every technology choice involves elements of both - you might use Linux (buy) but still configure and customize it extensively (build). The real question isn't whether to build or buy, but finding the right balance between the two approaches based on your company's resources, size, and unique requirements.
Companies often fall into the trap of thinking their processes are so unique that existing solutions won't work, leading to unnecessary custom development. This "not invented here" syndrome is particularly common in large enterprises that mistake their size for complexity. In reality, most businesses face challenges that have already been solved by others. The key is recognizing when you truly need a custom solution versus when you can adapt existing tools.
The decision becomes more nuanced when considering factors like maintenance costs, compliance requirements, and long-term sustainability. Building internally requires ongoing resources for updates, security patches, and knowledge retention within your team. Meanwhile, buying from vendors shifts much of this burden but introduces dependencies and integration challenges. The conversation features insights from Alex Gusev from Uploadcare, along with perspectives from hosts Darin and Viktor on navigating these complex technology decisions.
Alex's contact information:
X: https://x.com/alxgsv
LinkedIn: https://www.linkedin.com/in/alxgsv/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
327: When AI tools suggest putting glue on pizza, it's a harmless laugh. But when autonomous AI agents start managing your infrastructure, the stakes become much higher. The reality is that current AI technology isn't ready for unsupervised deployment in critical systems, and treating it like it is could lead to catastrophic failures.
The challenge isn't just about AI capabilities—it's about management and oversight. Most developers aren't trained as managers, yet they're being asked to supervise AI agents that need constant guidance and correction. Just like hiring a new employee, AI agents require company-specific knowledge, proper guardrails, and ongoing supervision to be effective. The same principles that apply to managing human workers—code reviews, testing, and performance evaluations—need to be adapted for AI management.
As the ecosystem around AI continues to evolve rapidly, new challenges emerge. From sleeper agents that activate on specific dates to the need for completely new approaches to technical SEO for LLMs, the landscape is changing faster than most organizations can adapt. Darin and Viktor explore these challenges and discuss practical approaches for keeping AI systems from going rogue while maintaining the productivity benefits they can provide.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
326: Microservices architecture has evolved far beyond simple distributed systems, but most development teams are still rebuilding the same foundational patterns over and over again. Mark Fussell, co-founder of Dapr and Diagrid, explains how his team at Microsoft identified this repetitive reinvention problem and created a solution that abstracts away the complexity of service discovery, messaging, state management, and security while providing true cloud portability.
Dapr emerged from Microsoft's Azure incubations team with a clear mission: stop forcing developers to rebuild distributed systems patterns from scratch. The runtime provides standardized APIs for common microservices needs while allowing teams to swap underlying infrastructure components without changing application code. Whether using Kafka, RabbitMQ, Redis, or cloud-native messaging services, developers write against consistent APIs while platform teams maintain control over infrastructure choices.
The conversation covers Dapr's journey from Microsoft internal project to CNCF graduated status, the technical decisions behind its multi-language approach, and how it integrates with existing frameworks like Spring Boot and .NET. Mark also discusses Diagrid's platform play around durable workflows and the emerging role of Dapr in AI agent development. Darin and Viktor explore the practical adoption challenges, the balance between developer productivity and platform engineering concerns, and why experienced developers tend to embrace abstraction layers more readily than those building their first distributed systems.
Mark's contact information:
X: https://x.com/mfussell
LinkedIn: https://www.linkedin.com/in/mfussell/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
325: KubeCon NA 2025 wrapped in Atlanta with unseasonably cold weather and some significant shifts in the cloud native ecosystem. The conference showed fewer vendors backing CNCF projects on the show floor, with key concerns emerging around maintainer burnout—exemplified by NGINX Ingress being deprecated despite running on 40% of Kubernetes clusters worldwide. The event revealed a maturing ecosystem where AI moved from buzzword to operational reality, with focus shifting toward conformance standards, security policies, and enterprise readiness rather than the hype cycle of previous years.
The discussions revealed a consolidation pattern where larger corporations like AWS, Microsoft, and Google are increasingly the only ones who can sustain open source project maintenance. Startups and smaller companies face difficult choices: maintain existing revenue streams, pivot entirely to AI, or attempt both and fail at both. Meanwhile, AI adoption in the ops space remains behind other sectors, with developers emerging as the primary buyers for AI tooling—a shift that's reshaping go-to-market strategies across vendors. Platform engineering continues as a parallel major theme, focusing on operationalizing infrastructure at scale.
Whitney's contact information:
X: https://x.com/wiggitywhitney
LinkedIn: https://www.linkedin.com/in/whitneylee/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
324: Kubernetes has reached a mature state where boring releases signal stability rather than stagnation. While the platform continues evolving with features like in-place resource updates in version 1.33, the real challenge lies in optimizing AI workloads that demand significantly more resources than traditional applications. The discussion reveals how auto-scaling capabilities become crucial for managing these resource-intensive workloads, with vertical and horizontal scaling finally working together through new features that allow pod resizing without restarts.
The conversation explores the ongoing tension between cloud costs and data center investments, particularly as companies navigate uncertain AI requirements. While cloud providers offer flexibility for experimentation, the hidden costs of skilled personnel and infrastructure management often make cloud solutions more economical than initially apparent. The debate extends to startup strategies, where outsourcing infrastructure complexity allows teams to focus on core business value rather than operational overhead.
Omer Hamerman joins Darin and Viktor to examine the common misconceptions about resource allocation, arguing that developers fundamentally cannot predict CPU and memory requirements accurately. This limitation makes automated right-sizing and intelligent scaling essential for modern Kubernetes deployments, especially as AI workloads continue pushing infrastructure boundaries.
Omer's contact information:
LinkedIn: https://www.linkedin.com/in/omer-hamerman/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
323: Vibe coding - the practice of giving AI a high-level description and letting it build applications unsupervised - has become increasingly popular among non-developers looking to quickly prototype ideas. While this approach excels at rapid prototyping and getting small, focused applications running, it creates significant security risks when deployed to production without proper oversight. The fundamental issue isn't with AI capabilities, but with treating any tool - whether AI or human - as capable of understanding company context, security requirements, and production standards on day one.
The real value emerges when vibe coding serves as a bridge between business requirements and technical implementation. Rather than replacing traditional development workflows, it can accelerate the initial phases by providing working prototypes that stakeholders can interact with before formal development begins. However, moving from prototype to production requires the same rigorous processes that any new technology integration demands: security scanning, code review, compliance with company policies, and proper authentication handling.
In this episode, Darin and Viktor explore the security implications of unsupervised AI development, discussing when vibe coding makes sense, where it falls short, and how organizations might eventually integrate AI-assisted development into their existing workflows while maintaining security and operational standards.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
322: Peer-to-peer technology represents a fundamental shift in how we think about data sovereignty and application architecture. Rather than relying on centralized servers and trusting specific endpoints, peer-to-peer systems allow users to verify data authenticity regardless of its source. This approach eliminates the traditional point-to-point communication model where data flows from a specific server to your device, instead creating networks where any peer can help distribute content while maintaining cryptographic verification.
The technology offers compelling advantages for developers and users alike. Applications built on peer-to-peer foundations can operate without ongoing infrastructure costs, scale naturally as more users join the network, and continue functioning even if the original company disappears. Development becomes simpler in many ways since everything runs locally by default, eliminating complex database configurations and external dependencies. However, challenges remain around debugging distributed systems, ensuring data persistence in small networks, and adapting traditional development workflows to this new paradigm.
In this episode, Darin and Viktor explore these concepts with Mathias Buus Madsen, co-founder of Holepunch and creator of the Pear Runtime. Mathias shares insights from building real peer-to-peer applications, including their chat app Keet, and explains how developers can start experimenting with this technology today.
Mathias' contact information:
LinkedIn: https://www.linkedin.com/in/mathiasbuus/
X: https://x.com/mafintosh
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
321: Model Context Protocol (MCP) represents a fundamental shift in how AI agents interact with tools and systems. Rather than forcing models to guess the best approach for tasks like creating AWS resources, MCP provides structured context that guides agents toward organization-specific workflows and tools. The protocol serves as an API for agents, allowing them to understand not just what you want to accomplish, but how your company prefers to accomplish it.
The real power of MCP emerges when it moves beyond simple tool mirroring to intent-based architecture. Instead of just wrapping existing command-line tools, effective MCP servers understand higher-level intents like deploying an application or finishing development work, then orchestrate complex workflows that align with company policies and best practices. This approach transforms AI agents from generic assistants into context-aware collaborators that understand your specific environment and constraints.
The rapid adoption of MCP across the industry signals something significant about the current state of AI tooling. While technical challenges around authentication, remote deployment, and stateful conversations remain unsolved, the protocol has achieved unprecedented adoption speed because it addresses a critical need for standardization in the agent ecosystem. In this episode, Darin and Viktor explore both the transformative potential and current limitations of this emerging standard.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
320: In this episode, Darin and Viktor are joined by Jim Hirschauer, Head of Product Marketing at Xurrent, for a deep dive into the realities of incident management in today's complex IT environments. While dashboards and monitoring tools have become ubiquitous in operations centers, the panel discusses why these visualizations alone often fall short when it comes to actually resolving incidents.
Drawing on decades of experience, they share stories of war rooms, recurring outages, and the persistent challenges that technology alone can't solve. The conversation highlights the critical role of human expertise, communication, and organizational culture in bridging the gap between raw data and effective action.
Whether you're an IT leader, SRE, or anyone responsible for uptime, this episode offers practical insights into what it really takes to keep systems running smoothly.
Jim's contact information:
LinkedIn: https://www.linkedin.com/in/j-hirsch/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
319: The AI infrastructure landscape is evolving rapidly, but the gap between marketing hype and practical reality remains significant. While vendors promise revolutionary changes with each new model release, the true challenge lies not in accessing more powerful AI tools, but in developing the organizational workflows and individual expertise needed to use them effectively. Most people claiming AI proficiency are barely scratching the surface, lacking experience with prompt engineering, vector databases, and custom agent development.
The future points toward increased specialization, moving beyond general-purpose models toward AI systems optimized for specific domains like infrastructure management, database security, and application development. This shift mirrors the historical progression from local spreadsheets to enterprise databases, but compressed into a much shorter timeframe. Organizations will need to invest heavily in secure, scalable infrastructure to support company-wide AI adoption, while individuals must start building their own agents now - these custom tools will likely become the new resume for technical professionals.
Infrastructure requirements are shifting dramatically toward a dumb terminal model where local computing power becomes less relevant than access to cloud-based AI services. The conversation between Darin and Viktor reveals that while $200 monthly AI subscriptions might seem expensive for individuals, they represent remarkable value for organizations when measured against productivity gains - essentially the cost of two cups of coffee per employee per day.
DevOps AI Toolkit
https://github.com/vfarcic/dot-ai
AI Meets Kubernetes: Simplifying Developer and Ops Collaboration
https://youtu.be/8Yzn-9qQpQI
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
318: In this episode, we explore how AI is fundamentally reshaping the world of API development and testing with Tom Akehurst, CTO & Co-founder at WireMock. As AI agents become more prevalent in software development, the tools and practices around API design, testing, and maintenance are evolving rapidly. Tom shares insights on how WireMock is adapting to this new landscape and what it means for developers and organizations building distributed systems.
Tom's contact information
X: https://x.com/TomAkehurst LinkedIn:
https://www.linkedin.com/in/tomakehurst/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
317: The often-overlooked human impact of AI's rapid advancement is creating unprecedented disruption across industries. Unlike previous technological shifts that affected one profession at a time, AI is poised to disrupt multiple sectors simultaneously, creating unprecedented challenges for workers, companies, and society. This episode covers why junior positions are already being eliminated, how domain knowledge becomes more valuable than coding skills, and why the transition from implementation work to oversight and strategy roles is inevitable.
Companies have dramatically less time to adapt than with previous technologies - moving from 10-year adoption cycles for cloud computing to just 1-2 years for AI. While the short-term disruption will be significant, the long-term outlook suggests transformation rather than elimination of jobs, similar to how agricultural mechanization created new opportunities while changing the nature of work.
Join Darin and Viktor for a discussion about navigating the biggest technological shift in recent history, with practical insights on preserving human value in an AI-driven workplace and strategies for both individuals and organizations to thrive during this critical transition period.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
316: In this episode, Darin and Viktor speak with Avery Pennarun, CEO at Tailscale, on the evolving technology landscape, specifically focusing on the challenges and advancements in VPNs and connectivity. Avery discusses the limitations of traditional VPNs, the advantages of Tailscale's unique approach to creating a secure virtual network, and the importance of maintaining a stable computing platform without compromising security. The episode delves into the historical context of networking, the philosophy behind Tailscale, its open-source client software, and detailed discussions on network security, trust issues, and the future of internet connectivity. This episode is a thought-provoking journey through the current state and the aspirational improvements in network technology and security.
Avery's contact information:
X: https://x.com/apenwarr
LinkedIn: https://www.linkedin.com/in/apenwarr/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
315: In this episode, the discussion centers around the critical importance of design over mere code writing in software development. The hosts reflect on their experience with coding tools like Cursor and Claude Code, noting their pros, cons, and the efficiency brought by AI in handling coding chores. They highlight the paradigm shift in developer tasks from writing code to managing and designing projects, comparing it to the role of an author in world-building. The conversation also touches on the potential future of startups leveraging AI to minimize costs, the iterative nature of design, and practical tips for integrating AI into development workflows effectively.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
314: Geoffrey Huck joins Darin and Viktor to discuss the ins and outs of building a speaking career, starting from small meetups and leading up to major conferences. He shares his personal experiences, tips on overcoming fear of public speaking, and the importance of community engagement in the developer industry. Geoffrey emphasizes the need to keep slides minimal and engaging, and highlights the benefits of starting with small presentations to gradually build confidence. He also explores techniques for initiating conversations, handling stage fright, and continuously improving speaking skills. Whether you're an introvert or an extrovert, this episode provides actionable advice for anyone looking to enhance their public speaking abilities.
Geoffrey's contact information:
LinkedIn: https://www.linkedin.com/in/geoffrey-huck/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
313: In this episode, Darin shares his recent experiences using AI tools Cursor and Claude Code to improve and refactor Jenkins plugins. After receiving a recommendation to try out Cursor for code improvements, he tests it alongside Claude Code, comparing their functionalities and effectiveness. He describes his process and observations, noting that both tools helped identify performance improvements in the code. While Cursor provided quick initial feedback, Claude Code offered a slightly better quality of suggestions but required nudging to get accurate results. Darin also mentions the practicality of integrating these tools with his existing setups and the importance of having issues documented for better management. Moreover, he discusses the benefits of AI-assisted PR descriptions and emphasizes the need for caution when using such tools for proprietary code without corporate approval. Overall, he concludes that transitioning to these advanced AI tools can significantly improve productivity in open-source projects.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
312: In this episode, the discussion focuses on the complexities and strategic considerations of migrating from VMWare to platforms like KubeVirt and OpenStack. Kevin Jackson, Director of Product Management at Trilio, joins the discussion to share insights on the challenges, benefits, and operational implications of such migrations. Topics include the intricacies of managing virtualization and cloud environments, the potential pitfalls and cost implications, and the importance of understanding existing applications before making a switch. Kevin highlights the significance of thorough research, involving partners, and the concept of lift and shift during migrations. The session also touches on the evolving role of Kubernetes in managing both applications and infrastructure, and the potential for KubeVirt to serve as a transitional technology.
Kevin's contact information:
LinkedIn: https://www.linkedin.com/in/linuxkev/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
311: In this episode, Viktor and Darin delve into the transformative impact of AI on project development. Viktor discusses how AI tools like Claude Code and Taskmaster have significantly reduced the time required for project development, bringing it down from a month to just a few days. They explore the components of AI-driven development, such as LLMs, agents, and MCP servers, and the roles they play. Viktor shares his personal experiences with AI, including the use of Taskmaster for generating comprehensive PRDs, and how tools like memory MCPs have enhanced productivity. They also touch on the practicality and affordability of AI tools, and the transition from traditional programming to AI-assisted development. The discussion provides insights into the future of AI in everyday coding tasks and project management.
Claude Code
https://www.anthropic.com/claude-code
Cursor
https://cursor.com/
Taskmaster
https://www.task-master.dev/
Memory MCP
https://github.com/modelcontextprotocol/servers/tree/main/src/memory
OpenRouter
https://openrouter.ai/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
310: In this episode, Darin and Viktor sit down with Tim Beattie, co-founder and CEO of Stellafai, to chat about the myths and realities of DevOps and Agile in today's workplaces. They dive into how DevOps and Agile should be seen more as philosophies rather than just titles on a business card. Tim shares his take on why roles like DevOps Engineer can actually create more silos and how the real goal should be about breaking down those barriers. They also talk about the crucial role of leadership in fostering a safe environment where teams can speak up and innovate. With references to aerospace and software industries, they show how adaptive practices are super important for staying relevant.
Tim's contact information:
LinkedIn: https://www.linkedin.com/in/tdbeattie/
X: https://x.com/timbeattie
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
309: In this episode, Darin and Viktor discuss their personal experiences and insights related to the rapid advancements in AI technology, particularly focused on AI agents like GitHub Copilot, Cursor, and Claude Code. They examine the paradigm shift in development practices due to these technologies, providing a critical evaluation of their effectiveness and efficiency. The conversation delves into the role of agents, how they operate alongside large language models (LLMs), and the intricacies of context management. They also reflect on the challenges and benefits of restarting projects when they veer off course, emphasizing the impact of AI in such scenarios. Additionally, they address the hurdles and considerations for integrating and managing multiple AI tools and agents in a development environment. This episode sets the stage for future discussions on how developers can adapt to and leverage these evolving AI tools effectively.
Gartner Predicts Over 40% of Agentic AI Projects Will Be Canceled by End of 2027
https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
308: In this episode, hosts Darin and Viktor are joined by guest Ricardo Castro to delve into the complexities and misconceptions surrounding Continuous Integration (CI) and Continuous Deployment (CD). The discussion begins with Ricardo's insights from a previous talk on the overestimation of automated systems in CI/CD and transitions into a broader conversation about the true essence of CI/CD practices. Key points include the critical distinctions between CI and CD, the importance of small batch deployments, the role of automation in scaling these processes, and the vital connection between CI/CD and business needs. The episode also touches on the contributions to open source projects and the need for balancing automation with risk management, ultimately questioning whether CI/CD can ever be truly solved.
Ricardo's contact information:
LinkedIn: https://www.linkedin.com/in/mccricardo/
X: https://x.com/mccricardo
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
307: In this episode, Darin and Viktor discuss a blog post from Fairwinds about Kubernetes in 2025. Key topics include the ongoing rise in Kubernetes and Docker adoption, the future of container use, Kubernetes use cases, developer sentiment towards Kubernetes, and predictions on container management, multi-cloud strategies, and the role of AI in DevOps. They also touch on the importance of resource optimization over purely cost optimization and the expected consolidation of Kubernetes clusters for better efficiency. The discussion offers a perspective on the Fairwinds predictions, with a particular focus on the practical aspects of Kubernetes deployment and management.
Kubernetes in 2025: Are You Ready For These Top 5 Trends & Predictions?
https://www.fairwinds.com/blog/kubernetes-2025-top-5-trends-predictions
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
306: In this episode of DevOps Paradox, we delve into the role of GraphQL in modern APIs with guest Sophia Willows from Rye. They discuss the pros and cons of using GraphQL versus REST and gRPC, highlighting the efficiencies and complexities each brings to API development, especially in developer tools. They tackle common misconceptions and usage pitfalls of GraphQL, offering valuable insights into its optimal application. Sophia explains the rationale behind Rye’s choice of GraphQL for public-facing APIs while opting for REST and gRPC for internal microservices, reflecting on the trade-offs between performance and flexibility. The episode also touches on the evolution of API standards and speculations on potential future innovations.
Sophia's contact information:
LinkedIn: https://www.linkedin.com/in/sophia-willows/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
305: In this brief and emotional update, Darin addresses the hiatus in the show following the passing of his wife, Valorie, on March 19th, 2025. He announces that new episodes will resume on July 9th, 2025, and thanks the audience for their patience and support during this difficult period. Darin also highlights the nonprofit organization Father's House, encouraging listeners to donate in lieu of other support.
Valorie Pope obituary
https://www.dignitymemorial.com/obituaries/frisco-tx/valorie-pope-12293410
Val's Celebration of Life service
https://www.youtube.com/live/lWPV7QP8Aqs
Father's House Ghana
https://www.fathershouseghana.org/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
304: As we continue to navigate the complexities of modern work environments, the debate surrounding remote work versus in-office setups remains a hot topic. Companies are constantly reevaluating their strategies when it comes to talent retention, with the return to office being a significant point of discussion.
On one hand, working in an office provides the opportunity for direct human interaction. This option can be particularly beneficial for those who are younger or new to the field, as they can directly learn and collaborate with their colleagues. Furthermore, for some individuals, an office environment provides the structure and engagement they need, preventing feelings of isolation that sometimes accompany remote work.
In this episode, Darin and Viktor tackle what it take to retain top talent in 2025.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
303: In today's digital realm, command-line interfaces (CLI) are lifelines for developers, embodying the efficiency and power required to manage complex tasks.
The goal in designing a CLI is not to overwhelm users with command intricacies but to allow them to navigate operations seamlessly and intuitively.
In this episode, we speak with Wesley Beary, a founding engineer at Anchor, about their journey of developing a robust CLI for their product.
Wesley's contact information:
LinkedIn: https://www.linkedin.com/in/geemus/
Developing CLIs: How Anchor developed a CLI and the tools that helped along the way
https://anchor.dev/blog/developing-clis
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
302: As individuals, engineers may feel that the day-to-day tasks and projects they undertake are not life-changing. After all, if an engineer has an off day, it doesn't mean they're suddenly out of the job market. However, when we look at the larger picture from a business standpoint, the stakes are significantly higher.
Companies that choose to ignore or delay engaging with emerging technologies might find themselves in precarious positions. The necessity of stepping out of the comfort zones to experiment and innovate is more important now than ever before. The failure to at least explore new avenues could mean missing the opportunity to adapt when the market demands change.
In this episode, Darin and Viktor discuss while changes, like AI, might not impact your business today, when they do take place, the effects can be sudden, leaving little time for a reactive strategy.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
301: How many applications are in your organization that need to be kept up to date? More than likely, that number is every application needs to be kept up to date, if for no other reason than to keep your security teams happy. It gets even worse if you have 10s, 100s or even 1000s of applications. How do you make this manageable?
In this episode, we sit down with Jonathan Schneider from Moderne to discuss OpenRewrite, a large-scale software refactoring solution. Jonathan explains how OpenRewrite assists in application modernization, security vulnerability repair, and code quality improvements.
Jonathan's contact information:
X: https://x.com/jon_k_schneider
LinkedIn: https://www.linkedin.com/in/jonkschneider/
Code Remix Summit
https://coderemix.ai/
Use the code MODERNE3VIP for an additional $300 off
Strategy Letter V
https://www.joelonsoftware.com/2002/06/12/strategy-letter-v/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
300: Innovation and technology are constantly shifting the landscape of various industries, and the rise of AI is no exception. The term "AI Native Engineer" is becoming more prevalent. This shift denotes not just an evolution in the technological tools at our disposal but a transformation in how engineers engage with these tools to enhance productivity and innovation.
In this episode, our friend Patrick Debois joins us to talk about what he has been doing over the past year with AI.
Patrick's contact information:
X (Formerly Twitter): https://x.com/patrickdebois
LinkedIn: https://www.linkedin.com/in/patrickdebois/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
299: The ability to efficiently manage and analyze data is crucial in today's rapidly evolving tech landscape. One innovative solution that addresses this need is ModelKit. ModelKits are built on existing standards, ensuring compatibility with the tools your data scientists and developers already use.
In this episode, Darin and Viktor speak with Gorkem Ercan, CTO at Jozu, about KitOps, the open source DevOps project built to standardize packaging, reproduction, deployment, and tracking of AI / ML models, so it can be run anywhere, just like application code.
Gorkem's contact information:
X (Formerly Twitter): https://x.com/GorkemErcan
LinkedIn: https://www.linkedin.com/in/gorkemercan/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
298: Throughout numerous conferences, experts have often proclaimed that choosing the right culture is paramount over the selection of tools. However, it’s an oversimplification to deem one right over the other. Tools and culture share a symbiotic relationship, each influencing and reshaping the other.
In this episode, Darin and Viktor try to settle this debate.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
297: In today's digital landscape, ensuring secure and efficient access to systems is crucial. Authorization plays a vital role in granting the right access levels — but how can businesses implement it effectively?
In this episode, we speak with Alex Olivier, co-founder & CPO at Cerbos, about how Cerbos presents an adaptable solution that streamlines access control and governance by externalizing authorization logic and focusing on policy-driven management.
Alex's contact information:
LinkedIn: https://www.linkedin.com/in/alexolivier/
X (Formerly Twitter): https://x.com/alexolivier
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
296: As we step into 2025, the tech landscape is marked by a myriad of opportunities and challenges, with artificial intelligence taking center stage. While AI is firmly entrenched in our daily lives, other technological advances and industry trends also demand our attention.
In this episode, Darin and Viktor make their tech predictions for 2025.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
295: Merry Christmas from the entire team, and thank you for making us a part of your year!
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
294: Here we are at the end of 2024. Darin and Viktor look back at the predictions they made back in episode 244.
Let's see how they did.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
293: As we edge closer to the end of 2024, companies grapple with the complexities of workforce retention and attraction. Companies must navigate post-COVID realities and adjust to altered market conditions. The enduring quest for stability in these uncertain times shapes employee priorities as they seek job security amidst market volatility.
In this episode, we speak with Michael Zuercher, CEO and co-founder of Prismatic, about the challenges and opportunities businesses must address while trying to attract and retain talent.
Michael's contact information:
LinkedIn: https://www.linkedin.com/in/michael-zuercher/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
292: Open source software has become an integral part of the modern digital landscape. It's often celebrated for its free access and collaborative ethos, contributing to rapid technological advancement.
However, the reality of open source is more complex, involving issues of ownership, licensing, corporate influence, and the role of foundations.
In this episode, Darin and Viktor discuss the moral and strategic dimensions of licensing and contributions to open source software.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
291: As we approach the end of 2024, a recurring theme in the tech industry is the impact of AI on software jobs. While some fear mass job displacement, others see an opportunity for unprecedented innovation.
In some respects, it appears that the job market is experiencing shifts reminiscent of the Industrial Revolution. However, unlike the fear of robots taking over in sci-fi narratives like The Terminator, current concerns are rooted in AI automating roles traditionally held by humans.
In this episode, we talk with Derek Ferguson, Chief Software Officer for the Fitch Group, about how new technologies historically create demand for new skills and roles, suggesting that AI may similarly open doors rather than close them.
Derek's contact information:
LinkedIn: https://www.linkedin.com/in/derekmferguson/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
290: Darin catches up with Viktor and Whitney Lee just minutes after they've finished up at KubeCon NA 2024. We discuss the good things and bad things that they experienced while in Salt Lake City.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
289: For startups, navigating the dilemma of cloud selection is critical. While major providers offer incentives and familiarity, stepping out of the conventional path to explore other providers or even setting up specialized solutions can lead to significant cost savings and tailor-made optimizations. The balance is in understanding when to scale with commercial offerings and when to embark on more customized, potentially costlier ventures.
In this episode, we talk with Hugo Santos, CEO at Namespace Labs, about how by optimizing for specific use cases, they have identified a niche where they can outperform hyperscalers. However, this path is complex and not always practical for every company, especially those lacking the necessary infrastructure expertise.
Hugo's contact information:
X (Formerly Twitter): https://x.com/20thr
LinkedIn: https://www.linkedin.com/in/hugomgsantos/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
288: Let's journey back in time, roughly 30 to 50 years ago, to an era where systems were relatively simple. These foundational systems were built with fewer components, making them not only easier to understand but also simpler to manage. At that time, the stability of a system was often directly correlated with its simplicity. Fewer variables meant fewer potential points of failure, and system operators could focus on optimizing the core elements. The mantra of the day was straightforwardness and robust design.
Fast forward to the present, and we find ourselves surrounded by systems that are more interconnected and interdependent than ever before. While each individual component or subsystem might be meticulously engineered and robust by today's standards, the sheer volume and interconnectedness introduce a new layer of complexity. However, this is not a detriment to technological progress, but rather a testament to our boundless ambition and innovation.
In this episode, Darin and Viktor discuss an article from 44 years ago titled Programs, Life Cycles, and Laws of Software Evolution by Meir Lehman.
Laws of Software Evolution
https://matt-rickard.com/laws-of-program-evolution
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
287: In the world of software development, updating dependencies remains a crucial yet often neglected task. Many developers dread the manual labor involved, especially considering potential compatibility issues and the risk of breaking existing functionality.
In this episode, we talk with Rhys Arkins, the creator of Renovate, about the origins of the project and how dependency update automation helps with software development efficiency and security.
Rhys' contact information:
X (Formerly Twitter): https://x.com/rarkins
LinkedIn: https://www.linkedin.com/in/rhys-arkins-5a643a/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
286: Consumers are often enticed by the allure of free services. From email services like Gmail to networking tools like Twingate, the appeal of getting something for nothing is irresistible. But is it truly 'free'?
When taking advantage of free services, one must consider the underlying trade-offs. Using free tools often means contributing personal data in exchange—a model many big tech companies operate upon, particularly for ad-supported services.
In this episode, Darin and Viktor discuss when taking advantage of free services, one must consider the underlying trade-offs.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
285: In the fast-paced world of technology, organizations often find themselves in a complex dance between embracing the latest advancements and grappling with decades-old infrastructure. This delicate balance is highlighted in today's enterprises as they attempt to integrate legacy systems with modern solutions like microservices. The challenges, both technical and organizational, raise critical questions about the future of software development and business strategy.
In this episode, we speak with Neil Millard, author of Confident Contractor, about how enterprises often cycle through waves of consultants every 18-24 months, disrupting continuity and expertise in managing these complex systems.
Neil's contact information:
X (Formerly Twitter): https://x.com/neil_millard
LinkedIn: https://www.linkedin.com/in/neilmillard/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
284: Every step forward is built upon the achievements of the past. When you're developing software, leveraging existing knowledge and improvements can propel your success. Stepping blindly into the vast sea of technological options without understanding the motivations behind their existence can lead to costly missteps.
In this episode, Darin and Viktor discuss when you choose to use someone else's technology, you are inherently choosing to adopt someone else's decisions.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
283: Moving beyond the usual suspects in observability, today's focus shifts towards mobile—a relatively unexplored domain for OpenTelemetry. The integration of OpenTelemetry with mobile applications opens new avenues for mobile app observability.
In this episode, Darin and Viktor talk with Austin Emmons from Embrace about the need for educating developers about the value of instrumentation and how OpenTelemetry can significantly aid in performance monitoring and diagnostic efforts for mobile applications.
Austin's contact information:
LinkedIn: https://www.linkedin.com/in/austin-emmons-264ba347/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
282: In the ever-evolving world of technology, the intricacies of software development and system design continually challenge engineers and developers alike. Insights from past thinkers, such as John Gall, combined with modern-day practices, provide a fascinating lens through which we can understand and navigate these complexities.
In this episode, Darin and Viktor discuss a blog post from Mahesh Balakrishnan titled "Three Laws of Software Complexity (or: why software engineers are always grumpy)"
Three Laws of Software Complexity (or: why software engineers are always grumpy)
https://maheshba.bitbucket.io/blog/2024/05/08/2024-ThreeLaws.html
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
281: In today's rapidly evolving tech industry, many startups believe they can challenge the well-established giants by offering similar products with minor tweaks. However, this approach is fundamentally flawed. Companies like Amazon and Microsoft will absorb a few of these new competitors, while many others will simply disappear. The driving force behind this harsh reality isn't just competition; it's the absence of truly innovative products.
The tech landscape is unforgiving to those who don't innovate. While it might seem tempting to follow the footsteps of successful giants like Adobe, Amazon, and Microsoft, the key to success lies in innovation and offering something new. Companies that fail to grasp this reality will find themselves disappearing into obscurity.
In this episode, Bret Fisher and Nirmal Mehta join Darin and Viktor to discuss how artificial intelligence is affecting the tech industry.
Bret's contact information:
X (Formerly Twitter): https://x.com/bretfisher
LinkedIn: https://www.linkedin.com/in/bretefisher
Nirmal's contact information:
X (Formerly Twitter): https://x.com/normalfaults
LinkedIn: https://www.linkedin.com/in/nirmalkmehta/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
280: Policy as Code is not just a trend but a critical practice for cloud-native success. It ensures automation, consistency, version control, auditability, security, and flexibility. By adopting policies as code, organizations can effectively manage and enforce policies, leading to improved compliance and faster incident response.
In this episode, Darin and Viktor dive deeper into the topic, share real-world scenarios, and discuss the practical implications of implementing policies as code as they review a blog post from Nirmata titled “What Is Policy-As-Code? Top 10 Reasons Why Policy-As-Code Is Essential for Cloud-Native Success”.
What Is Policy-As-Code? Top 10 Reasons Why Policy-As-Code Is Essential for Cloud-Native Success
https://nirmata.com/2024/06/24/top-10-reasons-why-policy-as-code/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
279: One topic continues to emerge in conversations about technology and observability — OpenTelemetry. It's clear that OpenTelemetry has become fundamental in the tech industry.
In this episode, we talk with Paschalis Tsilias, a software engineer with Grafana, about Alloy, a vendor-neutral distribution of the OpenTelemetry (OTel) Collector.
Paschalis' contact information:
X (Formerly Twitter): https://x.com/tpaschalis_
LinkedIn: https://www.linkedin.com/in/tsilias/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
278: In today's tech landscape, developers often find themselves caught in the middle of a debate that never seems to age: GUI or CLI? While the tools and interfaces we use may evolve, the core question remains. How do we balance the efficiency and familiarity of graphical user interfaces (GUIs) with the raw power and flexibility of command-line interfaces (CLIs)?
In this episode, Darin and Viktor discuss a blog post by Ian Miell titled In Praise of Low Tech DevEx.
In Praise of Low Tech DevEx
https://blog.container-solutions.com/in-praise-of-low-tech-devex
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
277: Developers are often caught in a challenging position. They are keen to write code, innovate, hack, and build new things. However, when security measures are perceived as long, difficult, and cumbersome tasks, these essential protocols tend to be avoided or improperly implemented. The key is to balance the pursuit of creativity with the need for robust security.
The idea is simple yet profound: by ensuring that security tools are straightforward and user-friendly, developers are more likely to incorporate them into their workflow. This not only benefits the developer but also the entire organization by safeguarding the product from potential vulnerabilities.
In this episode, we talk with Luke Hinds, CTO of Stacklok, about how bridging the gap between development and security can lead to healthier, more secure software environments.
Luke's contact information:
X (Formerly Twitter): https://x.com/decodebytes
LinkedIn: https://www.linkedin.com/in/lukehinds/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
276: In today's fast-paced tech world, one sentiment seems to echo louder than ever: "Don't give me help, give me an API." Whether it's AWS configurations, Kubernetes manifests, or even something as fundamental as setting up a basic S3 bucket, an intuitive, well-designed API can mean the difference between smooth sailing and being lost at sea.
When companies fail to adapt and streamline their operations through user-friendly APIs, they risk obsolescence.
In this episode, Darin and Viktor discuss why organizations must prioritize simplicity and customer-centric design in their technical architectures to stay competitive.
Today's sponsor:
Save 25% on your first Barbaro Mojo order using the code DevOps25
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
275: In the constantly evolving landscape of technology, embracing new methodologies can significantly enhance our system management capabilities.
One such methodology that has risen to prominence is GitOps. This practice enhances the declarative nature of infrastructure management, aiming to increase efficiency and reliability.
In this episode, we talk with Christian Hernandez about the origins, principles, and challenges of GitOps.
Christian's contact information:
X (Formerly Twitter): https://x.com/christianh814
LinkedIn: https://www.linkedin.com/in/chernandez1982/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
274: When we talk about problems in the tech space, one recurring issue is what we call the "XY problem", where understanding the root cause of a problem is crucial for crafting an effective solution.
In this episode, Darin and Viktor explore what the XY problem is, why it happens, and how we can mitigate it to create better outcomes for everyone involved.
The XY Problem
https://xyproblem.info/
Today's sponsor:
Save 25% on your first Barbaro Mojo order using the code DevOps25
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
273: Platform engineering plays a crucial role in modern software delivery. The platform engineering team is responsible for creating a development environment that is both productive and scalable. However, many platform engineers might not be familiar with foundational software design principles, and this can lead to inefficiencies and technical debt.
One such principle is the three-tier architecture model, a concept that seems to have become lost amidst the rapid evolution of technology.
In this episode, we speak with Daniel Bryant, the Head of Product Marketing at Syntasso, about how we can take the three-tier architecture model and apply it to building our platforms and portals.
Daniel's contact information:
X (Formerly Twitter): https://x.com/danielbryantuk
LinkedIn: https://www.linkedin.com/in/danielbryantuk/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
272: Public speaking, especially at conferences, can be a daunting task. The fear of failing, the pressure of performing in front of peers, and the challenges of preparation can make even the most confident individuals second-guess themselves.
In this episode, Darin and Viktor offer practical advice for aspiring conference speakers.
Today's sponsor:
Save 25% on your first Barbaro Mojo order using the code DevOps25
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
271: Platform engineering has traditionally centered around technological excellence. From building robust Kubernetes clusters to implementing intricate CI/CD pipelines, the emphasis has been on mastering the technical aspects. However, as the industry matures, there's a growing realization that technological prowess alone isn't enough.
In this episode, we speak with Puja Abbassi, the VP of Product at Giant Swarm, about how measuring success not just through the lens of technological achievement but through the tangible impact on users is really where platform engineering is headed.
Puja's contact information:
X (Formerly Twitter): https://x.com/puja108
LinkedIn: https://www.linkedin.com/in/pujaabbassi/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
270: In the ever-evolving world of software development, getting a new machine up and running can be an time consuming process. The journey from unboxing to being fully operational has undergone significant transformations over the years, with each phase offering its own solutions and challenges.
In this episode, Darin and Viktor talk about their experiences in setting up their machines and what they are doing now anytime they get a new machine.
How To Install and Use Devbox on macOS
https://www.youtube.com/live/SCWw0J_8fdk?t=1060
Today's sponsor:
Save 25% on your first Barbaro Mojo order using the code DevOps25
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
269: As developers, when we begin writing applications, the focus is often on the code itself. But what if we prioritized the user from the very beginning? This is where human-centered computing comes in. It's about placing the user at the heart of the development process, not merely making assumptions but actually going out and talking to them to understand their needs.
In this episode, we speak with Katharina Sick about her experiences with human centered computing and how that has helped her as team member of the Dynatrace platform engineering team.
Katharina's contact information:
LinkedIn: https://www.linkedin.com/in/katharinasick/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
268: Kubernetes has become the de facto standard for container orchestration, but its true strength lies in its API. Today, containers are prevalent, but tomorrow we might be dealing with a completely different runtime. The Kubernetes API, with its robust and flexible design, is poised to support these transitions seamlessly.
In this episode, Darin and Viktor talk about a few of the different ways that Kubernetes is currently being used and also where it might be headed in the future.
Today's sponsor:
Save 25% on your first Barbaro Mojo order using the code DevOps25
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact
267: In the fast-paced world of Kubernetes development, ensuring the reliability and effectiveness of applications is crucial. End-to-end testing plays a vital role in detecting bugs, ensuring proper functionality, and maintaining the overall quality of Kubernetes resources.
But what happens when existing testing tools fall short of meeting the evolving needs of developers and testers? This is what happened to the team working on Kyverno. They were using a tool but they ended up creating Chainsaw to solve their problem.
In this episode, we speak with Charles-Edouard Brétéché about the struggles the Kyverno team had with existing tools and what the team ended up doing to solve the problem.
Charles-Edouard's contact information:
LinkedIn: https://www.linkedin.com/in/eddycharly/
Chainsaw
https://kyverno.github.io/chainsaw/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
266: The tech industry has witnessed an explosion of new configuration languages that are reshaping the way we manage data structures and generate configuration files. From traditional formats like JSON and YAML to newer languages like Pkl, CUE, and KCL, the landscape of configuration languages is constantly evolving to meet the demands of modern software development.
In this episode, Darin and Viktor talk about where these languages fit in to our projects and how they can help make our lives easier if we are willing to put in the work.
Today's sponsor:
Save 25% on your first Barbaro Mojo order using the code DevOps25
https://barbaromojo.com/discount/DevOps25
Pkl
https://pkl-lang.org/
CUE
https://cuelang.org/
KCL
https://www.kcl-lang.io/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
265: The worlds of Kubernetes and GitOps are constantly evolving, each iteration bringing us closer to a more streamlined, efficient, and powerful way of managing and deploying our software architectures. Kubernetes has become the cornerstone of container orchestration, offering an unmatched level of flexibility and scalability. Meanwhile, GitOps practices are revolutionizing how we view and implement CI/CD pipelines, emphasizing a declarative way to manage infrastructure and applications.
As the Kubernetes landscape matures, clear winners in each category, such as Cilium for CNI and CertManager for certificate management, are emerging, streamlining the selection process for Kubernetes tooling. This maturation leads to a consolidation of best practices and tools, analogous to the evolution observed in Linux distributions. While diversity in tools offers flexibility, a certain level of standardization is necessary for broader adoption and ease of use.
In this episode, we talk with John Dietz, CEO and Cofounder of Kubefirst, about a potential future where Kubernetes becomes an unseen yet omnipresent force in software development.
John's contact information:
X (Formerly Twitter): https://twitter.com/vitamindietz
LinkedIn: https://www.linkedin.com/in/jd-k8s/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/`
264: In recent years, the very definition of open source has been subject to scrutiny and reinterpretation. Where once open source projects were largely managed and maintained by individuals or small groups for passion or as a hobby, today, they are at the forefront of business, technology, and innovation. The world's dependence on open-source software is undeniable. From infrastructure to development frameworks, open source underpins much of the digital world.
In this episode, Darin and Viktor reflect on how the adoption and demand for open-source software have evolved. This evolution demands a proportional change in the amount of effort that goes into these projects. No longer are they just "Saturday afternoon fun." They have become critical to business and societal functions. This shift raises a pivotal question. How do we, as a community, sustain and support the growth and maintenance of these projects.
Today's sponsor:
Save 25% on your first Barbaro Mojo order using the code DevOps25
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
263: In an era where technology is evolving at an unprecedented rate, the role of a DevOps architect has become increasingly significant. This career path is not just about overseeing development and operations. It involves a deeper understanding of the entire system, requiring a unique blend of experience across development, operations, and beyond.
The role of a DevOps architect is nuanced, blending the lines between a developer, an operations professional, and ultimately, an architect of comprehensive systems. It's a position that one doesn't simply step into right out of college. Rather, it is the culmination of years of evolving through the tech ranks, acquiring a deep understanding of both the development and operational sides of the aisle.
In this episode, we speak with Ádám Szücs-Mátyás about his role as a DevOps Architect at a large SaaS company.
Ádám's contact information:
LinkedIn: https://www.linkedin.com/in/adam-szucs/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
262: In the ever-evolving world of software development and IT infrastructure, striking the right balance between ambition and realistic expectations is a common challenge. This balance becomes even more precarious when dealing with the development and implementation of projects, be it in a Greenfield scenario or maintaining and upgrading existing systems.
In this episode, Darin and Viktor review a blog post from Ricardo Castro titled "Engineering Success: Prioritize Progress Over Grand Overhauls".
Engineering Success: Prioritize Progress Over Grand Overhauls
https://mccricardo.com/engineering-success-prioritize-progress-over-grand-overhauls/
Today's sponsor:
Save 25% on your first Barbaro Mojo order using the code DevOps25
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
261: The future of developer portals is one of seamless integration and intuitive operation. By bridging the gap between complex platforms and the developers who use them, portals can significantly enhance productivity and innovation.
This vision aligns with the ethos of companies like Port, which emphasizes an open and adaptable approach to developing internal developer portals.
In this episode, we speak with Zohar Einy, the CEO at Port, about the rapidly evolving landscape of software development and operations and the distinction between developer portals and platforms.
Zohar's contact information:
LinkedIn: https://www.linkedin.com/in/zohar-einy/
X (Formerly Twitter): https://twitter.com/ZoharEiny
Port
https://www.getport.io/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
260: In the fast-paced world of technology, advancements are constantly reshaping the way we work. As we strive to stay ahead of the curve, the debate between embracing innovation and resisting change becomes more relevant than ever.
In this episode, Darin and Viktor talk about where they see how AI is being used now, as well as how it will be used going into the future.
Today's sponsor:
Save 25% on your first Barbaro Mojo order using the code DevOps25
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
259: Terminals have been around for decades, serving as the backbone of many workflows and operations in the tech world. From managing servers to local file manipulation, terminals offer a direct line to the heart of computing. However, with the advent of graphical user interfaces (GUIs), the terminal's prominence has waned among the general user base, though it remains a powerhouse for those who know how to wield it.
Wave Terminal has emerged as a beacon of innovation in the static terminal landscape, bringing with it a host of features that leverage today's technology without abandoning the terminal's foundational principles. This modern terminal solution integrates technology, specifically Electron and Go, to create a user interface that feels familiar yet vastly more powerful.
In this episode, Darin and Viktor discuss these topics in depth with Mike Sawka, the founder of Wave Terminal, shedding light on the innovative features and the vision for Wave Terminal's future.
Mike's contact information:
LinkedIn: https://www.linkedin.com/in/mikesawka/
Wave Terminal
https://www.waveterm.dev/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
258: As startups journey through their growth phases, the choices made regarding technology infrastructure can significantly impact their agility, scalability, and ultimately, their success.
In this episode, Darin and Viktor discuss a blog post from someone that leads infrastructure at a startup where he writes about the decisions that they made as they were building their startup.
(Almost) Every infrastructure decision I endorse or regret after 4 years running infrastructure at a startup
https://cep.dev/posts/every-infrastructure-decision-i-endorse-or-regret-after-4-years-running-infrastructure-at-a-startup/
Today's sponsor:
Save 25% on your first Barbaro Mojo order using the code DevOps25
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
257: As the digital world continues to evolve, businesses and technology leaders find themselves at a critical inflection point, particularly when it comes to the deployment and management of infrastructure. The journey from traditional IT to cloud-native platforms has been significant, pushing the boundaries of innovation and efficiency. Yet, the continuous evolution raises a fundamental question: What lies ahead for Kubernetes, cloud-native platforms, and the burgeoning field of edge computing?
In this episode we speak with Joseph Sandoval about how Adobe's journey, from pioneering with its own Kubernetes distribution to embracing cloud providers' managed services and exploring edge computing, mirrors the broader industry's trajectory. Adobe's approach, focusing on developer experience and scalability, showcases the practical applications and considerations at the intersection of Kubernetes and edge computing.
Joseph's contact information:
X (Formerly Twitter): https://twitter.com/cloudtaquero
LinkedIn: https://www.linkedin.com/in/josephrsandoval/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
256: KubeCon season has started again and in this episode, we give you our thoughts on KubeCon EU 2024, along with our friend Whitney Lee.
Whitney's contact information:
Twitter: https://twitter.com/wiggitywhitney
LinkedIn: https://www.linkedin.com/in/whitneylee/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
255: In an era where software development and operations are increasingly converging, the need for effective and efficient observability tools has never been more critical. As systems grow in complexity and the lines between development and operations blur, the role of observability in understanding and managing these systems becomes more prominent.
One significant problem is the dichotomy developers face: either being completely isolated from production observability data or overwhelmed by the volume of information available, most of which may not be directly relevant to their specific tasks.
In this episode, we talk with Liran Haimovitch from Rookout about developer observability. This concept prioritizes making observability tools and data accessible and understandable for developers, allowing them to gain insights into how their code operates in production environments. This shift is not about discarding the importance of operations in observability but rather enhancing the collective capability of teams to monitor, diagnose, and resolve issues more effectively.
Liran's contact information:
X (Formerly Twitter): https://twitter.com/liran_last
LinkedIn: https://www.linkedin.com/in/liran-haimovitch/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
254: When you first started out working with infrastructure, you probably used point and click to get your work done. Over time, you created scripts to replace some of that point and click work.
But then, many infrastructure as code tools exploded on the market. You may have started working with one or two or you may have chosen to just keep doing what you were doing, but you soon realized you were falling way behind what was going on in the industry.
In this episode, Darin and Viktor discuss many of the ups and downs of using infrastructure as code and why not every infrastructure as code tool may be the right tool for you.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
253: As we move forward in 2024, one thing stands firm - platform engineering remains a significant focus for companies and has become a key component in the digital transformation journey.
This realization drove the creation of the Platform Engineering Maturity Model, a comprehensive guide that serves organizations in various stages of their platform engineering journey.
In this episode, we speak with Abby Bangser, one of the lead authors of the Platform Engineering Maturity Model published by CNCF.
Abby's contact information:
X (Formerly Twitter): https://twitter.com/a_bangser
LinkedIn: https://www.linkedin.com/in/abbybangser/
Platform Engineering Maturity Model
https://tag-app-delivery.cncf.io/whitepapers/platform-eng-maturity-model/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
252: In today's rapidly evolving technology landscape, it's crucial for organizations to keep their software stacks up-to-date. This is especially true for complex systems like Kubernetes, which require regular upgrades to ensure stability, security, and performance.
In this episode, Darin and Viktor delve into the challenges of upgrading Kubernetes and discuss best practices to follow during the upgrade process.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
251: We're becoming more and more dependent on sophisticated systems that transport data from one part of our application to another. This infrastructure, often referred to as message brokers, is a vital backbone supporting many products we use daily. But are we fully leveraging their power and simplicity?
In this episode, we speak with Valera Bronshtein, Director of Infrastructure at Memphis.dev, about event-based architectures and why using effective message brokers doesn't have to be hard or complicated.
Valera's contact information:
Twitter: https://twitter.com/ValeraBronsht
LinkedIn: https://www.linkedin.com/in/valerabr/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
250: Sure, we can use Generative AI to write code for us and generate cool pictures...sometimes.
But who has the responsibility for making sure all that infrastructure stays up and running? Look no further than your favorite sysadmin or cloud engineer. There is nothing new under the sun...
In this 250th episode, we have our friend Patrick Debois back on to talk about how he's researching we can use Generative AI beyond just the typical use cases that we see today and why understanding how to integrate all these new tools together may be more important than learning how to be a prompt engineer (whatever that means).
Patrick's contact information:
X (Formerly Twitter): https://twitter.com/patrickdebois
LinkedIn: https://www.linkedin.com/in/patrickdebois/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
249: One of the prominent discussions in the software industry is the concept of 'build versus buy.' Often the argument focuses on creating a whole system from scratch or opting for pre-built solutions.
But think about it. You never start from absolute zero. When you begin developing an application, it isn't devoid of pre-existing libraries or systems. It's about identifying the point on the spectrum from which you initiate your development journey.
In this episode, we speak with Hadi Chami from LEADTOOLS about how the key factors such as pricing, licensing model, support, maintenance, and the impact on the end product play significant roles in making this 'build versus buy' choice.
Hadi's contact information:
LinkedIn: https://www.linkedin.com/in/hadi-chami-002234131/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
248: When thinking about starting to learn a new technology, where do you start? Are you so busy at work that you're not able to spend any time learning something new?
Are you concerned that when your company finally jumps on the AI bandwagon, will you be left behind?
In this episode, Darin and Viktor talk about when and how you might want to start preparing yourself for the situation that will probably be arriving sooner than you think.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
247: What do you think of when I say “Developer Relations”? Is it a person that flys from conference to conference giving talks? Is it someone that is chasing you down to scan your badge in a booth? What if the answer to both of those questions is both yes and no?
In this episode, we speak with Lian Li about the realities of developer relations and how developer relations isn’t just something you buy off the shelf.
Lian’s contact information:
X (Formerly Twitter): https://twitter.com/lianmakesthings
LinkedIn: https://www.linkedin.com/in/lian-li/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
246: You may have been in the tech space for a number of years, but now you are ready to up-level and head down the path of being a DevOps Architect. However, you're not really sure where to begin.
In this episode, Darin and Viktor give their opinions on where you should start and the two tools that you'll need to know how to use if you really want to capture a DevOps Architect role in an enterprise.
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
245: Imagine this. You think you've been hired into a team of all A players. Think Wayne Gretsky, Michael Jordan, Lionel Messi, etc. Instead, what's really happened is you've been assigned to the team that is nothing more than the people that played behind the people that played behind the A players. Yeah, you've been demoted to the third string team.
You think, ok, at least I made a team and I'm not bagging groceries (is that still a thing?) down at the local market. Now that you're on a team, how do you plug in and help make the team better?
In this episode, we speak with Dr. David Burkus about his latest book “Best Team Ever”. We go into the 3 key areas that both the manager and the players need to understand in order to actually create a team that might even be able to beat a team of A players.
David's contact information:
Twitter: https://twitter.com/davidburkus
LinkedIn: https://www.linkedin.com/in/davidburkus/
Website: https://davidburkus.com/
YouTube channel:
https://youtube.com/devopsparadox
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
244: 2023 is in the rearview mirror. Welcome to 2024, the year of our AI overlords.
In this episode, Darin and Viktor make their predictions about all the technologies that will potentially impact our day to day work for both the good and the bad. Not surprisingly, AI is at the top of that list, but maybe not for the reasons that you might think.
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
243: Here we are at the end of 2023. Darin and Viktor look back at the predictions they made back in episode 192.
Let's see how they did.
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
242: Darin and Viktor look back over the past year. What do you have to be thankful for this year?
Also, listen all the way to the end of the episode for a handful of holiday themed tunes.
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
241: On today's episode, we go in depth with one of our friends, Whitney Lee. You may know her from her Enlightening series on Tanzu.TV or maybe from the You Choose videos she does with Viktor.
But did you know just over 4 years ago, she was a server in a vegetarian restaurant and since that time she's spoken five times at KubeCon conferences - 2 of which were keynotes?
What'll you'll learn is that just because you don't have a CS degree doesn't mean that you can't do great things in tech.
Whitney's contact information:
Twitter: https://twitter.com/wiggitywhitney
LinkedIn: https://www.linkedin.com/in/whitneylee/
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
240: Imagine being handed a nicely-wrapped box containing Platform Engineering, much like when we were sold DevOps in a Box. An enigmatic gift, with potential benefits yet accompanied by potential complexities. It calls to question - how is this different from the countless developer platforms we've seen companies launch over the years?
In this episode, we speak with Mauricio Salatino about his take on where platform engineering is today and where it's headed in the future.
Mauricio's contact information:
Twitter: https://twitter.com/salaboy
LinkedIn: https://www.linkedin.com/in/salaboy/
Platform Engineering on Kubernetes
https://www.manning.com/books/platform-engineering-on-kubernetes
Use the code "podparadox20" to save 40%
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
239: In this episode, Ville Aikas and Matt Moore from Chainguard join us for a discussion about open-source projects, distroless containers, and software security. They share their stories about the creation and progress of ChainGuard, offering insights into the way the company operates and contributes to the open-source community.
They also delve into the value of improving the signal-to-noise ratio of vulnerability scanners and how this can aid in addressing software security problems.
They also explain their commitment to the APK format and its advantages, as well as the significance of Wolfi, their '(un)distro', in maintaining vulnerability-free software environments.
Matt's contact information:
Twitter: https://twitter.com/mattomata
LinkedIn: https://www.linkedin.com/in/mattmoor/
Ville's contact information:
Twitter: https://twitter.com/aikasville
LinkedIn: https://www.linkedin.com/in/villeaikas/
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
238: You might just now be reaching the point of containerizing your workloads and running them in Kubernetes. However, how do you go about accessing those workloads? You might have started with an ingress, because other options seemed like they were too complex.
However, you've now crossed the point where you need that complexity.
That's where service mesh can help you out. On this episode, we speak with Marino Wijay, Principal Developer Advocate at solo.io, about how service mesh has evolved over time, the challenges of adopting certain models, and the advantages of open-source solutions. We also talk about the differences between sidecar and sidecar-less models, and the circumstances in which either might be appropriate.
Marino's contact information:
Twitter: https://twitter.com/virtualized6ix
LinkedIn: https://www.linkedin.com/in/mwijay/
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
237: Darin catches up with Viktor and Whitney Lee just minutes after they've finished up at KubeCon NA 2023. We discuss the good things and bad things that they experienced while in Chicago.
Could one of those things be AI?
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
236: As you are heading into budget season for 2025, you're probably trying to figure out how to eliminate as much wasteful cloud spend as you can. But how did you get here? Instead of trying to reduce your cloud spend, maybe you should think about not spending the money in the first place.
In this episode, we speak with Anton Grishko, Chief Architect at Profisea Labs, about the necessity of building cost-efficient architectures and how AI is reshaping the FinOps landscape.
Anton's contact information:
LinkedIn: https://www.linkedin.com/in/antongrishko/
5 Effective FinOps Methods for Optimizing Your Cloud Costs
https://profisealabs.com/blog/article/5-effective-finops-methods-for-optimizing-your-cloud-costs/
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
235: In the mid-2000s, Werner Vogels introduced the idea of "you build it, you run it". This concept suggested that the same team responsible for building a product should also be responsible for running and maintaining it. However, despite the initial enthusiasm, we have yet to see this phrase truly materialize in practice. The industry has faced challenges in fully realizing the "build it, run it" philosophy.
In this episode, we speak with Kaspar von Grünberg, founder & CEO at Humanitec, about why "shifting left" to the developers really isn't all it's cracked up to be and how instead cleaner abstractions can bridge the gap in understanding between non-technical managers and the developers in the trenches.
Kaspar's contact information:
Twitter: https://twitter.com/kaspar_official
LinkedIn: https://www.linkedin.com/in/kvgruenberg/
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
234: The shift to cloud computing has greatly increased the popularity of infrastructure as code.
But think about it. Cloud is nothing more than an abstraction on top of bare metal servers. Why can't we just as easily manage our bare metal servers as code as well?
In this episode, we speak with Rob Hirschfeld, founder and CEO at RackN, about the challenges and opportunities of managing bare metal servers as code.
Rob's contact information:
Twitter: https://twitter.com/zehicle
LinkedIn: https://www.linkedin.com/in/rhirschfeld/
Website: https://robhirschfeld.com/
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
233: When you first start a job, you'll probably be doing good to get paired up with a senior person to walk you through the ropes. What if instead you could sit down and actually run through simulations that were created from actual events?
In this episode, we talk with On Freund, Co-Founder and CEO at Wilco, about how Wilco can help not only individuals, but also companies needing to create better onboarding experiences for their employees and even their customers.
On's contact information:
Twitter: https://twitter.com/onfreund
LinkedIn: https://www.linkedin.com/in/onfreund/
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
232: More than eighteen months in, Log4J appears to still be a huge problem for many organizations. What if there was a way to make sure those types of problems could be easily bubbled out to the right people at the right time in the tools they are already using?
In this episode, we talk with Nir Valtman, CEO and co-founder at Arnica, about how protecting your source code, applications and people will help you minimize your risk.
Nir's contact information:
Twitter: https://twitter.com/ValtmaNir
LinkedIn: https://www.linkedin.com/in/valtmanir/
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
231: We never thought that exposing our databases to the public internet was a good thing. However, when we started creating middleware API services that sat in front of those databases, we probably ended up doing almost the exact same type work that we did when we created the database schemas themselves. Somehow or another, we thought this was good, but in reality, it was not the right solution.
In this episode, we speak with Tanmai Gopal, CEO and co-founder at Hasura, about how modern web APIs are developed and the role of modern databases in making development more efficient and scalable.
Tanmai's contact information:
Twitter: https://twitter.com/tanmaigo
LinkedIn: https://www.linkedin.com/in/tanmaig/
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
230: In today's digital age, it's no secret that relying solely on passwords for security is no longer an effective solution. We all understand the risks associated with using just passwords, but the question remains: what other alternatives do we have at our disposal?
What if you could eliminate passwords all together and still make all your communications completely secure?
In this episode, we speak with Mike Malone, Founder and CEO at Smallstep, about his background with OpenID and OAuth and how increasing security today doesn’t mean also increasing budgets.
Mike’s contact information:
Twitter: https://twitter.com/mjmalone
LinkedIn: https://www.linkedin.com/in/mmalone/
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
229: When Kubernetes was first released in September 2014, the only way we could get applications installed to the cluster was by using kubectl apply and big, ugly YAML files. Since that time, many tools have been introduced to help manage application installation into Kubernetes clusters.
However, no matter what tool you are using in 2023, under the hood, we’re still just submitting those big, ugly YAML files to the Kubernetes. Once you realize this, things become much clearer.
In this episode, we take a stroll down memory lane of how it all started and what you should consider doing today when creating (or maybe not creating) the YAML files for your application.
Today’s sponsor:
Save 25% on your first Barbaro Mojo order using the code "DevOps25”
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
228: The Agile Manifesto is now more than 20 years old. However, even after all this time, instead of helping organizations create and deliver software faster to satisfy customer needs, many times Agile principles are turned into rigid processes that stifle innovation and limit customer satisfaction. Have far have we strayed from the core principles of the manifesto?
In this episode, we talk with Paul Stovell, CEO and founder of Octopus Deploy, about the realities of Agile in 2023. Also, find out about the backstory of how Paul was able to snag the octopus.com domain.
Paul’s contact information:
Twitter: https://twitter.com/paulstovell
LinkedIn: https://www.linkedin.com/in/paulstovell/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
227: Imagine this. You walk into your office and your manager pulls you to the side and says “Pack up your belongings. You’ve been made redundant. We wish you the best in your future endeavors.”
Just like that, you no longer have a job.
In even more extreme cases, just because a company exists today does not mean that it will exist tomorrow. Think about Enron, Blockbuster, Compaq and many others.
At this point in history, it’s not if, but when, will you be laid off and what will you do?
In this episode, we speak with Dagna Bieda, founder of theMindfulDev.com, about strategies to "layoff-proof" your engineering career, touching on topics like the role of AI in the industry, the importance of mental health, and the impact of our belief systems on our careers.
Dagna’s contact information:
Twitter: https://twitter.com/dagnabieda
LinkedIn: https://www.linkedin.com/in/dagnabieda/
Website: https://www.themindfuldev.com/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
226: Dependency on third-party providers is an inescapable reality of modern operations. However, expecting third-party providers to solve everything for you is highly unrealistic. Even if you had all the money in the world, you probably still would have issues with your operations.
In this episode, we break down an article that discusses what level of support and services we should expect from third-party providers.
Cloud Dependencies Need to Stop F—ing Us When They Go Down
https://thenewstack.io/cloud-dependencies-need-to-stop-f-ing-us-when-they-go-down/
Today’s sponsor:
Save 25% on your first Barbaro Mojo order using the code "DevOps25”
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
225: How did Kubernetes become the predominant choice for modern-day DevOps teams? From changing how applications run to reshaping security parameters, learn how this open-source platform continues to turn heads.
In today’s episode, we talk with Craig Box, VP of Open Source and Community at Armo, as he uncovers the secrets behind Kubernetes. From Google's original vision for the tool to its unexpected rise in popularity within the DevOps community, we'll explore Kubernetes' improbable journey. Also, we’ll get insights into managing potential security issues, and learn how Kubescape is transforming Kubernetes' security landscape.
Craig’s contact information:
Twitter: https://twitter.com/craigbox
LinkedIn: https://www.linkedin.com/in/crbnz/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
224: Are boot camps and CS degrees always necessary for landing a job? Or, can hands-on learning through eLearning platforms bridge that gap?
In today’s episode, we speak with Lane Wagner, creator of boot.dev, to learn about the obstacles new developers face on their journey to becoming proficient back-end developers.
Lane’s contact information
Twitter: https://twitter.com/wagslane
LinkedIn: https://www.linkedin.com/in/wagslane/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
223: Maybe you’ve been in the tech space for years and you’re ready to get into open source. On the other hand, you may be fresh out of school and you’re trying to build your CV. What project should you start to work on? The answer is easier than you think.
In this episode, we speak with Dotan Horovits, Principal Developer Advocate at Logz.io, on topics ranging from running an in-person event to the proper way to engage in open source communities.
Dotan’s contact information:
Twitter: https://twitter.com/horovits
LinkedIn: https://www.linkedin.com/in/horovits/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
222: Where do you start when you are having performance bottlenecks in your application? You might start looking at a log or a dashboard. What if there was a better way?
In this episode, we speak with Kursat and Fatih, co-founders of Ddosify, about how the standard way of analysis will become a thing of the past.
Kursat’s contact information:
Twitter: https://twitter.com/kursat_aktas_
LinkedIn: https://www.linkedin.com/in/kursataktas/
Fatih’s contact information
Twitter: https://twitter.com/fatihbaltaci_
LinkedIn: https://www.linkedin.com/in/fatihbaltaci/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
221: As an application developer, how often do you receive spreadsheets of findings from your security team? Do you drop everything you’re doing and work your way through the 57,239 findings during your existing sprint? Our guess is probably not. Even if you did, how would you know where to start? Just because a finding is marked as critical does not mean that it’s exploitable.
In this episode, we speak with Ravid Circus, CPO at Seemplicity, about how you should be handling and remediating these security problems. Hint: it’s not by using spreadsheets, but rather it needs to be in your day to day work.
Ravid’s contact information:
LinkedIn: https://www.linkedin.com/in/ravid-circus-302a8/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
220: DevOps has revolutionized software development and operations, enabling organizations to deliver software faster, with improved quality and collaboration. But as with any significant transformation, implementing DevOps comes with its own set of challenges.
In this episode, we focus on the top challenges faced during the implementation of DevOps. From cultural resistance to finding skilled labor at a price you’re willing to pay, we'll explore the hurdles that can hinder DevOps adoption.
Today’s sponsor:
Save 25% on your first Barbaro Mojo order using the code "DevOps25”
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
219: In a world overflowing with data, traditional relational databases struggled to keep up with the demands of scalability, flexibility, and performance. Enter NoSQL, a groundbreaking approach to database management that shattered the limitations of the past.
In this episode, we talk with Matthew Groves, developer advocate for Couchbase, about his thoughts on SQL (the language), where you should actually start programming if you’re new to the industry and why conferences and user groups are starting to make their return.
Matthew’s contact information:
Twitter: https://twitter.com/mgroves
LinkedIn: https://www.linkedin.com/in/mgroves/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
218: Continuous testing has become an integral part of modern software development and delivery. It enables organizations to maintain high quality and agility in the face of rapid software iterations. But how can we harness the power of artificial intelligence to enhance and optimize the continuous testing process?
In this episode, we speak with Bharath Vantari, Principal Presales at Perforce for Blazemeter, about how we should start thinking how we can add AI into our continuous testing process.
Bharath’s contact information:
Twitter: https://twitter.com/BharathVantari
LinkedIn: https://www.linkedin.com/in/bharathvantari/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
217: Extended Berkeley Packet Filter, or eBPF, has been making waves in the tech industry over the past few years. It's a technology that enables you to extend the functionality of the Linux kernel without having to write kernel modules. But what exactly is eBPF, and how does it impact our systems, networks, and security?
In this episode, we speak with Liz Rice, Chief Open Source Officer with eBPF pioneers Isovalent, about where eBPF started and why you may never write a line of (byte)code of eBPF yourself.
Liz’s contact information:
Twitter: https://twitter.com/lizrice
LinkedIn: https://www.linkedin.com/in/lizrice/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
216: As your team continues down the microservices journey, at some point you’ve probably hit the wall on being able to test against the versions of the other services that you really need to test. You could spin up new hardware, but that becomes very inefficient and very costly very quickly.
Since you are running your production (and staging and QA) environments in Kubernetes, there has to be an easy way to do this type of testing.
In this episode, we speak with Arjun Iyer, CEO and Co-founder at Signadot, about how sandboxes within your Kubernetes clusters can help with your testing problem without breaking the bank.
Arjun’s contact information:
Twitter: https://twitter.com/arjuniyer_
LinkedIn: https://www.linkedin.com/in/arjun-iyer-916332/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
215: Thoughtworks recently released Volume 28 of their Technology Radar. Darin and Viktor take some time to break it down and discover that they might be in the wrong jobs.
Thoughtworks Technology Radar
https://www.thoughtworks.com/en-us/radar
Today’s sponsor:
Save 25% on your first Barbaro Mojo order using the code "DevOps25"
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
214: When we first start developing applications, we probably also use a database. But at some point in time, we’ll probably hit a wall with that database because of changing business requirements. What are we supposed to do then?
In this episode, we speak with Arjun Narayan, CEO of Materialize, about of a number of items ranging from why you should move from the no-win scenario of self-hosting to fully managed services and why you may be doing too much when building and orchestrating microservices.
Arjun’s contact information:
Twitter: https://twitter.com/narayanarjun
LinkedIn: https://www.linkedin.com/in/arjunravinarayan/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
213: You've been tasked with bringing a new SaaS product to market. Where do you start?
Logically, or maybe not so much so, it's important to start by defining your target audience, understanding their needs, and developing a solution that meets those needs. You’ll also probably end up fighting the build from scratch versus modifying something that already exists battle.
In this episode, we speak with Mav Turner, CTO of DevOps at Tricentis, about his thoughts on how to correctly assemble teams to get a product successfully launched and learning to love constraints.
Mav’s contact information:
LinkedIn: https://www.linkedin.com/in/mav-turner-b5542a4/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
212: Let’s assume for a moment that you are building a SaaS that you want to turn into a product. Sure, you need to make sure your authentication works, but that’s really step 1 of potentially thousands of steps. Should you create all the services you really need to run a SaaS or should you pull something off the shelf?
In this episode, we speak with Anton Zagrebelny, the co-founder and CTO of Stigg, about some of the reasons why you should use solutions that solve your problem instead of trying to build it yourself.
Anton’s contact information:
LinkedIn: https://www.linkedin.com/in/anton-zagrebelny/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
211: With the advent of video games like Minecraft and Roblox, kids are starting to learn to code at much younger ages than before. The question is are these kids going to be ready to become the computer programmers for the next generation?
In this episode, we speak with Jim Douglas, CEO at Armory, about the reality of what programming will look like in the future and what skills we need to be learning now if we don’t want to be displaced by middle school students.
Jim’s contact information:
LinkedIn: https://www.linkedin.com/in/jidouglas/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
210: If you're feeling frustrated and overwhelmed due to your current database deployment and management process not working as expected, then you are not alone! Think about how many times you’ve needed to maintain the schema of your database and then you give up because it’s either going to break things or it’s going to take too long for a migration to happen.
In this episode, we speak with Sam Lambert, CEO of PlanetScale, about how running your own database should be considered a thing of the past and that you really shouldn’t be scared to make changes to your database schema when it's as simple as doing a rewind.
Sam’s contact information:
Twitter: https://twitter.com/isamlambert
LinkedIn: https://www.linkedin.com/in/isamlambert/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
209: Many people think they want to take their applications and run replicas of those applications on different cloud providers to mitigate risk. What if instead you created your applications to leverage the benefits of all the different cloud providers?
In this episode, we speak with Chetan Venkatesh, CEO and founder of Macrometa, about why using multiple cloud services to run cookie cutter versions of your applications is actually a bigger problem than it might seem on the surface.
Chetan’s contact information:
Twitter: https://twitter.com/chetan_
LinkedIn: https://www.linkedin.com/in/chetanvenkatesh/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
208: KubeCon season has started again and in this episode, we give you our thoughts on KubeCon EU 2023, along with our friends Whitney Lee and Engin Diri.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
207: When you begin building a SaaS product, it’s pretty straightforward. Open an account with one of the big 3 hyperscalers, upload your code, then profit! Ok, only those first two are guarantees. The third one is up for interpretation.
In this episode, we speak with Yaniv Leven, VP of SaaS products at SQream, about what it was like to build a “native” SaaS product in 2016 and how that differs to converting a classical on-premise application to SaaS in 2023.
Yaniv’s contact information:
Twitter: https://twitter.com/yanivleven
LinkedIn: https://www.linkedin.com/in/yanivleven/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
206: As an application developer, you’re probably used to pulling libraries from Maven Central, PyPI, or npm Registry. Has it ever crossed your mind how secure is this thing that I’m pulling or do you just YOLO so you can get the job done?
In this episode, we speak with Stephen Chin, VP of Developer Relations at JFrog, about Pyrsia, an open source project that helps protect the open source supply chain so you can have confidence in the libraries that you use.
Stephen’s contact information:
Twitter: https://twitter.com/steveonjava
LinkedIn: https://www.linkedin.com/in/steveonjava/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
205: At the end of 2022, Werner Vogels, CTO at Amazon, published a blog post about the tech predictions for 2023 and (more importantly) beyond.
In this episode, Darin and Viktor dig into a couple of those predictions, namely simulated worlds (digital twins) and custom silicon.
Tech predictions for 2023 and beyond
https://www.allthingsdistributed.com/2022/12/tech-predictions-for-2023-and-beyond.html
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
204: When you think about managing data in an organization, you’re probably familiar with the concept of ETL: extract, transform and load. But in this world of new data tools, the order of transform and load can become problematic.
In today’s episode, we speak with Itamar Ben Hemo, Co-Founder and CEO at Rivery, about why you might want to consider flipping that order. We also discuss why if you aren’t using SaaS solutions for data management, you’re probably quickly falling behind your competitors.
Itamar’s contact information:
Twitter: https://twitter.com/Itamar_Hemo
LinkedIn: https://www.linkedin.com/in/itamar-ben-hemo-47080a5/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
203: Given a choice, would you rather have broken builds or flaky tests? At least with a broken build, you have certainty of what is happening. How do you go about eliminating both from your environment?
In this episode, we speak with Ankit Jain, CEO at Aviator, about different ways you can approach these two issues. We also dive head first into the debate about whether you should be using a monorepo in your organization.
Ankit’s contact information:
LinkedIn: https://www.linkedin.com/in/ankitjaindce/
Twitter: https://twitter.com/ankitxg
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
202: How many people love Helm? Yeah, that’s what we thought. A lot of the time, you’re probably looking for an easier and simpler way to manage installing applications into a Kubernetes cluster.
You might be wishing that you could use something as simple as Docker Compose to do that, but you can’t see a way forward.
In this episode, we speak with Benjie De Groot, Co-Founder at Shipyard, about how approaching development from the human side instead of the machine side can make this possible.
Benjie’s contact information:
LinkedIn: https://www.linkedin.com/in/bueller/
GitHub: https://github.com/bueller
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
201: As an application developer, we’re used to adding logging to our applications. We also work with our operations counterparts to enrich those logs to help them out when troubleshooting. But what happens during an incident when the logs are flowing so fast that neither you nor the operations people can keep up? That’s where machine learning can help.
In this episode, we speak with Ajay Singh, CEO at Zebrium, about why humans need help troubleshooting issues and how machine learning helps detect outliers and solve those last mile problems.
Ajay’s contact information:
LinkedIn: https://www.linkedin.com/in/ajaysingh3/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
200: We’ve reached episode 200!!! As we do with all our divide by 50 episodes, we invited our friend Patrick Debois back to discuss topics ranging from digital twins to the metaverse to AI to becoming a manager.
Patrick’s contact information:
Twitter: https://twitter.com/patrickdebois
LinkedIn: https://www.linkedin.com/in/patrickdebois/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
199: You’re probably used to hearing about using OpenTelemetry for your production troubleshooting. But have you considered using OpenTelemetry during your development lifecycle?
In this episode, we speak with Ran Nozik, CTO and co-founder of Helios, about the current state of OpenTelemetry and how using OpenTelemetry may save us a lot of time troubleshooting issues in production if we first start using while we are developing our applications.
Ran’s contact information:
LinkedIn: https://www.linkedin.com/in/ran-nozik/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
198: It’s the dream that many of us have. We set out to build a service that gains a lot of adoption. However, we when reach that goal, we find that building something successful can make it an attractive target for attackers.
In this episode, we speak with Brian Smith, CTO of Spyderbat, about how traditional security tools don't meet the dynamic requirements of Kubernetes and that the processes we put in place to manage our runtime security need to be part of a shift-left approach.
Brian’s contact information:
LinkedIn: https://www.linkedin.com/in/brian-smith-07a4191/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
197: Do you feel like you are working in a company that is not only behind the times but behind the century? If you feel stuck, is it because you’re too scared to search for another job and losing all the benefits you’ve accrued over the years at your current company?
In this episode, we talk about a couple of Reddit and Twitter threads that surprised us, but in reality, they shouldn’t have. It’s a very sobering reminder that not everyone is not only working on the latest and greatest, some are just now moving to technology that has already reached end of life.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
196: Where do you start when you work on optimizing the performance of your application? The number of options can seem overwhelming. Do you start with memory, CPU, network, or somewhere else? Even if you get it right, it's only right for right now and not next week when you release a new version of your application, at which point you start the performance optimization process all over again.
What if there was a way to continuously optimize for performance? That's where Granulate comes in.
In this episode, we talk with Noam Salinger, Director of Product Management at Granulate, about different ways you can optimize the performance of your applications and the basics that you might not even be doing today.
Noam’s contact information:
LinkedIn: https://www.linkedin.com/in/noam-salinger-313025126
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
195: Most companies have decades of legacy systems running their day-to-day business. They're difficult to replace with newer systems, and they're costly to maintain. But they also offer security, stability, and consistency. The challenge is deciding how to make them work in the modern world.
In this episode, we talk with Robert Cooke, CTO and Founder at 3forge, about why replacing legacy systems is not a simple as just doing it and also why open source may not be the answer that everyone thinks it is.
Robert’s contact information:
LinkedIn: https://www.linkedin.com/in/robert-cooke-a7835b69/
Website: https://3forge.com/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
194: Whether you are doing greenfield development with microservices or are doing brownfield development migrating monoliths to microservices, there’s one thing that you have to get right when testing those microservices, otherwise you will fail. What is that one thing?
Culture.
If you don’t get the culture right, no amount of technology will fix the problems that you have now or in the future.
In this episode, we talk with Darko Fabijan, co-founder of Semaphore, about the process and structure you need to follow when migrating away from monoliths and how to make sure that you get the culture right in order to succeed in the long term.
Darko’s contact information:
Twitter: https://twitter.com/darkofabijan
LinkedIn: https://www.linkedin.com/in/darkofabijan/
Podcast: https://semaphoreci.com/podcast
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
193: As a database administrator, you probably want to spend more time trying to make things better for people using your database instead of always chasing down the latest tuning parameters or queries that are causing problems. There are only 24 hours in a day and you’re not sure if you’ll ever be able to really make things any better with the schema changes and data volume that are constantly being thrown at the database you manage.
In this episode, we talk with Andy Pavlo, CEO at OtterTune, about the knobs that should be turned in Postgres or MySQL before you even start trying to do any index or query tuning.
Andy’s contact information:
Twitter: https://twitter.com/andy_pavlo
YouTube channel: https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
192: Have you decided what you're going to be learning in 2023? In their annual attempt to read the crystal ball, Darin and Viktor talk about the things that you need to learn or that you will probably be learning in 2023.
Save 25% on your first Barbaro Mojo order using the code "DevOps25"
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
191: In this episode, we recap all of the predictions we made at the beginning of 2022 and see how we did.
Save 25% on your first Barbaro Mojo order using the code "DevOps25"
https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
190: Darin and Viktor look back over 2020 part 3, in other words, 2022. Also, for something new this year, listen all the way to the end of the episode for a couple of hand-picked holiday tunes.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
189: In the distant past, we used punchcards and dumb terminals to program. Then came the advent of the personal computer and we started developing locally on our machines. There are now new offerings that allow us to use pretty much any device that has a web browser to do all our programming. One of those offerings is Gitpod.
On this episode, we speak with Chris Weichel, CTO of Gitpod, about the history of Gitpod and why the standard developer machine is ripe for disruption.
Chris’ contact information:
Twitter: https://twitter.com/csweichel
LinkedIn: https://www.linkedin.com/in/christian-weichel-740b4224/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
188: Just because you’ve run some chaos experiments against your system doesn’t mean you are ready to fend off wide ranging and prolonged attacks. It just means that you might be ready for the attacks you’ve created experiments for. Why? Because you probably didn’t actually fully load your systems with persistent and ever-changing attacks.
In this episode, we talk with Benjamin Wilms, CEO of Steadybit, about why just running chaos experiments is just one part of helping make your systems resilient and why capturing what happens in real-life incidents can help you create even better experiments.
Benjamin’s contact information:
Twitter: https://twitter.com/mrbwilms
LinkedIn: https://www.linkedin.com/in/benjamin-wilms/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
187: When writing tests that need to talk to a data source, you're usually faced with a couple of options. The first one is that you setup a database server on your machine. The problem with that is what happens when other developers need to run those same tests? They have to setup the database too.
The other option is you can mock your database connections. However, it's hard to keep your mock up to date with the latest features of the database you are using. What if there was another option you could use? Enter Testcontainers.
In this episode we speak with Sergei Egorov from AtomicJar about the history of Testcontainers and how to implement it into your development processes.
Sergei’s contact information:
Twitter: https://twitter.com/bsideup
LinkedIn: https://www.linkedin.com/in/bsideup/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
186: Most companies say they want their application developers to be shipping more code faster and faster. However, those same companies don’t do enough to help the application developers be successful at doing that.
In this episode, we speak with Ankit Bhati, co-founder and CEO at Amnic, about how by providing a unified operating platform for your application developers will not only help speed up the work that those developers do, but also reduce the risk in running the applications that go through this platform.
Ankit’s contact information:
LinkedIn: https://www.linkedin.com/in/ankitbhati/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
185: You've been told that you have to reduce your AWS bill. You also know that you cannot make any major changes to your infrastructure quickly. By carefully considering your needs and being willing to make some concessions, you can reduce your AWS bill significantly. But where do you start?
In this episode, we talk with Ganesh The Awesome from GlobalDots about where to start when trying to reduce your AWS bill.
Ganesh’s contact information:
LinkedIn: https://www.linkedin.com/in/stevenpuddephatt/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
185: You've been told that you have to reduce your AWS bill. You also know that you cannot make any major changes to your infrastructure quickly. By carefully considering your needs and being willing to make some concessions, you can reduce your AWS bill significantly. But where do you start?
In this episode, we talk with Ganesh The Awesome from GlobalDots about where to start when trying to reduce your AWS bill.
Ganesh’s contact information:
LinkedIn: https://www.linkedin.com/in/stevenpuddephatt/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
184: The public cloud is a powerful tool that allows businesses to outsource their data and compute to ensure security, availability, scalability, and reliability. But like many tools, they cannot be used best without understanding the total cost of ownership. By cost, we really mean cold, hard cash.
In this episode, we talk with Jason Yaeger, Co-Founder & CEO of Tenacity Cloud, about how Tenacity is tackling the problem of helping businesses understand their true cloud costs and why you shouldn't trust your cloud provider to give you the best possible discounts.
Jason’s contact information:
Twitter: https://twitter.com/jasnoyaeger
LinkedIn: https://www.linkedin.com/in/jasonyaeger/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
184: The public cloud is a powerful tool that allows businesses to outsource their data and compute to ensure security, availability, scalability, and reliability. But like many tools, they cannot be used best without understanding the total cost of ownership. By cost, we really mean cold, hard cash.
In this episode, we talk with Jason Yaeger, Co-Founder & CEO of Tenacity Cloud, about how Tenacity is tackling the problem of helping businesses understand their true cloud costs and why you shouldn't trust your cloud provider to give you the best possible discounts.
Jason’s contact information:
Twitter: https://twitter.com/jasnoyaeger
LinkedIn: https://www.linkedin.com/in/jasonyaeger/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
183: Darin catches up with Viktor just minutes after he finishes up at KubeCon NA 2022. We discuss the good things and bad things that he experienced and some surprises that you might not have seen coming.
Save 25% on your first Barbaro Mojo order using the code "DevOps25": https://barbaromojo.com/discount/DevOps25
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
182: As developers, we've all started at least a few side projects. Sometimes they're just for fun, or as a way of learning something new.
Other times you find yourself building something really cool that might even turn out to be your life's work. If you're able to run that project and grow it to a sizable monthly revenue, you could sell it and potentially do whatever you want for the rest of your life.
In this episode, we talk with Ryan Kulp about the path he took to get to Merge Freeze and how you might be able to follow a similar path.
Ryan’s contact information:
Twitter: https://twitter.com/ryanckulp
Website: https://www.ryanckulp.com/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
181: Once you have your Kubernetes cluster up and running, what do you do next? One option is to monitor it and make sure everything is running smoothly.
On this episode, we talk with Ruben Hakopian, the founder of Kubevious, about how the project started and how you can start using it today.
Ruben’s contact information:
Twitter: https://twitter.com/rubenhak
LinkedIn: https://www.linkedin.com/in/rubenhak
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
180: At a time when big data and machine learning are transforming the enterprise, it is hard to see what is coming next. The answer: artificial intelligence. The transformation of AI into AIOps — machine learning in the cloud that continuously learns and optimizes predictive models — may be the next game-changer for businesses, but how can you get started?
In this episode, we speak with Richard Whitehead, CTO at Moogsoft, about where AIOps is in 2022, and why the humans shouldn’t fear for their jobs…yet.
Richard’s contact information:
Twitter: https://twitter.com/rwhitehead
LinkedIn: https://www.linkedin.com/in/richardwhitehead/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
179: For many decades, the use of service level objectives (SLOs) in IT has been a routine part of day-to-day business. The objectives are based on measurable impacts that each individual customer or operational unit should experience with a specific IT service. These SLOs are typically associated with costs and benefits that can be tracked over time.
But what do you need to do if you are new to SLOs? What are the pitfalls associated with introducing SLOs into an environment where they have not yet been a part of the culture? For those of you that have been working with IT for any length of time, there has probably been one idea in the IT space that has received more flak from different teams than anything else. Many people and teams still do not understand what SLOs are, how to use them and why some companies use them and others do not.
In this episode, we speak with Brian Singer, the Chief Product Officer at Nobl9, about the mechanics of implementing and maintaining SLOs in your organization.
Brian’s contact information:
Twitter: https://twitter.com/brian_singer
LinkedIn: https://www.linkedin.com/in/briantsinger/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
178: Observability has been around since the dawn of computing. Around 1992, BPF was introduced. It gave us the ability to do network packet filtering. Around 22 years later in 2014, eBPF was included in Linux kernel 3.18, building on top of what was available with BPF. Now in 2022, eBPF is helping to supercharge Kubernetes observability.
In this episode, we speak with Shachar Azulay, CEO and Co-Founder of groundcover, about how eBPF is changing how we monitor our Kubernetes clusters in five minutes or less.
Shachar’s information:
LinkedIn: https://www.linkedin.com/in/shahar-azulay-54156bb4/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
178: Observability has been around since the dawn of computing. Around 1992, BPF was introduced. It gave us the ability to do network packet filtering. Around 22 years later in 2014, eBPF was included in Linux kernel 3.18, building on top of what was available with BPF. Now in 2022, eBPF is helping to supercharge Kubernetes observability.
In this episode, we speak with Shachar Azulay, CEO and Co-Founder of groundcover, about how eBPF is changing how we monitor our Kubernetes clusters in five minutes or less.
Shachar’s information:
LinkedIn: https://www.linkedin.com/in/shahar-azulay-54156bb4/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
177: Imagine this. What if you could magically turn your 20 year old Java and .NET applications into modern, containerized applications without having to spend years doing it? Also, what if you could do this with the help of AI? Seems too good to be true?
In this episode, we speak with Bob Quillin, Chief Ecosystem Officer at vFunction, about the classical and painful ways we’ve tried to do application modernization in the past and how AI is helping to reduce a lot of those pain points in 2022.
Bob’s contact information:
Twitter: https://twitter.com/bobquillin
LinkedIn: https://www.linkedin.com/in/bob-quillin-46802511/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
177: Imagine this. What if you could magically turn your 20 year old Java and .NET applications into modern, containerized applications without having to spend years doing it? Also, what if you could do this with the help of AI? Seems too good to be true?
In this episode, we speak with Bob Quillin, Chief Ecosystem Officer at vFunction, about the classical and painful ways we’ve tried to do application modernization in the past and how AI is helping to reduce a lot of those pain points in 2022.
Bob’s contact information:
Twitter: https://twitter.com/bobquillin
LinkedIn: https://www.linkedin.com/in/bob-quillin-46802511/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
176: Many people ask us what they need to do in order to start a career in DevOps. The usual initial question is “what technologies do I need to learn?” What if we told you that you shouldn’t necessarily start with the tech but with something else?
In this episode, we speak with Sashank Purighalla, CEO and Founder of BOS Framework, about the critical skills that every engineer should master in order to start and grow their DevOps career.
Sashank’s contact information:
Twitter: https://twitter.com/sashankbos
LinkedIn: https://www.linkedin.com/in/sashankpurighalla/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
176: Many people ask us what they need to do in order to start a career in DevOps. The usual initial question is “what technologies do I need to learn?” What if we told you that you shouldn’t necessarily start with the tech but with something else?
In this episode, we speak with Sashank Purighalla, CEO and Founder of BOS Framework, about the critical skills that every engineer should master in order to start and grow their DevOps career.
Sashank’s contact information:
Twitter: https://twitter.com/sashankbos
LinkedIn: https://www.linkedin.com/in/sashankpurighalla/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
175: When most people start with low-code and no-code applications, they log in to a user interface, fill in some forms and do a lot of pointing and clicking. As we’ve learned over the years, that is just an invitation for long-term trouble. What if were possible to treat our low-code and no-code application development the same way as we treat our normal application development?
In this episode, we speak with Gil Hoffer, Co-Founder and CTO of Salto, about a number of issues around the low-code and no-code application development ecosystem and why you might want to consider approaching these development processes in a more standard way.
Gil’s contact information:
Twitter: https://twitter.com/gilhoffer
LinkedIn: https://www.linkedin.com/in/gilhoffer/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
175: When most people start with low-code and no-code applications, they log in to a user interface, fill in some forms and do a lot of pointing and clicking. As we’ve learned over the years, that is just an invitation for long-term trouble. What if were possible to treat our low-code and no-code application development the same way as we treat our normal application development?
In this episode, we speak with Gil Hoffer, Co-Founder and CTO of Salto, about a number of issues around the low-code and no-code application development ecosystem and why you might want to consider approaching these development processes in a more standard way.
Gil’s contact information:
Twitter: https://twitter.com/gilhoffer
LinkedIn: https://www.linkedin.com/in/gilhoffer/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
174: As more and more companies start to use low-code and no-code solutions within their organizations, how many of them are actually evaluating their security posture? Do these organizations not realize they are literally giving away the keys to their kingdoms to third party providers?
In this episode, we speak with Alon Jackson, CEO and Co-Founder at Astrix Security, about how these internally produced low-code and no-code applications present even further security risks due to the lack of professional security processes for these applications.
Alon's contact information:
LinkedIn: https://www.linkedin.com/in/jackson-alon/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
173: How much time have you wasted writing YAML files, helm charts or Kustomize configurations? What if deployments to Kubernetes could be as simple as drag and drop?
In this episode, we speak with Dom Holt, the CEO of Harpoon, about how Harpoon can make this drag and drop dream become reality.
Dom’s contact information:
LinkedIn: https://www.linkedin.com/in/dominicholt/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
172: As a developer, we might think we know how our application is going to run in production. We know we’ll need a web server, an application server and a database. But what we might not know is how popular (or unpopular) our application is going to be and what the actual sizing is that we’ll need in order to optimally run our application.
In this episode, we speak with Maxim Melamedov from Zesty about the different models that need to be taken into account when not only designing and writing our applications but also operating them at scale.
Maxim’s contact information:
LinkedIn: https://www.linkedin.com/in/maximmelamedov/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
171: How many hours a day do you think you code? 5? 4? Maybe 3?
What if I told you that you were only averaging 52 minutes each day?
In this episode, we talk with Mason McLead, CTO at Software, about the Code Time Report they released. In this report, you may discover that a few key secrets to help you increase your time in front of your IDE and less time in meetings.
Mason’s contact information:
LinkedIn: https://www.linkedin.com/in/mmclead/
Global Code Time Report
https://www.software.com/reports/code-time-report
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
170: Containers are one of the quickest ways we can move away from a traditional server-centric architecture, as they allow us to host software "in the cloud" without over-provisioning resources or managing infrastructure like we did with virtual machines.
What do you think about when you hear edge computing? Is it CDN, serverless functions, or something else? All of these definitions can be heavily related to the concept of edge computing. The term itself is ambiguous and hard to grasp.
But what happens when you try to run containers at the edge? In this episode, we speak with Dan Bartholomew, Co-Founder & CTO at Section, about how running containers at the edge is much more than deciding what city to run your container in.
Dan’s contact information:
Twitter: https://twitter.com/dbartholomew
LinkedIn: https://www.linkedin.com/in/daniel-bartholomew-27baa625/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
169: With the development trend toward cloud services, developers need to build and deploy applications in this new paradigm. However, it may be difficult to determine what is possible and what is not, because building on a cloud service can lead to unforeseen difficulties that require a more complex solution.
In this episode, we speak with Ala and Aaron from Klotho about how complexity cannot be avoided as well as how operations teams are on the rise.
Ala’s contact information:
Twitter: https://twitter.com/alashiban
LinkedIn: https://www.linkedin.com/in/alashiban/
Aaron’s contact information:
Twitter: https://twitter.com/aarontorres
LinkedIn: https://www.linkedin.com/in/torresaaron/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
169: With the development trend toward cloud services, developers need to build and deploy applications in this new paradigm. However, it may be difficult to determine what is possible and what is not, because building on a cloud service can lead to unforeseen difficulties that require a more complex solution.
In this episode, we speak with Ala and Aaron from Klotho about how complexity cannot be avoided as well as how operations teams are on the rise.
Ala’s contact information:
Twitter: https://twitter.com/alashiban
LinkedIn: https://www.linkedin.com/in/alashiban/
Aaron’s contact information:
Twitter: https://twitter.com/aarontorres
LinkedIn: https://www.linkedin.com/in/torresaaron/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
168: At DockerCon 2022, Docker announced a number of improvements to Docker Desktop, including extensions and Docker Desktop for Linux. What is it going to take for Viktor to install Docker Desktop on his machine again?
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
167: When you install vanilla Kubernetes, which security option do you take? Trick question. There are no options. It is always installed wide open. If you're just experimenting, that's probably not a big deal.
However, how many times have we had an experiment turn into a production system? Probably too many times to count. At that point, retrofitting security into your Kubernetes cluster is near impossible.
In this episode, we speak with Lachlan Evenson about his thoughts on the proper strategies to secure your Kubernetes clusters.
Lachlan’s contact information:
Twitter: https://twitter.com/LachlanEvenson
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
166: In-person events are starting to ramp back up. However, there are plenty of online conferences. Worse yet, some companies are still trying to do hybrid events.
In this episode, we dig into what makes for a bad online experience and some different ways that event organizers should consider to make the experience better for attendees.
Robin’s blog posts:
Remote-First Developer Advocacy
https://rmoff.net/2022/04/07/remote-first-developer-advocacy/
Hanging up my Boarding Passes and Jetlag…for now
https://rmoff.net/2022/04/07/hanging-up-my-boarding-passes-and-jetlagfor-now/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
165: Viktor recently (sort of) attended KubeCon EU 2022 in Valencia, Spain. In this episode, we talk about everything that Viktor saw and experienced. We also attempt to answer the age old question, how was the conference food?
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
164: When you create a monolithic application, it's usually not a huge deal to add in some form of monitoring to keep track of what is happening when. However, when you start writing numerous microservices, specifically functions as a service, the ability to simply and easily keep track of what is happening when is thrown out the window.
In this episode, we speak with Aviad Mor, CTO of Lumigo, about how to monitor large numbers of microservices and how to debug them when something goes wrong.
Aviad’s contact information:
Twitter: https://twitter.com/aviadmor
LinkedIn: https://www.linkedin.com/in/aviadmor/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
163: When you first start out with Kubernetes, probably the last thing on your mind is how much it costs. So how does one figure out what a Kubernetes cluster costs?
In this episode, we speak with Webb Brown from Kubecost about the tradeoffs between hard cost, optimization and efficiency.
Webb’s contact information:
Twitter: https://twitter.com/webb_brown
LinkedIn: https://www.linkedin.com/in/webbbrown/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
162: Ever since the release of web applications, performance testing tools have been around to help analyze load times and many other aspects of those applications.
However, many of those performance testing tools require you to learn vendor specific languages or you're forced to point and click in order to create your tests. These requirements to use those tools made it really unpleasant for developers to create and maintain tests.
In this episode, we speak with Nicole van der Hoeven about k6, a modern load testing tool built for developers.
Nicole’s contact information:
Twitter: https://twitter.com/n_vanderhoeven
LinkedIn: https://www.linkedin.com/in/nvanderhoeven/
Website: https://nicolevanderhoeven.com/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
161: When an incident happens in a company, what happens? Usually people are running around trying to figure out what is going on and not communicating very well.
Most likely, that is because there is not a clear process for how to handle an incident. This is also an indicator that practicing and preparing for incidents is not part of the company culture.
In this episode, we with speak with Matt Davis and Jake Englund from Blameless about their experiences about how practice can help remediate issues more quickly and why you should do it yourself.
Matt’s info:
LinkedIn: https://www.linkedin.com/in/mattcookedavis/
Jake’s info:
Twitter: https://twitter.com/srejake
LinkedIn: https://www.linkedin.com/in/zeblith/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
160: If you are new to Continuous Integration/Continuous Delivery (CI/CD), you may be a little overwhelmed. There are so many tools and technologies out there to choose from, and it can be difficult knowing where to start. You may have heard of or even tried some of the tools on your own, but without success.
What if we told you that the tools that you need to get started with CI/CD already exist on your laptop?
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
159: In the age of microservices and containers, Kubernetes has become one of the most popular ways to manage application deployment and lifecycle management. However, it can be difficult to know when it's necessary or appropriate to use Kubernetes.
In this episode, we attempt to answer the question "when should I use Kubernetes?" We also talk about the right and wrong ways to use Kubernetes.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
158: Security is a paramount concern for many organizations today due to remote work. The typical starting point is a VPN client is installed on workers devices. But is using a VPN really that secure?
In this episode, we talk with Mike Guthrie from NetFoundry about an alternative approach to security that is not only Zero Trust, but also open source. OpenZiti is an open source project focused on bringing Zero Trust not only to network connect, but also to the communication between applications.
Mike’s contact info:
LinkedIn: https://www.linkedin.com/in/mike-guthrie-b4b4a024/
Twitter: https://twitter.com/mguthrie88
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
157: You're sitting at home and all of a sudden, you have a new business idea. You message a few of your friends and they agree that it is a great idea. You take out a few pieces of paper and start brainstorming. But then you have a bad feeling. The idea is too vague or too complicated to explain or you cannot decide whether to pursue it any further. How do you decide what to do?
In this episode, we speak with Aharale Batonia about what it's like to create and work in a startup and how you might go about creating and running your own startup.
Aharale’s contact info:
LinkedIn: https://www.linkedin.com/in/aharale/
Twitter: https://twitter.com/aharaleb
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
156: When you are writing an API, do you first create an OpenAPI document and then generate code or do you create your code and then generate an OpenAPI document? Regardless of how you create it, how do you know that when your API is running that it is actually doing what you’ve said it will do?
In this episode, we speak with Guy Levinger, CTO of BLST Security, about all things API and about their open source tool named Cherrybomb.
Guy’s information:
Twitter: https://twitter.com/guylevinger1
LinkedIn: https://www.linkedin.com/in/guy-levinger-b8638413a
Website: https://www.blstsecurity.com/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
155: Do you know what the difference is between a project and a product in your day job? After years of working with clients as well as working in open source, we've figured out the differences between a project and a product, why it's important to know the differences, and how you can use this knowledge to build better products.
In this episode, Darin and Viktor walk you through what they are and why they're different, as well as provide insight into how these concepts can impact your day-to-day work.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
154: What are the right and wrong ways organizations help their application developers be more productive? Should those organizations have the mentality of my way or the highway or should they allow the application developers they’ve hired to run the shop?
Interestingly, the answer is somewhere in the middle.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
153: Cloud has been around in an organization for a number of years and has had many, many employees and contractors managing the cloud assets. These assets have been created in numerous ways. Sometimes Terraform was used. Other times, a script was written that used the CLI provided by the cloud vendor. Finally, other assets were created by pointing and clicking in the console.
You’ve been recently hired into this company to fix the mess that they are in. Where are you going to start?
In this episode, we speak with Eran Bibi from Firefly about why you might want to try to get a handle on the unmanaged assets first before you do anything else.
Eran’s info:
LinkedIn: https://www.linkedin.com/in/eran-bibi/
Website: https://www.gofirefly.io/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
152: Many companies are seriously starting to look into creating an internal developer platform for their developers. However, how many of those companies really understand what it takes to create a developer platform that is going to be used by those developers.
We speak with Diogo and Ragnar from Pipedrive to see how they are using the open source project DevSpace as the basis for their internal developer platform.
Diogo’s contact:
LinkedIn: https://www.linkedin.com/in/diogocorreia/
Email: diogo.correia@pipedrive.com
Ragnar’s contact:
LinkedIn: https://www.linkedin.com/in/ragnar-paide/
Email: ragnar.paide@pipedrive.com
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
151: As an application developer, you know you need data about your application. Usually, that data starts with logs. Over time, you add in metrics. At some point, you might add traces. With OpenTelemetry, you get all three with one tool.
In this episode, we speak with Ramon Guiu about the OpenTelemetry landscape and how as an application developer you might want to start using OpenTelemetry in your projects.
Ramon’s info:
Twitter: https://twitter.com/ramonguiu
LinkedIn: https://www.linkedin.com/in/ramonguiu/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
150: Patrick Debois joins us for his almost-annual divide by 50 episode. We talk about items ranging from digital twins to diagrams as code to everyone’s current favorite topics, NFTs and blockchain.
Patrick’s info:
Twitter: https://twitter.com/patrickdebois
LinkedIn: https://www.linkedin.com/in/patrickdebois/
Website: https://www.jedi.be/
Sites discussed:
https://structurizr.com/
https://icepanel.io/
https://c4model.com/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
149: You might just be starting out using cloud and your credit card is doing just fine. However, after a few months, you notice that you need to add multiple credit cards to your account in order to pay your cloud bill. What do you do? You start looking for a better way.
In this episode, we speak with Roi Ravhon, the CEO at Finout, about why a DevOps team should care about their cloud costs.
Roi’s information:
Twitter: https://twitter.com/roiravhon
LinkedIn: https://www.linkedin.com/in/roiravhon/
Website: https://www.finout.io/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
148: The Kubernetes ecosystem continues to mature, but one area is still a challenge. That area is managing storage for stateful applications.
In this episode, we speak with Nic Vermandé from Ondat to discuss the challenges with StatesfulSet applications and the items you've got to get right first before you can even think about scaling your applications to multi-region or even multi-cloud.
Nic’s contact info:
Twitter: https://twitter.com/nvermande
LinkedIn: https://www.linkedin.com/in/vnicolas/
Website: https://www.ondat.io/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
147: In the pre-internet days, you would look through the newspaper when you wanted to get a new job. However, if you wanted to get to a job faster, you would hire a recruiter to help pitch you to multiple companies. In 2022, obviously everything has changed and the value of a good recruiter is move important than ever.
In this episode, we talk with Erin Lovern, the founder and CEO of Grove Talent Group, about how a good recruiter can not only help a person looking for a job, but how a great recruiter can help a company fill positions that they are looking to fill.
Erin’s contact information:
Website: https://grovetalentgroup.com/
Email: erin@grovetalentgroup.com
LinkedIn: https://www.linkedin.com/in/erinlovern/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
146: Who owns security? Is it the Development team? Is it the DevOps or Shared Services team? Is the the Security team?
In this episode, we with speak with Dean Agron from Oxeye to determine what happens when you actually have all the context you need and how that can make the call on what security issues are important to remediate immediately and which ones can wait or even be ignored.
Dean's contact info:
Twitter: https://twitter.com/agrondean
How insecure application tracing and telemetry may lead to sensitive data and PII leakage
https://www.oxeye.io/blog/how-insecure-application-tracing-and-telemetry-may-lead-to-sensitive-data-and-pii-leakage
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
145: In this episode, we discuss a blog post from spike.sh that analyzed 29 DevOps engineer job postings from a number of the large technology companies. The overlap of the job requirements wasn't very surprising. However, some of the requirements seemed pretty silly.
What does a DevOps Engineer do? We analyzed 29 job postings to find out.
https://spike.sh/blog/devops-engineer-responsibilities-analyzed-29-job-postings-to-find-out/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
144: Filippo Valsorda recently wrote a blog post titled “Professional Maintainers: A Wake-up Call" in which he discusses his thoughts about the sustainability of open source. Where do you think open source will be in the coming years?
https://blog.filippo.io/professional-maintainers/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
143: When you are first starting with CI/CD, where should you start? That’s the question that Ahmed asks us in this episode. Should it be tools? Should it be pipelines? Should it be Kubernetes? Actually, the answer is none of the above.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
142: We answer a new variation on a question that we get a lot. Sure, we all know we need to know how to code if we are doing DevOps, but do we also need to know how to use development frameworks and potentially even how to connect to and use databases?
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
141: In this episode, we attempt to answer Stan's question "name five things we should gauge with current employer if they are still doing that would make you leave." What do you think those five things are?
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
140: Have you decided what you're going to be learning in 2022? Darin and Viktor attempt to answer a question from Konstantin about what a DevOps person should be learning this year. Guess what? It's not just technology that you need to be learning.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
139: When you sit down to write documentation, do you start with a Google Doc or Microsoft Word? Hopefully neither. Hopefully you start with plain text. But how do you handle formatting? That's where it starts to get interesting.
In this episode, we answer a question from Karl Webster where he asks "what do you use for documenting all your notes and how do you take notes when learning a new technology / application?"
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
138: It's that time of year where we reflect on everything that happened over the past year and ponder what will be happening over the next year.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
137: Many application developers have either been hearing about or having thrust upon them the concept of shifting left. But now in some places, even infrastructure is trying to get in on the game. However, to believe that application developers can correctly build, maintain, secure, and govern infrastructure is a failed experiment unless they are getting a lot of help. In trying to answer this question from Momodu, we think that we have a few possible actions that organizations can take to take this from failed experiment to a success.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
136: Imagine you've just learned Kubernetes yourself, but now you've been selected to help train a new team member on what Kubernetes is and how to operate it. Where would you start? In this episode, we attempt to answer Dor's question and take you through what we think one of the easiest paths is to learn and teach Kubernetes.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
135: Alexey asked us the following question:
My company is considering migrating everything to Kubernetes. What stack of Kubernetes technologies would you suggest...in 1 minute or less?
It's a good thing that we are a podcast and have the chance to take longer than one minute to answer this question. How many of the suggestions do you agree or disagree with?
The Architect: Bare Metalsson Rejects the Cloud
https://www.youtube.com/watch?v=AXxr0pghWS0
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses: Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
134: In this episode, we attempt to answer the following question from Karan: "How do you make a case to your organization to embrace open source, especially if it has historically favored big vendor-supported tools?"
We discuss not only the money aspect, but a number of other items that might make you think twice before deciding on choosing open source.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
133: Joyce Lin, the head of developer relations at Postman, joins us to discuss why software produced today should be done in a "API First" manner. We talk about what it means for a product to be "API First" and how that process differs from the what typically happens in the real world. Joyce shares her thoughts on emerging trends in the world of APIs and how Postman's own business is being shaped by them.
Joyce's contact info:
Twitter: https://twitter.com/PetuniaGray
LinkedIn: https://linkedin.com/in/joyce-lin
Postman:
https://www.postman.com/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
132: Since around March 2020, we've been working, or trying to work, remotely. That doesn't mean that it has been done efficiently or effectively.
In this episode, we speak with David Burkus, organizational psychologist and the author of Leading from Anywhere, about the struggles that many organizations have had and continue to have even after 18 months.
David's contact info:
Website: https://davidburkus.com/
YouTube: https://www.youtube.com/davidburkus
Twitter: https://twitter.com/davidburkus
LinkedIn: https://linkedin.com/in/davidburkus
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
131: HashiCorp recently did their first-ever State of Cloud Strategy survey. In this episode, Rosemary Wang, developer advocate from HashiCorp, rejoins us to discuss the survey.
Patterns and Practices for Infrastructure as Code
https://www.manning.com/books/patterns-and-practices-for-infrastructure-as-code
Use the code "podparadox20" to save 40% when you purchase the book from Manning.com
HashiCorp State of Cloud Strategy Survey:
https://www.hashicorp.com/state-of-the-cloud
What Everyone Should Know About DevOps, Cloud, or Platform diagram:
https://twitter.com/joatmon08/status/1046745482377273346
HashiCorp State of Cloud Strategy Survey:
https://soundcloud.com/hashicast/episode-34-hashicorp-state-of-cloud-strategy-survey
HashiCast:
https://soundcloud.com/hashicast
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
130: In this episode, we discuss a tweet made by John Cutler about the signs of high work in progress. How many of these do you encounter on a weekly, daily, or hourly basis?
We also discuss a blog post by Chris McEvoy about Kanban gone wrong. The most hilarious one? You'll have to listen to find out.
Signs of High Work in Progress tweet by John Cutler:
https://twitter.com/johncutlefish/status/1434093982368235521
Kanbandoned blog post by Chris McEvoy:
https://usability.typepad.com/confusability/2020/10/kanbandoned.html
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
129: In this listener question episode, we discuss the different ways to develop microservices: fully local, fully remote and hybrid. What do you think the best way is to develop microservices?
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
128: You know that securing environments with a secrets manager is something that needs constant upkeep. Sometimes secrets management can be difficult and complex to handle. Thankfully, there are universal secrets managers which make the process of managing secrets simple for everyone, not just the DevOps and security teams.
Today, we talk with Brian Vallelunga, founder and CEO of Doppler, about how universal secrets management differs from secrets storage and secrets management will be changing over the coming years.
Brian's contact info:
Twitter: https://twitter.com/vallelungabrian
LinkedIn: https://linkedin.com/in/vallelungabrian
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
127: Even though it is 2021, many application development organizations still follow the decades-old process of throwing software over the wall to an operations team to deploy. This practice causes operational difficulties like organizational silos, poor collaboration, and poor user experience.
As software continues to become more complicated, application environments that are properly supported by operations teams will be needed for successful deployment into production.
But what does "properly supported by operations teams" really mean? Does it mean they are processing their Jira tickets faster or does it mean that they have provided services so they are no longer injecting delay into the delivery process?
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
126: If you're like most people, you're probably wondering what "bare metal" means. Turns out, it's a term that's been thrown around for decades. And if you're wondering how it can be applied to something like cloud computing, you might be surprised to find out that it is different than you might think.
In this episode, we speak with Ian McClarty, the president of phoenixNAP, about their bare metal cloud offering and how your organization's profit and loss statement can influence where you host your infrastructure.
A Fun Data Center Tour at phoenixNAP
https://www.youtube.com/watch?v=qUmLnSEVVDw
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
125: Low code is a movement that aims to further automate the development of systems and software. By doing so, it reduces the time spent on building custom applications. Low code is becoming more popular because it provides high-value features with less development time, which ultimately helps companies save money.
In today's episode, we speak with Mike Fitzmaurice, WEBCON's Chief Evangelist, about all things low code and why DevOps usually doesn't even factor in to low code solutions.
Mike's contact information:
Twitter: https://twitter.com/mikefitz
LinkedIn: https://linkedin.com/in/mikefitzmaurice
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
124: If you are an application developer, more than likely you work with some sort of data set. But what do you do when you have sensitive data like credit card numbers, social security numbers or something as simple as a first and last name?
Enter Tonic.ai and their solution: de-identification of data. They take your sensitive data and de-identify it and then they give you a sanitized version of that same data that you can use to do your job without the risk of leaking the real data.
In today's episode, we speak with Adam Kamor, a Co-founder and Head of Engineering of Tonic.ai, about their solution and approach to creating fake data.
Adam's contact information:
Email: hello@tonic.ai
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
123: When you have an application designed using the microservice architecture, where the microservice being developed interact with other services using events from messaging queues and HTTP requests, how can you avoid having all the services on your laptop and still have isolation between different application developers? We will discuss some techniques that can be used to simplify your development process even when you have a complex system with a large number of services.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
122: In this episode, we speak with Randy Abernethy about a number of topics ranging from the costs of digital transformation, how companies are embracing hybrid cloud, and the differences between the Apache Software Foundation (ASF) and the Cloud Native Computing Foundation (CNCF).
Randy's contact information:
Twitter: https://twitter.com/randyabernethy
LinkedIn: https://linkedin.com/in/randyabernethy
Website: https://rx-m.com/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
121: Hooray! You've finally gotten around to implementing your infrastructure as code. But tomorrow is a new day with new problems that you didn't plan for in Day 1. Now what do you have to do in order to continue moving forward? Today, we speak with Tim Davis about day two and many other topics around infrastructure as code.
Tim on Twitter:
https://twitter.com/vtimd
Order your copy of Essential Infrastructure as Code at:
https://www.manning.com/books/essential-infrastructure-as-code
and be sure to use the code "podparadox20" to save 40% off of Essential Infrastructure as Code and any other purchases at Manning Publications.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
120: From everyday conversations to important messages, words have a profound effect on our lives. As we are finding out in today's society (and really throughout time), words really do matter, especially from a technical perspective. But what happens when a word is used out of context or incorrectly? In this episode, we argue that it's time to take a very specific word out of our technical vocabulary.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
119: Many companies are hiring for Developer Advocates. Have you considered making the move from engineering to developer advocacy? Today we talk with Anaïs Urlichs, a SRE that is doing both developer advocacy and engineering at Civo.
Anais' information:
Twitter: https://twitter.com/urlichsanais
YouTube: https://youtube.com/AnaisUrlichs
Website: https://anaisurl.com/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
118: Do you know who your customer is? If you think the answer is "I don't have any customers", you would be wrong. Everyone has awesome customers. The question is are you working tickets for your customers or are you providing a valuable service for your customers?
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
117: Many times, people question why gates exist in business. It's good to question why a gate exists. However, it's not ok to remove a gate without first doing the work necessary to figure out what will happen if the gate is removed.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
116: Individuals typically love to chase the new bright shiny technology objects. However, most enterprises go in the exact opposite direction and want any "new" technology to be fully proven out, i.e. for years, before that technology has a chance to actually be turned into a live production system. How can we help convince management to think differently?
Choose Boring Technology:
https://mcfunley.com/choose-boring-technology
Go Time – Episode #186
https://changelog.com/gotime/186
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
115: Are you still logging in and making manual changes to your servers and applications or have you started on the path to not only no touch production, but to no touch everything? If you aren't moving in that direction, why not?
Security Operations, Reliability, and Securing Google with Heather Adkins
https://cloud.withgoogle.com/cloudsecurity/podcast/security-operations-reliability-and-securing-google-with-heather-adkins/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
114: Are you running your Kubernetes clusters by applying the Oprah effect (you get a cluster...you get a cluster...you get a cluster) or have you finally realized you have neither unlimited cash nor unlimited compute resources? In this episode, we talk about different multitenancy options that are available that you can use with your Kubernetes clusters today.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
113: Are specifications still relevant in today's software development lifecycle? It depends on who you ask..and how old they are. In this episode, we talk with Luca Ingianni about his experiences ranging from a software tester in avionics to his current role working as a consultant and trainer.
Luca's contact information:
https://ingianni.eu
https://www.linkedin.com/in/luca-ingianni
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
112: Are you still clicking around in consoles to create and manage your infrastructure? If so, you'll want to listen to today's episode with Rosemary Wang, the author of Essential Infrastructure as Code.
Order your copy of Essential Infrastructure as Code at:
https://www.manning.com/books/essential-infrastructure-as-code
and be sure to use the code "podparadox20" to save 40% off of Essential Infrastructure as Code and any other purchases at Manning Publications.
Rosemary's contact information:
https://twitter.com/joatmon08
https://linkedin.com/in/rosemarywang
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
111: Ever since Alex Birsan published his Dependency Confusion article in February 2021, the concept of the software supply chain has come to the forefront. The supply chain should not be a new concept to people, but many seemed to have been caught off guard. Today we talk about Alex's article along with a new project that allows you to manage your supply chain security in Tekton.
https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610
https://security.googleblog.com/2021/06/verifiable-supply-chain-metadata-for.html
https://cloud.google.com/blog/products/identity-security/how-were-helping-reshape-software-supply-chain-ecosystem-securely
https://portswigger.net/daily-swig/software-supply-chain-attacks-everything-you-need-to-know
https://www.cisa.gov/publication/software-supply-chain-attacks
https://www.whitesourcesoftware.com/resources/blog/software-supply-chain-attacks/
https://deps.dev/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
110: It seems that everyone thinks that microservices solves every problem that can be imagined. In fact, there's probably a good chance that you don't even want microservices in your organization due to the new problems that they introduce.
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
109: You've made the decision that you're going to drop your monoliths and move to microservices. Have you given any consideration how you are going to test your microservices? Beyond that, have you thought about how you can make testing easy for the consumers of your microservices?
Transcript:
https://www.devopsparadox.com/episodes/how-to-test-microservices-109/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
108: If you cannot define a thing, how do you know what it is? Is a microservice a function, a container, a VM, all of the above or none of the above? Today, we give you our definition of what a microservice is and where microservices should fit into your application architecture.
Transcript:
https://www.devopsparadox.com/episodes/why-do-we-want-to-use-microservices-108/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
107: As a software development community, we're used to hearing the terms sprints, projects, and agile. However, the people that sign our paychecks, in other words, the business people, could care less and wonder why everything is taking so long and why it is so complex. Today, we speak with Steve Pereira, the found of Visible.is, a consulting firm focused on value streams, and flow engineering, about what he sees when he speaks with his clients.
Visible:
https://visible.is/
Steve's info:
LinkedIn:
https://www.linkedin.com/in/devopsto
Twitter:
https://twitter.com/SteveElsewhere
Transcript:
https://www.devopsparadox.com/episodes/getting-into-the-flow-with-value-streams-107/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
106: There seems to be a great debate about what a DevOps engineer is and what a SRE is. Today, we throw our hat in the ring and attempt to dispel the myths that we see running rampant throughout the industry.
Viktor's video for "What is the difference between SRE and DevOps?":
https://www.youtube.com/watch?v=jgW4r9FxItI
Transcript:
https://www.devopsparadox.com/episodes/the-difference-between-sre-and-devops-106/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
105: The following quote is attributed to Mark Twain, "History does not repeat itself, but it rhymes." Does this sound familiar? VMs. LXC. Containers. They are all (roughly) the same thing. So why do we keep recreating things that already exist?
Transcript:
https://www.devopsparadox.com/episodes/does-history-repeat-itself-105/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
104: When a business decides to release code to production that hasn't been fully tested or is releasing because a date has been promised, that's a business decision and not a technical decision. However, at some point in the future, the debt will come due. Today, we speak with Dan Burns from Testifi about TDD, BDD, and why an organization must apply test automation the correct way or they'll find themselves playing catchup all the time.
Dan's contact information:
https://linkedin.com/in/danburns6
https://testifi.io/
Transcript:
https://www.devopsparadox.com/episodes/technical-debt-is-a-business-decision-104/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
103: What is there was a way that you could harness the power of Kubernetes without having to learn all the ins and outs of Kubernetes? Enter Knative. Today with speak with Jacques Chester, the author of Knative in Action, about that at much more.
Order your copy of Knative in Action at:
https://www.manning.com/books/knative-in-action
and be sure to use the code "podparadox20" to save 40% off of Knative in Action and any other purchases at Manning Publications.
Jacques on Twitter:
https://twitter.com/jacques_chester
Transcript:
https://www.devopsparadox.com/episodes/knative-in-action-103/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
102: Are you a rule-maker or a rule-breaker? Hopefully we all agree that having guardrails up help us live a better life, whether personally or professionally. However, sometimes those rules get in our way of getting things done. Today, we take an introductory look at Open Policy Agent and Gatekeeper and try to figure out how using Gatekeeper can make not only our lives but the lives of our end users much easier when managing our Kubernetes clusters.
Transcript:
https://www.devopsparadox.com/episodes/getting-started-with-open-policy-agent-102/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
101: What happens when you're doing a demo and your technology fails? You can get angry and write a blog post that goes viral. Today, we speak with Nicolas Frankel about his move from minikube to Kind, how Gradle is no better than Ant, and how the conference circuit is not meant for people that only want to work from 9 to 5.
Nicolas on Twitter:
https://twitter.com/nicolas_frankel
Transcript:
https://www.devopsparadox.com/episodes/what-to-do-when-technology-fails-101/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
100: In our 100th episode, we bring back Patrick Debois, the GodFather of DevOps (at least we think so), as our "divide by 50" guest. In very Patrick fashion, he turns the tables on us and we go down a number of paths that we didn't see coming.
Patrick's info:
Twitter: https://twitter.com/patrickdebois
Website: http://www.jedi.be/
Transcript:
https://www.devopsparadox.com/episodes/course-correcting-devops-100/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
99: In the nineties and early 2000s, it wasn't strange to see operations people copy and pasting "code" from Word documents, also known as runbooks, into their terminals to get their job done. It's now 2021 and we still have people questioning whether or not they should be writing code to do their work.
Transcript:
https://www.devopsparadox.com/episodes/do-devops-engineers-need-to-know-how-to-code-99/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
98: How many times have you been put into the situation to debug a production issue and you have no idea where to start? Probably more than you can count. Worse yet, your employer expects that you can troubleshoot the issue without having access to all the tools that you need. Today we speak with Itiel Shwartz, CTO and co-founder of Komodor, a startup developing the next-gen troubleshooting platform for Kubernetes.
Itiel's contact information:
https://twitter.com/itielshwartz
https://linkedin.com/in/itiel-shwartz-18542853
https://komodor.com/
Transcript:
https://www.devopsparadox.com/episodes/kubernetes-troubleshooting-simplified-with-komodor-98/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
97: A chess player knows to write down their moves so they can replay their matches and learn from them. Having the ability to replay those matches also gives you the ability to start over and see where something goes wrong. In today's episode, we speak with Viktor (Vik) Gamov about Apache Kafka and how it can help you breathe new life into systems that may not have been written in a way to take advantage of events.
Vik on Twitter:
https://twitter.com/gamussa
Transcript:
https://www.devopsparadox.com/episodes/processing-event-streams-with-apache-kafka-97/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
96: With the advent of software like Crossplane, we are beginning to see the Kubernetes API coming more to the forefront. In today's episode, we attempt to tackle why it appears that events are still not completely understood.
Crossplane:
https://crossplane.io/
Transcript:
https://www.devopsparadox.com/episodes/the-kubernetes-api-is-becoming-omnipresent-96/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
95: You would think in 2021, we still wouldn't be having this conversation. However, it happens everyday. Should everything be automated? You might surprised at our answer.
Transcript:
https://www.devopsparadox.com/episodes/should-everything-be-automated-95/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
94: Some people like reading text. Some people like watching videos. Which one are you when it comes to learning and building your skillset? Today, we talk about what we like as both producers and consumers of content.
Transcript:
https://www.devopsparadox.com/episodes/are-videos-or-text-better-for-learning-94/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
93: Many times, probably most, people don't leave your company only for more money. There's usually more to it than that. Today we discuss different things that a company can do to keep people from leaving that normally would.
Transcript:
https://www.devopsparadox.com/episodes/creating-a-healthy-working-environment-93/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
92: On this podcast, we spend a lot of time discussing backend and infrastructure. Today, we speak with Grady Saccullo, a front end developer for Cycle, a container orchestration platform. We talk about what it's like to work in a smaller shop in 2021 and how some workflows are very different than much larger enterprises.
Grady on LinkedIn:
https://linkedin.com/in/grady-saccullo
Transcript:
https://www.devopsparadox.com/episodes/frontend-vs-backend-development-in-2021-92/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
91: The Docker of 2021 is not the same as the Docker of 2016, especially when it comes to the tools around the Kubernetes ecosystem. Today, we talk about how Docker Compose should not be used to manage Kubernetes and how you should be developing Kubernetes based applications in 2021.
Kaniko - Building Container Images In Kubernetes Without Docker
https://www.youtube.com/watch?v=EgwVQN6GNJg
Followup blog post from Tobias:
https://powdrsoft.com/blog/k8s/docker-compose-on-k8s/
Tobias on Twitter:
https://twitter.com/teericsson
Transcript:
https://www.devopsparadox.com/episodes/its-past-time-to-abandon-docker-compose-91/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
90: Email. Slack. Kubernetes. These things have at least one thing in common. They are all event-driven. Even if you don't agree with that statement, we can agree that asynchronous development has taken off in the past few years, thus exploding the concepts of event-driven. We are now starting to see these concepts arriving in tooling space. We speak with Andi Grabner about Keptn, an event-based control plane for continuous delivery and automated operations for cloud-native applications.
Keptn on Twitter:
https://twitter.com/keptnProject
Andi on Twitter:
https://twitter.com/grabnerandi
Transcript:
https://www.devopsparadox.com/episodes/event-driven-continuous-delivery-with-keptn-90/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
89: 2020 is in the rear view mirror. 2021 is out the front windshield. The items that are going to be the most important are going to be those items that are the most irrelevant. In today's episode, we try to unwind what that means and why it matters to you.
Transcript:
https://www.devopsparadox.com/episodes/2021-the-year-of-the-irrelevant-89/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
88: 2020 was quite a year. Your year may have been great or it may have been horrible. Hopefully it trended towards great, even if did not live up to your expectations. In today's episode, we look back over some of the items that we encountered and that you probably did too.
Transcript:
https://www.devopsparadox.com/episodes/devops-in-2020-year-in-review-88/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
87: This is a little different episode. With it being Christmas week, Darin and Viktor take a step back and think about all the things that they are grateful for in this crazy year that is 2020.
Transcript:
https://www.devopsparadox.com/episodes/god-bless-us-everyone-87/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
86: Just because you are running your application on Kubernetes, that doesn't mean it was simple to get to that outcome. Today, we speak with Alan Barr about how his company is trying to not only make Kubernetes operationally simple, but also how it is important to also make it simple for application developers to use.
https://www.alanmbarr.com/blog/internal-developer-platform/
Alan's information:
LinkedIn: https://linkedin.com/in/alanmbarr
Transcript:
https://www.devopsparadox.com/episodes/your-internal-developer-platform-sucks-86/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
85: It's simple to quantify the hard costs of DevOps. Labor. Hardware. Software. However, it's a lot harder to calculate the hidden costs of DevOps. Today we talk with Yuval Oren about what he is seeing in the industry and how technical debt may be the answer to your problems.
Yuval's information:
Twitter: https://twitter.com/yuvalo
Transcript:
https://www.devopsparadox.com/episodes/the-hidden-costs-of-devops-85/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
84: In these times, everyone is familiar with Slack and Microsoft Teams. However, there are other companies that offer similar solutions. Today, we talk with PJ Hagerty from Mattermost and find out how Mattermost sets itself apart from its competitors.
PJ's information:
Twitter: https://twitter.com/aspleenic
Transcript:
https://www.devopsparadox.com/episodes/mattermost-saves-a-30-year-old-d-d-campaign-84/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
83: When Spring Framework appeared on the scene over 18 years ago (October 1, 2002), the public cloud was just a glimmer in the eyes Amazon, Google, and Microsoft. Fast forward to today. Spring has adapted over its lifetime and still is considered the industry standard for Java development. Today, we speak with the Thomas Vitale, author of "Cloud Native Spring in Action" from Manning Publications.
Order your copy of "Cloud Native Spring in Action" by clicking on the link below.
Don't forget to use the discount code "podparadox20" to save 40%!
https://www.manning.com/books/cloud-native-spring-in-action
Thomas' information:
Twitter: https://twitter.com/vitalethomas
LinkedIn: https://www.linkedin.com/in/vitalethomas
Transcript:
https://www.devopsparadox.com/episodes/using-spring-to-develop-cloud-native-applications-83/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
82: Today we speak with Olaf Molenveld, the CTO of Vamp.io, a Cloud-Native AIOps platform that provides self-service release and cost optimization capabilities. We discuss numerous items from should where you live determine your salary to why does ColdFusion still exist.
Olaf's information:
Twitter: https://twitter.com/olafmolenveld
LinkedIn: https://linkedin.com/in/olafmolenveld
Transcript:
https://www.devopsparadox.com/episodes/where-you-live-shouldnt-define-your-pay-82/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
81: Today we speak with Christine Spang, CTO and co-founder of Nylas. We discuss the problems that Nylas solves for application developers so they don't have to figure out how to integrate with numerous email and calendar providers.
Christine's information:
Twitter: https://twitter.com/spang
Nylas: https://www.nylas.com/
Transcript:
https://www.devopsparadox.com/episodes/making-email-provider-integration-simple-with-nylas-81/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
80: When you're first starting out in your business, you're probably going to outsource a lot of things, like HR, payroll and even server hosting. However, over time, you might start pulling some things back in house. The question is should you bring those items back in over time and, if so, when should you do it?
Transcript:
https://www.devopsparadox.com/episodes/what-should-i-outsource-to-a-managed-solution-80/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
79: In this episode, we with speak with Ant Weiss from Otomato about the differences between continuous integration and build automation. We also dig into what it takes to culturally change an organization to succeed at continuous delivery.
Ant's information:
https://antweiss.com/
https://twitter.com/antweiss
https://linkedin.com/in/antonweiss
Transcript:
https://www.devopsparadox.com/episodes/are-you-doing-ci-cd-or-none-of-the-above-79/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
78: Today we with speak with Adam Hawkins, a SRE for Skillshare and the host of the Small Batches podcast. We discuss what it's like to be a day-to-day SRE and how some companies still don't understand that it is possible to actually follow the "you build it, you run it" model of software development.
Small Batches podcast:
https://smallbatches.fm/
Transcript:
https://www.devopsparadox.com/episodes/a-day-in-the-life-of-a-sre-78/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
77: The unsung hero of any company. The NOC engineer. But what happens if your most skilled NOC engineer is on vacation and there was no backup for him? Enter NOC as a Service. Today, we talk with Avi Shalisman and Asaf Matyas from Xiteit to understand how NOC as a Service can minimize risk so your favorite NOC engineer taking a vacation.
Transcript:
https://www.devopsparadox.com/episodes/noc-as-a-service-with-xiteit-77/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
76: We know that there are numerous ways to provision infrastructure. Today, we talk with Joe Duffy, the CEO of Pulumi, about how everyone can become a cloud engineer using Pulumi.
https://www.pulumi.com/
https://cloudengineeringsummit.com/
Transcript:
https://www.devopsparadox.com/episodes/how-to-be-a-cloud-engineer-with-pulumi-76/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
75: Declarative, imperative, CSV, JSON, and YAML. Do any of these items represent code? We attempt to answer that question in today's episode.
Transcript:
https://www.devopsparadox.com/episodes/what-is-code-75/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
74: Many people today are still clicking around in consoles and copy and pasting instructions from Word documents. Today, we make the case for changing your workflows to incorporate GitOps to minimize risk in managing your environments.
Transcript:
https://www.devopsparadox.com/episodes/using-gitops-in-your-devops-workflow-74/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
73: If you don't want to run Elasticsearch for logging for your Kubernetes cluster, what do you do? As we found out from Vadim, one of our community members, the answer today is Loki.
Transcript:
https://www.devopsparadox.com/episodes/logging-with-loki-73/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
72: In this episode, we speak with Gigi Sayfan, the author of Mastering Kubernetes. We speak with him about where Kubernetes is today and where he thinks it is headed in the future.
https://www.packtpub.com/product/mastering-kubernetes-third-edition/9781839211256
Transcript:
https://www.devopsparadox.com/episodes/mastering-kubernetes-with-gigi-sayfan-72/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
71: Observability can be broken down into three layers; software, infrastructure, and knowledge. Which of these things do you think is most important? Today, we discuss these items and more with Yotam Atad and Chen Goldberg from CloudWize.
Transcript:
https://www.devopsparadox.com/episodes/observability-in-the-cloud-with-cloudwize-71/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
70: Some people believe that high availability means 100% availability. That just isn't true. We attempt to disprove this age old myth in today's episode.
Transcript:
https://www.devopsparadox.com/episodes/high-availability-does-not-mean-100-availability-70/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
69: Google Cloud Run vs Azure Container Instances vs AWS ECS. We discuss the pros and cons of each Containers as a Service solution in today's episode.
Transcript:
https://www.devopsparadox.com/episodes/is-containers-as-a-service-serverless-69/#transcript
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
https://www.devopsparadox.com/contact/
68: Docker recently announced integrations with Azure Container Instances (ACI) and Amazon EC2 Container Service (ECS) that makes it simple for developers to use native Docker commands to interact with these services. Darin and Viktor discuss why this is a very big deal not only for Docker, but for the ecosystem as a whole.
Transcript:
https://www.devopsparadox.com/episodes/is-docker-back-68/#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Slack:
https://www.devopsparadox.com/slack
Connect with us at:
https://www.devopsparadox.com/contact
67: We step away from serverless for a week to visit with Uma Mukkara about LitmusChaos. We discuss the origin story and how MayaData uses LitmusChaos on their SaaS platform to keep everything running so they can sleep at night.
Transcript:
https://www.devopsparadox.com/episodes/orchestrating-chaos-on-kubernetes-using-litmuschaos-67/#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Slack:
https://www.devopsparadox.com/slack
Connect with us at:
https://www.devopsparadox.com/contact
66: Viktor has finished the next section of the Catalog course. Today, we discuss the amazing, and not so amazing, use cases where you should use managed Functions as a Service in 2020.
Transcript:
https://www.devopsparadox.com/episodes/aws-lambda-vs-google-cloud-functions-vs-azure-functions-for-2020-66#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Slack
https://www.devopsparadox.com/slack
Find our contact information at:
https://www.devopsparadox.com/contact
65: Today we talk with Rodric Rabbah, creator and the lead contributor to Apache OpenWhisk as well as the CTO and co-founder of Nimbella, a serverless cloud platform.
Rodric's info:
Twitter: https://twitter.com/rabbah/
LinkedIn: https://www.linkedin.com/in/rodric/
GitHub: https://github.com/rabbah/
Website: https://rabbah.io
Transcript:
https://www.devopsparadox.com/episodes/serverless-made-easy-with-nimbella-65#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Slack
https://www.devopsparadox.com/slack
Find our contact information at:
https://www.devopsparadox.com/contact
64: In this next episode about serverless, we tackle the question if we should be using serverless or not. Our answer may surprise you.
Transcript:
https://www.devopsparadox.com/episodes/do-we-really-want-to-use-serverless-64#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Slack
https://www.devopsparadox.com/slack
Find our contact information at:
https://www.devopsparadox.com/contact
63: In this first episode about serverless, we attempt to define the fundamentals of serverless in 2020.
Transcript:
https://www.devopsparadox.com/episodes/serverless-101-63#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Slack
https://www.devopsparadox.com/slack
Find our contact information at:
https://www.devopsparadox.com/contact
62: We welcome back Ádám Sándor to continue our discussion about Kubernetes, Serverless and developer productivity.
Ádám's info:
https://twitter.com/adamsand0r
https://www.linkedin.com/in/adamsandor/
Transcript:
https://www.devopsparadox.com/62#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Slack
https://www.devopsparadox.com/slack
Find our contact information at:
https://www.devopsparadox.com/contact
61: Today with talk with Mikolaj (Miko) Pawlikowski, the creator of PowerfulSeal and the author of the new Manning book "Chaos Engineering: Crash Test Your Applications". We go through the how PowerfulSeal came to be and where Miko thinks chaos landscape will be in a few years. Be sure to listen all the way to the end of the episode for a chance to receive a code to get Miko's book for free.
Miko's book ==> Chaos Engineering: Crash Test Your Applications
https://www.manning.com/books/chaos-engineering?query=Mikolaj%20Pawlikowski
Use the discount code "podparadox20" to get 40% off!
Viktor's picture:
https://www.devopsparadox.com/viktors-room
Miko's Twitter:
https://twitter.com/mikopawlikowski
PowerfulSeal:
https://bloomberg.github.io/powerfulseal/
Chaos Engineering Newsletter:
https://chaosengineering.news/
Tech At Bloomberg:
https://twitter.com/TechAtBloomberg
https://www.techatbloomberg.com/blog/powerfulseal-testing-tool-kubernetes-clusters/
Transcript:
https://www.devopsparadox.com/61#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
The DevOps 2.6 Toolkit: Jenkins X
https://www.devopstoolkitseries.com/posts/devops-26/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
60: As a followup from last week's episode, we talk about the specific problems that Jenkins X solves.
Transcript:
https://www.devopsparadox.com/60#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
The DevOps 2.6 Toolkit: Jenkins X
https://www.devopstoolkitseries.com/posts/devops-26/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
59: Recently, Viktor has been hearing a number of people talking about choosing to use native services within cloud providers for their business applications instead of using Kubernetes. We attempt to tackle this flawed mindset.
Transcript:
https://www.devopsparadox.com/59#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
The DevOps 2.6 Toolkit: Jenkins X
https://www.devopstoolkitseries.com/posts/devops-26/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
58: We get the tables turned on us today by one of the Docker Captains, Nirmal Mehta. We discuss numerous items ranging from biases, fallacies and Jurassic Park.
Nirmal on Twitter:
https://twitter.com/normalfaults
Nirmal on the Friday livestream from 15May2020:
https://youtu.be/7GgyM6RZdvI
Transcript:
https://www.devopsparadox.com/58#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
The DevOps 2.6 Toolkit: Jenkins X
https://www.devopstoolkitseries.com/posts/devops-26/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
57: On this episode, we have a conversation with Tracy Miranda, the current chair of the Governing Board of the Continuous Delivery Foundation.
Tracy on Twitter:
https://twitter.com/tracymiranda
Continuous Delivery Foundation:
https://cd.foundation/
https://twitter.com/cdeliveryfdn
Transcript:
https://www.devopsparadox.com/57#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
The DevOps 2.6 Toolkit: Jenkins X
https://www.devopstoolkitseries.com/posts/devops-26/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
56: We have a conversation with one of our listeners who challenges us on some previous comments that we've made on the necessity of growing your skills.
Joost on Twitter:
https://twitter.com/joost_vdg
Transcript:
https://www.devopsparadox.com/56#transcript
YouTube channel:
https://youtube.com/devopsparadox
Books and Courses:
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
The DevOps 2.6 Toolkit: Jenkins X
https://www.devopstoolkitseries.com/posts/devops-26/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
55: What's it like to actually operate multiple Kubernetes clusters at a global scale? We chat with Carlos Sanchez about his experiences and his love for progressive delivery. You may also be surprised at one of his favorites tools to use.
Carlos on Twitter:
https://twitter.com/csanchez
Transcript:
https://www.devopsparadox.com/55#transcript
Books and Courses:
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
The DevOps 2.6 Toolkit: Jenkins X
https://www.devopstoolkitseries.com/posts/devops-26/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
54: We recently released a course on Chaos Engineering. Today, we speak with Russ Miles and Sylvain Hellegouarch, a couple of the team members behind the ChaosToolkit open source project.
Russ' article discussed during the episode:
https://medium.com/chaosiq/pre-requisites-to-practicing-reliability-23b9a459e1bd
Russ' Twitter:
https://twitter.com/russmiles
Sylvain's Twitter:
https://twitter.com/lawouach
ChaosIQ:
https://chaosiq.io/
Transcript:
https://www.devopsparadox.com/54#transcript
Books and Courses:
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
The DevOps 2.6 Toolkit: Jenkins X
https://www.devopstoolkitseries.com/posts/devops-26/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
53: Recently, the governor of New Jersey made a plea for COBOL programmers to help maintain the state's unemployment system. In this episode, we discuss the ramifications of not taking the maintenance of your systems seriously.
https://www.theverge.com/2020/4/14/21219561/coronavirus-pandemic-unemployment-systems-cobol-legacy-software-infrastructure
https://twitter.com/kjhealy/status/1246605999131316226
https://komonews.com/news/local/new-pictures-reveal-cracking-cement-forcing-closure-of-west-seattle-bridge
Transcript:
https://www.devopsparadox.com/53#transcript
Books and Courses:
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
The DevOps 2.6 Toolkit: Jenkins X
https://www.devopstoolkitseries.com/posts/devops-26/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
52: It's not uncommon to see software vendors bashing competitor's products. Recently, Viktor had this happen to the product that he manages. This episode is about what happens next and how you should react if it ever happens to you.
Transcript:
https://www.devopsparadox.com/52#transcript
Books and Courses:
Kubernetes Chaos Engineering With Chaos Toolkit And Istio
https://www.devopstoolkitseries.com/posts/chaos/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.devopstoolkitseries.com/posts/canary/
The DevOps 2.6 Toolkit: Jenkins X
https://www.devopstoolkitseries.com/posts/devops-26/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
51: After a short Twitter fight with Viktor, we asked Ádám Sándor to join us to discuss his position that Kubernetes is not too hard for developers to learn.
Ádám's contact information:
https://twitter.com/adamsand0r
https://www.linkedin.com/in/adamsandor/
Transcript:
https://www.devopsparadox.com/51#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
50: For our 50th episode, we talk with the godfather of Patrick Debois. We talk about many things ranging from DevOps in a fully remote environment to the Muppets.
Patrick's information:
https://twitter.com/patrickdebois
http://www.jedi.be/
AllTheTalks.online:
https://www.allthetalks.online/
Transcript:
https://www.devopsparadox.com/50#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
49: Amid the coronavirus pandemic, many businesses have implemented their business continuity plans. Part of those plans include remote work. Today, we talk about both of our experiences with remote work and what are the chances are that remote work will become the new normal for knowledge workers.
https://stayinghome.club/
https://about.gitlab.com/blog/2020/03/06/resources-for-companies-embracing-remote-work/
YouTube recording (if you want to see us talking):
https://youtu.be/fIwiXReWWEw
Transcript:
https://www.devopsparadox.com/49#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
In this bonus episode of DevOps Paradox, we talk with James Rawlings and James Strachan about the challenges in doing continuous delivery in Kubernetes.
Twitter:
https://twitter.com/jstrachan
https://twitter.com/jdrawlings
Watch the replay on YouTube:
https://youtu.be/9ZjqQNgNYe4
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
48: Today we have a conversation with two consultants that work in the financial sector in London. Also, we discover that unicorns live on islands of happiness and have pockets of excellence.
Transcript:
https://www.devopsparadox.com/48#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
In this bonus episode of DevOps Paradox, we talk with Mislav Stipetic of MSB (Magic Sandbox) to talk about their platform that makes learning Kubernetes easy.
https://www.msb.com/
Watch the replay on YouTube:
https://youtu.be/vhuYF8_ejX8
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
47: You want to do the right thing for your clients, but you can't because your manager won't let you. What kind of excuse is that? Are you a 3 year old? In this episode, we go deep into why it's up to you, not someone else, to make the right decision when your role starts getting hard.
Transcript:
https://www.devopsparadox.com/47#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
46: Today we have a conversation with Phil Estes, a Distinguished Engineer for IBM as well as one of the maintainers of the containerd project. We discuss a number of items including image signing and a hopeful distribution spec release for 2020.
Find Phil at:
https://twitter.com/estesp
https://github.com/estesp
https://estesp.dev
Project Harbor:
https://goharbor.io/
OCI = Open Container Initiative:
https://www.opencontainers.org/
OCI TOB = Technical Oversight Board:
https://github.com/opencontainers/tob
OCI/CNCF Notary V2 (Image Signing standardization):
https://hackmd.io/_vrqBGAOSUC_VWvFzWruZw?view#Notary-v2-Meeting-Notes
Transcript:
https://www.devopsparadox.com/46#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
45: Unless you're a Kubernetes administrator, why should you bother learning everything about Kubernetes? Our answers may surprise you.
Transcript:
https://www.devopsparadox.com/45#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
44: What happens when your company is not allowed to run anything in the cloud and must run everything on premise? What can you do get get the best of both worlds? We'll attempt to answer these questions in today's episode.
Transcript:
https://www.devopsparadox.com/44#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
43: Many times we are asked how to implement continuous testing on top of continuous delivery. Today, we talk about how there is, in isolation, no such thing as continuous testing. We also discuss the concepts of "delayed delivery" and "executable documentation".
Transcript:
https://www.devopsparadox.com/43#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
42: As a company grows, it's not unexpected to see executive leadership change. However, those personnel changes mean different things to different people, both internal and external. We discuss the far reaching implications of those changes.
Transcript:
https://www.devopsparadox.com/42#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
41: In today's episode, we talk about the evils (and not so evils) of UIs in their many different forms.
Transcript:
https://www.devopsparadox.com/41#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
40: We've heard about Continuous Integration, Continuous Delivery, and Continuous Deployment. Today, with the help of our guest Eric Mizell, we discuss Continuous Reliability.
Eric's information:
LinkedIn: https://www.linkedin.com/in/eric-mizell-8864977/
Email: eric.mizell@overops.com
Twitter: https://twitter.com/EricMizell
DevNexus video: https://blog.overops.com/video-continuous-reliability-an-agile-process-to-deliver-higher-quality-applications/
Canary Deployments To Kubernetes Using Istio and Friends
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?referralCode=75549ECDBC41B27D94C4
Transcript:
https://www.devopsparadox.com/40#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
39: Is it possible that the biggest contribution from the Kubernetes project isn't container scheduling, but the Kubernetes API itself?
Transcript:
https://www.devopsparadox.com/39#transcript
Books and Courses:
https://www.devopstoolkitseries.com/
Canary Deployments To Kubernetes Using Istio and Friends is still on sale for $13.99 with the link below (coupon and price expires 27-Jan-2020 10:01 AM PT)
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?couponCode=7F311AD2C040117054AB
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
38: How important do you think you are to your company? It only takes one decision and you'll find out. In this episode, we step on more toes than normal.
Books and Courses:
https://www.devopstoolkitseries.com/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
37: We take a walk through the continuum of deployment strategies.
Canary Deployments To Kubernetes Using Istio and Friends
$13.99 with the link below (coupon and price expires 27-Jan-2020 10:01 AM PT)
https://www.udemy.com/course/canary-deployments-to-kubernetes-using-istio-and-friends/?couponCode=7F311AD2C040117054AB
Books and Courses:
https://www.devopstoolkitseries.com/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
36: Welcome to 2020! We make 4 predictions for the upcoming year. How many of them do you agree or disagree with?
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
35: We look back at many of the topics of the past year. And yes, we still continue to ramble.
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
34: Today we dig into what we believe the current state of Docker is and where we think they are headed.
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
33: This was supposed to be the results show for which managed Kubernetes service sucks the least. Well, life got in the way. Listen to today's episode to get the inside scoop of what happened. We also delve into what happens when there are massive changes in technology and how most people deal with it.
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
32: We begin the discussion about how to determine which managed Kubernetes service sucks the least.
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Find our contact information at:
https://www.devopsparadox.com/contact
31: We tackle the role of shared service teams in an organization's DevOps culture. We also attempt to define what are "DevOps rules".
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Contact us at:
https://www.devopsparadox.com/contact
Viktor has arrived back from KubeCon 2019. We talk about everything that happened from his perspective. We also touch on the Mirantis acquisition of Docker's Enterprise business.
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Contact us at:
https://www.devopsparadox.com/contact
30: Matt Turner joins us today to discuss his role as a day-to-day site reliability engineer practitioner at Ziglu. He also tells us a cautionary tale that everyone should listen to.
If you are in the London financial district, you might be interested in working with Matt at Ziglu:
https://www.ziglu.io/careers
The Site Reliability Engineering books from Google: https://landing.google.com/sre/books/
Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps Toolkit Series by Viktor Farcic: https://www.devopstoolkitseries.com/
Join the Slack team:
http://slack.devops20toolkit.com/
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Twitter:
Matt: https://twitter.com/mt165
Darin: https://twitter.com/darinpope
Viktor: https://twitter.com/vfarcic
DevOpsParadox: https://twitter.com/DevOpsParadox
LinkedIn:
Darin: https://www.linkedin.com/in/darinpope/
Viktor: https://www.linkedin.com/in/viktorfarcic/
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
29: We speak with Philipp Krenn today about Elasticsearch. We go through it's history and some of the more interesting stories where it has been used.
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Twitter:
Peter: https://twitter.com/xerra
Darin: https://twitter.com/darinpope
Viktor: https://twitter.com/vfarcic
DevOpsParadox: https://twitter.com/DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
28: Peter Jausovec joins us today to talk all things service mesh. We also break out the crystal ball and make some predictions about Kubernetes for 2020.
Service Mesh Patterns at Riga Dev Days:
https://youtu.be/jQsgVeT8MnI
Service Mesh Interface:
https://smi-spec.io/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Twitter:
Peter: https://twitter.com/pjausovec
Darin: https://twitter.com/darinpope
Viktor: https://twitter.com/vfarcic
DevOpsParadox: https://twitter.com/DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
27: We discuss one of the greatest B movies ever and how it relates to one of the more recent Docker security issues.
Graboid: First-Ever Cryptojacking Worm Found in Images on Docker Hub
https://unit42.paloaltonetworks.com/graboid-first-ever-cryptojacking-worm-found-in-images-on-docker-hub/
Tremors:
https://www.imdb.com/title/tt0100814/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
26: In this episode, we propose that the architect role is useless within most companies. We also tackle having non-technical people in technical roles.
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
25: We discuss difference conference types and the pros and cons of each.
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at: https://www.devopsparadox.com/
24: We discuss numerous deployment strategies, ranging from blue/green to serverless.
Also, it appears we have our first real fight on our hands. You decide.
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at: https://www.devopsparadox.com/
23: Today we speak with Erez Rusovsky from Rollout and talk all things feature flags. Who knew that code injection as a service could be so cool?
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
22: In today's episode, we answer Neven's question about what motivates us to learn, work, and write.
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
21: Neven asks us how we organize time for work, learning, and new stuff we’d like to try. We talk about some tools and tips that we both use. We also learn some of the key secrets about how Viktor is able to crank out so many books.
Remember The Milk:
https://www.rememberthemilk.com/
Trello:
https://trello.com/
Full Focus Planner by Michael Hyatt:
https://fullfocusplanner.com/
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Leave us a message on Voxer:
https://web.voxer.com/u/devopsparadox
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
20: In our first guest episode, John Laffey joins us to discuss his disagreements with our episode about configuration management. Can we keep it a good, clean fight? You be the judge.
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Leave us a message on Voxer: https://web.voxer.com/u/devopsparadox
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
19: What are the big differences between hackers and developers? Our answers may surprise you.
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
18: Neil Gealy asks "What is the best way to track features, bugs, etc, going into a release for visibility to the rest of the company (outside the development team)? And how do you incorporate that into release notes and versioning of your microservices. I've seen companies using a combination of Jira and spreadsheets, but they are very clunky and manual."
https://devops20.slack.com/archives/CK3906Q1K/p1565655300018600
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Connect on Voxer
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
17: Ivor asks "How do you like to learn? People that like to learn have their own style. What's yours?"
https://twitter.com/ivorsco77/status/1154039680603529218
Design Patterns: Elements of Reusable Object-Oriented Software by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides:
https://www.amazon.com/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612/
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Email:
Darin: darin@planetpope.com
Viktor: viktor@farcic.com
Visit us at:
https://www.devopsparadox.com/
16:Vadim asks "when will we automate ourselves out of our jobs?"
Fire Someone Today by Bob Pritchett:
https://www.amazon.com/gp/product/B004GJVXKC/
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Visit us at: https://www.devopsparadox.com/
15: Silos exist throughout enterprises. We discuss if silos are bad or good and everything in between.
Here's the question from Joost:
https://www.linkedin.com/feed/update/urn:li:activity:6559101458564866048?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A6559101458564866048%2C6559335225585913856%29
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Twitter:
Darin: @darinpope
Viktor: @vfarcic
DevOpsParadox: @DevOpsParadox
Visit us at: https://www.devopsparadox.com/
14: We take our first listener question and it's all about GitOps.
Here's the question from Andrey:
https://www.linkedin.com/feed/update/urn:li:activity:6559101458564866048?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A6559101458564866048%2C6559134063964246016%29
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Twitter:
@darinpope
@vfarcic
@DevOpsParadox
Visit us at: https://www.devopsparadox.com/
13: With apologies to Shakespeare...to have opinions or not to have opinions? That is the question.
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Join the Slack team:
http://slack.devops20toolkit.com/
Visit us at: https://www.devopsparadox.com/
If you'd like to reach out, you can find us on Twitter:
@vfarcic
@darinpope
@DevOpsParadox
12: Viktor is back from a recent trip through Asia. One of the things he encountered was the surprising "lack" of English throughout the region. We discuss if English should be a requirement to be a developer in today's global economy and how that parallels many of the problems found in enterprises.
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
Signup for access to the DevOps20 Slack workspace:
http://slack.devops20toolkit.com/
Visit us at: https://www.devopsparadox.com/
If you'd like to reach out, you can find us on Twitter:
@vfarcic
@darinpope
@DevOpsParadox
11: We discuss a lot of different angles of serverless, including why it's a smart thing for you to start looking into serverless today.
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
DevOps20 Slack workspace:
https://devops20.slack.com/
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/
10: With all the consolidation in the open source market, how can you and your company be a good citizen when it comes to open source?
Open Source Beyond The Market:
https://rework.fm/open-source-beyond-the-market/
The fight to keep open source truly “open” — open source providers need to stand up:
https://www.information-age.com/open-source-providers-123483267/
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
DevOps20 Slack workspace:
https://devops20.slack.com/
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/
9: Why are people scared of continuous deployment? Can everyone get to true continuous deployment? Darin and Viktor discuss these question as well as why delayed is sometime perceived as continuous.
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
DevOps20 Slack workspace:
https://devops20.slack.com/
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/
8: You understand the impact that feature flags have on continuous delivery. However, have you thought about how refactoring should also be a part of your day to day life?
Refactoring by Martin Fowler
https://www.amazon.com/Refactoring-Improving-Existing-Addison-Wesley-Signature-dp-0134757599/dp/0134757599/
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
DevOps20 Slack workspace:
https://devops20.slack.com/
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/
7: It seems like Continuous Integration should be a simple and non-negotiable process in today's workplace. We discover that not everything is as it appears.
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
DevOps20 Slack workspace:
https://devops20.slack.com/
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/
6: Matt Klein recently tweeted his career advice to be a successful individual contributor. We take an in depth look at that concept in today's episode.
Link to Matt's Twitter thread:
https://twitter.com/mattklein123/status/1130206773078421504
The Proximity Principle by Ken Coleman:
https://www.kencoleman.com/store/product/the-proximity-principle-book
DevOps Paradox by Viktor Farcic:
https://www.packtpub.com/web-development/devops-paradox
The DevOps 2.6 Toolkit: Jenkins X by Viktor Farcic:
https://leanpub.com/the-devops-2-6-toolkit
DevOps20 Slack workspace:
https://devops20.slack.com/
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/
5: Chef...Puppet...Ansible...Terraform...CFEngine. These are some of the big names in configuration management. In today's episode, we debate are these "classic" tools still applicable in today's DevOps world.
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/
4: How today's workforce is driving many of the current trends in DevOps.
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/
3: Convention over configuration. We know that it makes a developer's life easier (or it is supposed to...). Can we apply that same thought process to the full lifecycle of an application? We'll answer that question and more on today's episode.
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/
2: With apologies to Derek Zoolander, Kubernetes is so hot right now. Why is that? We ask that question and come up with a few answers that might surprise you.
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/
1: What is DevOps? The answer(s) we come up with may surprise you.
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/
Welcome to DevOps Paradox.
Signup for access to the Slack workspace:
http://slack.devops20toolkit.com/