Imagine you are looking at your calendar and there is 1:1 session scheduled for 2 PM today. Maybe it is with your manager, or maybe you’re a manager about to talk with someone who reports to you. So how do you feel? Happy? Anxious? Neutral? Thinking about losing your time, again? Spending your time well and proactively? Able to push things forward? Competing against…you don’t even know what exactly? Complaining once more? Feeling excitement about sharing your recent achievements? Feeling awkward as you don’t know what to say? Expecting to get and provide candid feedback?

You can certainly experience a whole mixture of emotions before, during, and after 1:1 meetings. And even if you think you do “quite fine” in this area and know how to have effective 1:1s, we think it could be at least a bit better at Red Hat!

I’ve used the term Feature Factory at a couple conference talks over the past two years. I started using the term when a software developer friend complained that he was “just sitting in the factory, cranking out features, and sending them down the line.

How do you know if you’re working in a feature factory?

Learn how to set up continuous delivery with a Jenkins pipeline to continuously deploy your application as part of a DevOps process.

Who doesn't love a good scary story, something to send a chill across your skin in the middle of summer's heat? And this year, we're celebrating the 200th birthday of one of the most famous scary stories of all time: Frankenstein

Imagine you are a Django developer building a social network for a lean startup. The CEO is pressuring your team for an MVP. The engineers have agreed to build the product using behavior-driven development (BDD) to deliver fast and efficient results. The product owner gives you the first feature request, and following the practice of all good programming methodologies, you begin the BDD process by writing a test. Next you code a bit of functionality to make your test pass and you consider your design. The last step requires you to analyze the feature itself. Does it belong in your app?