Daily Digest #216 ‐ October 22, 2018

• What is new in Rails 6.0
• The Decline of OpenID
• Surfing as a Metaphor for Software Development
• Here is how UX Design Integrates with Agile and Scrum
• Systems Monitoring: top vs Htop vs Glances
• Developing cross-platform apps using Neutralinojs latest release
• Well Architected Monoliths are Okay

---

Daily Digest #215 ‐ October 19, 2018

• Awesome vscode – 🎨 A curated list of delightful VS Code packages and resources
• csvreader library
• PeerTube – Federated (ActivityPub) video streaming platform using P2P (BitTorrent) directly in the web browser with WebTorrent and Angular
• memcached-util – Memcached utility to backup and restore the cache
• CrashDB – an ephemeral in-memory NoSQL database for the confident developer
• Goodbye Microservices: From 100s of problem children to 1 superstar
• Github Actions

---

Daily Digest #214 ‐ October 18, 2018

• Understanding Design Systems and Patterns
• Experimenting with GraphQL
• Patterns for distributed transactions within a microservices architecture
• WebAssembly on Cloudflare Workers
• Secrets Management within AWS ECS

---

Daily Digest #213 ‐ October 17, 2018

• The Illustrated TLS Connection
• CPDD: Critical Path Driven Development
• How to Recruit and Hire When You Need to Move Fast
• Be a Mentor, Not a Bully
• Why Agile Goes Awry — and How to Fix It
• Plans for the Next Iteration of Vue.js
• Unicorn—Rheos Remediation Center

---

Daily Digest #212 ‐ October 16, 2018

• Sourcegraph
• AWS Service Operator
• Kube-score – Kubernetes object static code analysis
• Markdown Page – build webpage with markdown
• Hardening macOS
• Falcon – A modern high-performance web server for Ruby

---

Daily Digest #211 ‐ October 15, 2018

• Breaking Good — Having a blameless engineering culture
• Etsy’s experiment with immutable documentation
• The Business Case For Serverless
• Chaos Conf 2018 Recap: Chaos engineering hits maturity as community moves towards controlled experimentation
• Serverless: The Missing Manual
• Dear AWS, we need to talk about your service names
• 5 Things Your Team Should Do to Make Pull Requests Less Painful
• Well documented Makefiles (available via make help)

---