It's here! Get all 19 issues of Increment as a limited-edition bundle: https://t.co/XXp7SP5e14

New limited-edition bundle coming soon to https://t.co/PnE0wVZ0pN 📈

📖 From the archives: @elizabethminkel chronicles the development of Archive of Our Own (AO3), now 15 years old. “This is what a website would look like if you didn’t have to care about most of the things that you usually have to care about.” https://t.co/cCWOeutg8n

“Management work often consists of building up your team’s resilience to organizational storms—and your own resilience, too.” —@lara_hogan

“Frontend development is at the intersection of art and logic, business and expression, left brain and right brain, design and nerdery. I love it.”—@chriscoyier

“This is where observability really shines: It enhances your ability to ask questions of your systems, including ones you hadn’t originally thought to ask.” —@glitch’s @Mads_Hartmann

“Successful onboarding isn’t about learning the codebase at light speed or pushing out new features as quickly as possible; it’s about building a foundation of relationships and psychological safety.” —@alexandras_dev https://t.co/MAPi5GqHPj

“Releasing pieces of your infrastructure as independent projects helps create technological honesty in your stack.” —@sophiebits

"We’re not designing to judge people’s coding practices, but to help them solve problems." —@old_sound

“The long history of cities offers useful models for open-source software—not only for what can work, but for what is possible.” —@devonzuegel

“Good plans not only light the path forward, but also show you where not to tread, making the consequences of wrong paths clearer.” —@hillelogram

“Crafting a roadmap that pairs engineers’ personal objectives with product and company goals can yield measurable gains both for the business and its people.” —@meowlissa10

“Assuming teams don’t need a clear objective to work toward is like handing a list of turn-by-turn directions to a driver and expecting them to understand where they should end up by nightfall.” —@ph1

“Individual contributors are often especially well-positioned to identify high-impact areas of work, yet they’re often left out of the planning process altogether. What’s an IC to do?” —@davidnoelromas

“With wicked problems, the trick is to surface and reconcile diverse viewpoints, making multiple perspectives explicit so all parties can develop a shared understanding of contentious issues.” —@kailashawati

“In business, building wealth is something to be done as soon as possible. Likewise, doing the fundamental work to make our systems stronger and more efficient should be viewed as worthy of up-front investment.” —@leemaynassery

“Open-source maintainers have learned to leverage and share plans to generate energy and exuberance, incorporate user perspectives into the prioritization process, and communicate with their communities.” —@captainsafia

“Where agile champions continuous experimentation and iteration, milestones advocate for letting work come to a finishing point. Together, they can produce a steady, sustainable rhythm.” —@mellogood

“Digital spaces are getting more and more public. Closed user groups and forums are switching to open communities and massive networks. Customer support is no longer private. Our goal is to be a part of these discussions.” —@youtrack’s Elena Pishkova

“By understanding tooling as a complement to our planning processes rather than an alternative to them, we can better tackle the technical and human challenges of software development.” —@mikiobraun