Steve July 27, 2020
getting-started-as-an-open-source-builder-and-more-industry-trends

As part of my role as a principal communication strategist at an enterprise software company with an open source development model, I publish a regular update about open source community, market, and industry trends for product marketers, managers, and other influencers. Here are three of my and their favorite articles from that update.

Open source builders: Getting started

“Eventually I found myself wanting to make code changes myself,” Liz says. One of her first contributions was an authorization extension for the Django framework. “I remember being worried that the maintainers might not want a change from a complete stranger, so it was exciting and something of a relief that it was accepted,” she adds. “It’s always a great feeling to get approval and even thanks for your contribution.”

The impact: This series of interviews with open source maintainers (quote from Liz Rice) is an intersection of motivations and experiences jumping into open source. It’s also a nod to the myth of the genius lone wolf developer; you can get a long ways by yourself, but you’ll get further and build better things if you know how to work well with other people. Farther still if you figure out how to persuade and inspire them.

Fluent Bit v1.5: Lightweight and high-performance log processor

One of the biggest highlights of this major release is the joint work of different companies contributing with Fluent Bit core maintainers to bring improved and new connectors for observability cloud services provided by Google, Amazon, LogDNA, New Relic and Sumo Logic within others.

The impact: To “collect data/logs from different sources, unify and send them to multiple destinations” is as tedious of a task as you can come across, yet it’s one shared both by the hyperscalers and their customers. Exhibit A: a prime example of open source working exactly as intended. Congrats to the Fluent Bit team on this release!

How Kubernetes empowered Nubank engineers to deploy 700 times a week

As a result, deployment has gone from 90 minutes to 15 minutes for production environments. And that, says Nobre, was “the main benefit because it helps the developer experience.” Today, Nubank engineers are deploying 700 times a week. “For a bank you would say that’s insane,” Capaverde says with a laugh. “But it’s not insane because with Kubernetes and canary deployments, it’s easier to roll back a change because it’s also faster to deploy. People are shipping more often and with more confidence.”

The impact: This feels like a win and a loss to me. Sure they lowered the cost of making a change in a way that gave people more confidence to try things out. But their developers can no longer run 10k while waiting for their deployment to finish and can now only fit in a single TED talk.

I hope you enjoyed this list and come back next week for more open source community, market, and industry trends.

Read More