DiscoverCode Comments
Code Comments

Code Comments

Author: Red Hat

Subscribed: 50,479Played: 73,598
Share

Description

Putting new technology to use is an exciting prospect. But going from purchase to production isn’t always smooth—even when it’s something everyone is looking forward to. Code Comments covers the bumps, the hiccups, and the setbacks teams face when adjusting to new technology—and the triumphs they pull off once they really get going.
23 Episodes
Reverse
Every digital transformation journey is unique. The goals may be similar, but the requirements, features, and choices made along the lead to new systems unlike any other. That’s all well and good—until you need to merge two systems into one, on a short timetable.Atul Verma of the Bank of Montreal recounts how he and his team found themselves handling the technical side of one of the largest acquisitions in Canadian banking history—with only a few months to get it done.
Modernizing your IT systems is a worthy achievement. You can reap the benefits of digital transformation at last. But don’t be lulled into a false sense of security—digital transformation isn’t about reaching the finish line. It’s about reaching for the horizon. Randall Núñez of Experian explains how perpetual improvement is a key element of digital transformation, because systems can’t stay modern forever.
It can be difficult to know the full outcome of your choices. Not having clear priorities makes it impossible to know which choice is the right one, because those should inform your direction. Adam Timm of Crunchy Data explains how multiple factors influence outcomes—and how keeping your priorities at the forefront of your decision-making process makes it easier to pick the right choice for your organization.The guest featured in this episode works for Crunchy Data, a Red Hat partner.
Databases are rarely the stars of digital transformation. That’s not necessarily a bad thing. But that doesn’t mean they should be an afterthought either. Craig Kerstiens of Crunchy Data covers the state of the database—and how the database tools you choose have implications beyond the databases themselves.The guest featured in this episode works for Crunchy Data, a Red Hat partner.
We’ve been taught to stash our secrets. Passwords, credentials, and tokens shouldn’t be shared lest they fall into the wrong hands. When it comes to building and running large-scale systems, that thinking has to change. But maybe only a little bit.Rosemary Wang and Steve Almy of HashiCorp share how business as usual for secrets management means putting your business at risk.The guests featured in this episode work for HashiCorp, a Red Hat partner.
Modern IT systems have a lot of components—components people have to use, and components who need to talk to each other. That’s a lot of traffic and exchanging of sensitive information. How do you sort the legitimate users from the potential intruders?Niels Van Bennekom shares how CyberArk helps organizations set up identity management systems that can keep up with expansive, ever-changing IT systems.The guest featured in this episode works for CyberArk, a Red Hat partner.
A journey of 1,000 upgrades starts with a single commit. It’s not always clear how much change digital transformation entails. But it’s likely more than expected.Season 3 of Code Comments travels the well-trodden paths of IT modernization, cloud migration, and the unmentioned necessities to make it all work.
Is there such a thing as too much enthusiasm for automation? Probably not. But it can be difficult to unify an organization with strong opinions. Vincenzo Sposito shares how Discover harnessed its teams’ passions to build a unified automation solution—while preserving debate and experimentation.
The tensions between security and operations and developer teams are the stuff of legend. DevSecOps is trying to change that, and automation is a big part of making it possible. But automation alone can’t overcome entrenched behavior. Joylynn Kirui shares how Microsoft is helping shift security considerations to the left—and alleviating the headaches that process can bring. Because in the long run, everyone is better off with better security.
No single person can automate a whole company’s IT. Even most teams would need some help. But it’s also not likely you can immediately get everyone to automate their own work right away. So how do you get it done? Sudheer Kumar Donthineni explains how Ulta Beauty makes the most of its small team of 3 automation experts. Through the power of collaboration, they’re able to make significant progress with automation—and help their employees grow.
Establishing consistent automation habits helps keep those skills sharp and gets the systems set up promptly. But getting to that point takes time. And even when automating processes becomes second nature, you can still overlook potential pitfalls. Joshua Bradley of Cox Edge describes what it’s like managing the expectations teams and stakeholders may have about automating infrastructure. The systems may be more complex. Timelines may be longer. And even when you leave detailed instructions, users may still make mistakes. It just means you need to keep adjusting until you get it right.
Making automation work takes more than just writing the scripts. And it’s most effective when it becomes a habit rather than a one-off project. But building habits and changing culture is no easy task. Eduardo Krumholz and David Linthicum of Deloitte help their clients internalize automation as part of their workflows. They share their strategies to help their customers make that transition successful—and overcome reluctance to change.
World Wide Technology (WWT) helps organizations set up their tech infrastructure. But they also have to do it for themselves. It’s a lot to juggle with their ambitious goals for growth. Automation is helping them get to where they want to go—but it took them a few years to find a solution the team bought into.  Corey Wanless and Jason Kayser share what WWT wanted to achieve with automation, the challenges they faced, and how it helped the people of WWT come together.
Automation is a game-changer. It promises to decrease time to deploy, reduce errors, and increase reliability and efficiency. But you can’t automate change. What does it take for teams to actually reach that finish line? And how does it affect how they actually work? Season 2 of Code Comments goes beyond the sales pitch and features teams who’ve tackled automation. Because there’s no script for adjusting to automation.
The idea behind extended reality, or XR, is immersion. That can be a hard standard to meet when dealing with a visual interface. As an intern at NVIDIA, Hayden Wolff stepped up to tackle a thorny challenge, and with some assistance from natural language processing (NLP), the company’s Project Mellon is changing the way we look at the design process.
Connecting tools and systems yields all sorts of benefits. What can be tricky is knowing exactly what those benefits are - especially emergent ones. Neesha Godbole, a Partner Account Manager with MuleSoft, shares how mapping the benefits of joint projects is about finding more than the sum of the parts. But it doesn’t make a difference if you can’t communicate the value to customers.
Change may seem exciting for some. But for those who are moving from one platform, or one technology, to the next, it can be a daunting, anxiety-filled experience. For Dynatrace’s Markie Duby, keeping empathy at the center of one’s work is crucial for building trust and for collaborating with customers as they adapt to an industry that never stops moving.
When it comes time to move to the cloud, the concerns can be many. Companies are increasingly security conscious, and success depends on applications being reliable. There’s also the need for agility, to adjust to changes in the market. F5’s Matt Quill tells Burr how planning carefully and collaboratively can address challenges while building pivotal internal relationships.
Ever been so frustrated with the options available that you build your own? Ben Darnell, Chief Architect and Co-Founder of Cockroach Labs, shares how his dissatisfaction with distributed databases led to the creation of CockroachDB. To build a distributed database that not only plans for but expects failures, they needed to implement the Raft consensus algorithm. Getting it up and running was a tough technical challenge. But the result was an incredibly resilient database.Find out why Netflix uses CockroachDB for their databases. Can you have access to a globally available database at the speed of a regional one? Check out how Cockroach Labs accomplishes this with global tables.  
It’s one thing to talk about your open source principles. It’s another entirely to build them into your workflows. How does a large company like Amazon Web Services actually make it work? David Duncan, Sr Manager Partner Solutions Architect at AWS, explains that being open with partners and customers throughout the development process is key. He talks about ensuring there are no one-way doors, and how collaboration helps to produce a better experience for OpenShift on AWS as well as combining the power of the Cloud Control API with Ansible automation.
loading
Comments (6)

Cedric cheri

great

May 25th
Reply

SASSA

it's best, also do you know you can check sassa status at https://sassastatus-gov.co.za/

May 22nd
Reply

SASSA

Can't wait to share experiences! By the way, have you tried using SRD Status Check to track your progress on https://sassastatus-gov.co.za/

May 22nd
Reply

For Google

contact@castbox.fm

May 14th
Reply

SASSA

Can't wait to share experiences! By the way, have you tried using SRD Status Check to track your progress on https://sassastatus-checks.co.za/

Feb 23rd
Reply

Hamed khosravi

it's so fantastic

Jan 24th
Reply