BT

InfoQ Homepage Communication Content on InfoQ

  • The Human Side of Microservices

    A microservices architecture is a game changer for team communication, not a purely technical solution. If different teams don’t have stable, direct communication channels, the software they produce will suffer. The five key properties crucial for a successful microservices implementation are zero-configuration, auto-discovery, high redundancy, self-healing, and fault tolerance.

  • Organizational Refactoring at Mango

    To increase agility, companies can descale themselves into value centers in charge of a business strategic initiative, with end-to-end responsibility and with full access to the information regarding customer needs. You need to create spaces where people can cross-collaborate and learn, using for instance self-organized improvement circles, Communities of Practice or an internal Open Source model.

  • Readable Code - Why, How and When You Should Write It

    Most people would say they want readable code, and may even prefer readability over functionality. But when it comes down to asking people to define readability, opinions will start to diverge. At Explore DDD 2018 , Laura Savino covered why we want readable code, what it really means to be readable, and when readability absolutely must take priority over other considerations.

  • Atlassian Announces Solutions for Incident Management

    Atlassian announced on September 4 that they have launched a new product called Jira Ops and that they will acquire OpsGenie. Organizations can use Jira Ops for resolving incidents and doing post-mortems to learn from them. OpsGenie adds prompt and reliable alerting to Jira Ops.

  • Leading within: Evolving into Agility

    Adaptive organizations rely on horizontal leadership where awareness is a fundamental quality for leadership. When we are able to really listen with curiosity, empathy and courage, then our listening changes our perceptions, our relationships, and therefore, our environment.

  • Strategies for Microservices Communication

    When moving from a monolith to a microservices architecture, complexity implicitly hidden within the monolith becomes explicitly visible and the challenges for communication will grow exponentially, Michael Plöd explained in a presentation at GeeCON 2018, describing different strategies for communicating between microservices.

  • Digital Disruption via Space: High-Speed Internet Access through Satellites

    Satellites are enabling high speed access to the internet in rural areas, on airplanes, and for internet service providers to the core network. Space technology innovations like electric propulsion, digitalization revolutionize telecommunications and new entrants like SpaceX are forcing launch costs down. These developments will enable new services and lower the costs of existing ones.

  • Chatbots 101 for Developers: Q&A with Anamita Guha

    Chatbots are becoming more critical to developers in their daily lives – from understanding how the technology operates, to creating better code. Developers tend to have a natural curiosity about bots and the tech behind it. Artificial intelligence tools exist to address emotional intelligence with chatbots in conversational interfaces.

  • Management Support in Agile Adoption

    It is essential that everyone involved in operating the business be aware of how IT can change daily operations. Senior management can look across silos and teams to impact the throughput of the entire system. IT managers and executives rely on business managers being active participants for teams to work effectively and efficiently. Management commitment remains key for agile across the company.

  • Great Engineering Cultures and Organizations - Afternoon Sessions from QCon London

    The Building Great Engineering Cultures and Organizations track at QCon London 2018 contained talks from practitioners representing digital leaders of the consumer internet as well as transformational corporates from “traditional” sectors. Previously InfoQ published a summary of the morning sessions; this is the summary of the afternoon sessions of this track.

  • Dealing with the Broken Human Machine: How to Create High-Performing Teams

    To really progress in developing software and build anything at a scale, you have to examine your blind spots and learn to deal with people. The culture we build is important: the difference between a high performing engineering team and a low performing one is orders of magnitude in terms of productivity and quality. Focusing on how we do things is as important as what we’re doing.

  • Making Our Language and Behaviour More Inclusive

    To avoid excluding people, we need to gain more awareness when we are in the wrong and be introspective to find out why someone is upset or offended by what we have said or done. By being excluded, people will eventually leave their jobs, communities or profession, which is something that we need to prevent. Peter Aitken suggested taking a positive approach when addressing inclusion issues.

  • How Blogging Empowers Agile Teams

    Moving the thinking and decisions a team makes from people’s inboxes onto a blog can make it accessible to all, findable in the future, and referenceable by everyone. Instead of writing documentation, you can use blogumentation to transfer knowledge and document the history of projects that provide context to the code.

  • Q&A with Aurynn Shaw on Sharing Her Personal DevOps Journey at DevOpsDays NZ

    Raf Gemmail speaks with Aurynn Shaw about her upcoming DevOpsDays NZ talk and the humanist side of DevOps.

  • Tackling Technical Debt at Meetup

    Continuous product health can be realized by regularly prioritizing the highest impact technical debt items and knocking those off systemically. You need to continuously iterate how you're tackling technical debt to drive more and more impactful results. Going for maximum impact items first and communicating the impact of paying down technical debt is what Yvette Pasqua, CTO of Meetup, recommends.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.