InfoQ Homepage Culture & Methods Content on InfoQ
-
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.
-
Fair Individual Compensation for Agile Teams with Team-Set Salaries
Team-set salaries can be used to set fair compensation for individuals in multiskilled, collaborative, autonomous teams. People don’t appraise themselves, only their colleagues. It gives everyone a direct say in salary settings.
-
How Measuring Defect Mass Helps to Test Critical Product Areas
Introducing a measurement called “defect mass” helped a project to find the most impacted areas by developments and decide how many tests should be run for each impacted area. Using this measurement together with other KPIs helped them focus their testing. They managed to decrease the number of customer incidents.
-
Workplace Challenges & Opportunities for Software Engineering Professionals
Skills shortages, the great resignation, remote and hybrid working, continuing impacts of COVID-19 and increasing demand on software professionals have been examined and surveyed over the last few months and have identified both challenges and opportunities for software engineering professionals at this time. Time pressure, resource limitations and increasing customer demand contribute to stress.
-
Increasing Collaboration at Ericsson: Hardware and Software Developers Learn Each Other's Language
You can integrate hardware and software development with a cross-border team setup, where it’s important that hardware and software developers speak each other’s languages. The suggestion is to focus on “us” instead of “we” and “them”, and on the technical competence that connects developers over agile or lean terminology.
-
Moldable Development: How Custom Tools Make Systems Explainable
Moldable Development is a way of programming through which we construct custom tools for every software development problem. Glamorous Toolkit is a moldable development environment that can be used to mold custom tools.