It’s been a busy couple of weeks, so I missed a couple posts, but I’m back on track from my last post. There have been a ton of interesting links flying around in the last couple of weeks between me and colleagues, here are my five must reads:
What's the next DevOps buzzword: DevSecOps
-
Awesome-DevSecOps is a list of links following the Awesome-* trend on a movement designing security approaches into a agile DevOps techniques. but try and put a couple of these links on your reading list. I know I'll be asking our Node.JS developers to pull the NodeGoat repo and find how to both test and mitigate all of the OWASP Top 10 vulnerabilities exposed in the application.
-
So many interesting stats can be taken away from StackOverflow’s Insight 2017 survey. Some key take aways we had circling around at Morningstar included that 73% identify themselves as a web developers, and of those, 64% identify as full stack; half of those surveyed have been professionals less than five years; 73.9% of professional developers code as a hobby; 32.7% of developers said they contribute to open source projects; JavaScript is the most popular language (63%); Node.js is the most popular framework, followed by Angular and .NET code; topping the "most dreaded platforms" list are SharePoint, Salesforce and Word Press.
-
I’ve always complaining that there is no great site where people collect learnings from all of the experimental digital design that so many companies are doing. We could share so many lessons so they don’t need to get repeated (A/B tests on language tweaks, placement, colors, layouts, workflows). Well, the Unbounce product team runs a pretty great blog that is worth reading. It focuses on marketing, and I’m still dreaming of the repository of product workflow and product usability experiments, but its a great resource for people to understand a lot of typical techniques.
-
Great to see Google continue to double down on open source with a new public home for their open source projects, and also releasing their guidelines on how they publish and manage open source internally. Really useful resource, we’ve been navigating opening a number of our internal frameworks and platform tools, and leverage techniques like InnerSource to share code internally even when we don’t plan to open it externally. The community building and shared responsibilities practices of open source are great cultural tools for teams.
-
On the front-end technology side, I’m really excited to see a framework we’ve made a major investment in, Ember.JS, become even more accessible, with the separation of the core component rendering library into a distinct project, Glimmer.JS. Tristan Edwards gives a quick overview of why this is big news. for Morningstar, this is huge, because we develop components that both need to get consumed by third parties, and also bring them together into our complex institutional financial research products.
And since I missed a couple weeks, I’m going to cheat with a shameless 6th link that I think is really awesome. It's our latest Morningstar Design Reel that features our focus on design in our products, and I think its really fun to watch.
.png)
