BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Culture & Methods Content on InfoQ

  • How Open Source Can Pave the Path Towards a Staff+ Role

    Open source contributions and long-term community engagement can help you on your path to a staff+ engineer role. Written communication skills are key for the async and remote work which is common in open source. Your contributions should be aligned with business needs, which can give you visibility that opens up career possibilities. Alex Porcelli presented at QCon London 2022.

  • How Software Affects Climate Change, and What Software Engineers Can Do about It

    There are huge amounts of software running everywhere on the planet - and this software consumes energy when it is running. Unfortunately most of the energy world-wide is still being produced by burning fossil fuels. Software engineers can improve the software so that it uses less energy to do its job, then less energy needs to be produced by burning fossil fuels, which is better for the climate.

  • Becoming a Staff Plus Engineer: Leadership and Communication Training Matters

    The poor industry support for engineers who want to pursue a technical career affects them; many outstanding technical individuals find themselves forced to seek a management position. The path to a staff plus engineer role is not straightforward. Training on leadership and communication for staff plus engineers can help them to become a better tech leader.

  • CircleCI Report Finds Successful Software Teams are Larger and Test Extensively

    CircleCI - a continuous integration and continuous delivery platform - has released the findings from their 2022 State of Software Delivery Report. The report reveals that the most successful software delivery teams are larger, use extensive testing, and prioritise being ready to deploy.

  • Improving Software Quality with Gamification

    Bingo Bongo sessions for bug hunting and playing risk storming games can improve quality. Gamification supports learning, can make everyday work interesting, and strengthen team spirit. Playing games should be part of the daily work at the office and seen as an effective work time. In gamification, a real value is created by the creative process.

  • Five Behaviours of Successful Staff Plus Engineers

    Staff plus engineers act as technical leaders to have a bigger impact. Their ability to get things done goes beyond their individual capacity to grow and mentor others. The tech industry has moved away from thinking that engineers work individually and collaboration is one of the most important behaviours in a staff plus role.

  • Infinite Representations: an Impossible Thing for Developers

    Developers can face impossible things in their daily work. It’s impossible to directly represent infinity or to hold infinite precision on a discrete physical computer. Storage and representations are bounded. Ignoring or being unaware of this impossibility can lead to bugs or systems behaving differently than expected. Kevlin Henney gave the keynote Six Impossible Things at QCon London 2022.

  • Scaling and Automating Microservice Testing at Lyft

    Lyft used cloud-based isolated environments for several purposes, including end-to-end testing. As the number of microservices increased, tests using these environments became harder to scale and lost value. Recent articles describe how Lyft shifted to testing using request isolation in a shared staging environment and used acceptance tests to gate production deployments.

  • Using Team-Set Salaries for Company-Wide Compensation

    Team-set salaries (TSS) can be scaled up by doing appraisals across teams where results are automatically calibrated. The scores indicate where conversations are needed. TSS encourages people to learn new skills and adapt.

  • Developer Experience at Lyft: from the Cloud to Local Environments

    Lyft engineering finished their decomposition of a monolith into a collection of microservices back in 2018. Modular development environments using Docker containers eventually moved to the cloud. Recent articles describe how their development tooling struggled to keep up as time passed and the number of microservices exploded. Development environments had to return to the engineer’s machine.

  • Creating Tight Cohesive Tech Teams for Women to Thrive

    Women in tech need a dynamic, valuing team, stimulating work, push and support, local role models, nonjudgmental flexibility, and personal power. Tight cohesive teams can provide high-quality interactions, making people feel valued.

  • Measuring the Environmental Impact of Software and Cloud Services

    Software has an influence on the limitation of the service life or the increased energy consumption. It’s possible to measure the environmental impacts that are caused by cloud services. The design of the software architecture determines how much hardware and electrical power is required. Software can be economical or wasteful with hardware resources.

  • Making On-Call Less Painful for Developers by Using High-Quality Alerts

    On-call is an increasing reality for developers. Improving alerts to reduce noise, automation, and removing warnings can help to make on-call work more humane. A driving force behind automation is Infrastructure as Code. Over time you can abstract that code so that it fits other use cases, which helps propagate best practices.

  • QCon Software Development Conferences: Seven Tracks Not to Miss

    Why are micro-frontends important? How should you optimise your organisational architecture for speed and flow? How to make microservices successful? Have you ever wondered how well-known tech companies can seamlessly deliver an exceptional user experience while supporting millions of users and billions of transactions? Looking for new processes and best software practices?

  • How Security by Design Helped to Manage Risks in a Cloud Migration

    When a company migrated to the cloud, security issues arose due to difficulties in getting stakeholders on board and involving security from the start. Embedding security assessments as part of the continuous cloud DevOps process and adopting an agile strategy for security risk management throughout the lifecycle of the project helped to increase the governance of security during the migration.

BT