Many people and companies have poorly interpreted Grace Hopper’s famous quote about getting things done inside bureaucracies. I’m here to set the record straight.
A generative engineering culture is one where nothing seems to fall through the cracks, “we should” gets prioritized and becomes reality, and original ideas and value come primarily from engineers, rather than management. A culture like this is an engine for building capacity, quality, innovation, and sophistication.
Here’s some hard-earned experience on how to validate an email address. If you listened to JS Party #39, then you already know this. If you think I’m about to hand the best regex you’ve ever seen…
Having spent the better part of the last decade as a work-from-home developer, I have discovered or adopted a few LIFE HACKS which I am going to share with you now.
If there’s one thing successful community projects have in common, it’s that they all provide something valuable to the developers who use them.
Has your organization considered building a community project that’s meaningful for developers? Here are five of the most common types of developer community projects and how they create value for the community.
When you hard-attach your library to a specific technology or framework, you limit its potential impact. By thinking ahead and putting in a little more effort, your library could benefit orders of magnitudes more people.
Two new terms have recently emerged around software delivery: Software Defined Delivery and Progressive Delivery. Why? How do they relate to Continuous Delivery?
Several forces today make delivery increasingly complex. Notably, proliferation of repositories, with hundreds of small projects replacing a handful of monoliths; desire for greater automation to realize the full potential of CD across multiple environments; the rise of feature flagging; and increased evidence (such as the Equifax debacle) of the need to bake security into the delivery process.
If you open source your work to (speculatively) make lots of money… you’re doing it wrong. There are much easier means to that end. But there are plenty of good reasons to do open source for free. Here’s three of them.
What would happen if everyone in your company was reading and responding to incoming support emails? In this post, Simon Schultz shares why he spends more time on incoming support emails than internal reports, plus six good reasons you should do so as well.
I love my numbers, and I love my spreadsheets, but the heart and soul of all the great people using and being in contact with your service, product and company are too often buried somewhere in a soulless column in your beloved spreadsheets.
Valuable insights, information, and data are too often ignored and forgotten.
The new changelog.com setup for 2019 is packed with exciting features that are too good to keep to ourselves. Since the infrastructure code is already public and has been running changelog.com for a few months now, the value that we are sharing is proven to us.
Until now, the best way to add a contributor to the list was via the CLI tool. That works great when you’re at your computer in “code mode”, but not when you’re mobile or just browsing the web.
Building an open source business is hard. Octobox co-founders Andrew Nesbitt and Benjamin Nickolls know this all too well. They’re walking a preverbal “tightrope” with the introduction of new pricing in order to move towards sustainability.
By all accounts, Octobox is a success. It’s a thriving open source project that’s being adopted by the software community using GitHub. It has a growing community of maintainers and contributors. Organizations like Shopify run company-wide instances for their own use. Octobox is also run as a SaaS that hosts more than 11k users.
But there’s one tiny little problem…Octobox is not sustainable (yet).
If you’ve been watching the news, you know that the latest data breach involved Marriott exposing 500 million guest reservations from its Starwood database. The kicker is that the unauthorized access to the Starwood guest database stretches back to 2014. That’s FOUR YEARS of unfettered access to this database!
It’s breaches like these that helped motivate the team at the Cryptography Research Group at Microsoft to be “extremely excited” to announce the release of Microsoft SEAL (Simple Encrypted Arithmetic Library) as open source under the MIT License.