3 posts tagged with "teams"

As you might have heard by now, the tech world is undergoing massive layoffs due to the looming recession. Big tech companies like Twitter, Meta, Google, and Amazon have all announced massive job cuts in the past few months. Software developers are on the receiving end in 2023, accounting for 20% of layoffs, according to data from workforce intelligence firm Revelio Labs.

Apart from the stress and anxiety it causes employees who were let go, layoffs can disrupt the rhythm of development teams and impact how projects move forward. The developers that survive layoffs are expected to keep everything running smoothly despite their smaller numbers. They'll have to explore strategies that will allow them to continue working efficiently and produce high-quality software without overworking themselves.

Feature flagging is a powerful technique that allows remote teams to quickly and easily toggle features on and off in their codebase. With feature flags development, teams can deploy new code to production without immediately making it available to end users.

This can be especially useful for remote teams, as it allows them to deploy code safely and efficiently. That’s because remote teams may not have the same level of communication and coordination as they would in a co-located setting. By using feature flags, remote teams can deploy new features and updates more frequently, without the risk of disrupting the user experience.

Let’s discuss what feature flagging actually means and how to get started with it.

If you’ve been reading about feature flags then I’m sure you’re convinced of the power and value they provide. Since development is mostly a team effort, you may be wondering how to manage a feature flag within a team, regardless of size, so one developer’s work doesn’t affect another’s. Well, in this article, we discuss exactly this issue and offer two solutions, depending on the size of your team.