Results are in for the 2019 State of JS survey. I’ve been digging through charts to see what I can see. Here are 7 insights that jumped off the page to me.
Gone are the days when we developers were too shy/humble/introverted to promote our warez with the confidence and vigor necessary to draw a crowd.
In fact, we may be experiencing an over-correction. Some of us are selling a bit too hard at times. With that in mind, here’s some help translating between how developers describe our software and what we might actually be thinking. 😉
Did you miss GitHub Universe this year? We did too, but we have an insider giving us all the details to share with you so you can stay productive, but not miss out. This is a summary of what was announced at GitHub Universe 2019.
Shanku Niyogi shared a full-length write up on the GitHub Blog with more details and links.
As the saying goes… history doesn’t repeat itself, but it often rhymes.
If you want to create a successful programming language (or at least understand how you might), it’s immensely valuable to learn from others who have done just that. on Go Time episode #100, two of Go’s creators (Rob Pike and Robert Griesemer) sat down to discuss the language’s success. Here’s 5 things they attribute to its success.
I’m excited to announce our newest podcast — Brain Science!
Brain Science is a podcast for the curious. Are you curious?! We’re exploring the inner-workings of the human brain to understand behavior change, habit formation, mental health, and being human. It’s Brain Science applied — not just how does the brain work, but how do we apply what we know about the brain to transform our lives.
The Changelog team will have a BIG presence at All Things Open in October. To celebrate, we’re giving away FREE tickets!
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.