I'll Help with some topics DevOps Practices Application Quality Enhancements Code Patterns Tools Value Processes People Skills & Personal Development DevOpsPorto 2018
Logging, Monitoring and business metrics capturing Infrastructure as code Feature agging Deployment techniques DocOps Security (OWASP and more) Portmortems Game Day activities Chaos engineering DevOps Practices DevOpsPorto 2018
ADRs (Architecture Decision Records) #0003 - Add Request Logging ##Date: 2017-02-24 ##Context Debugging calls to the server can be hard if requests and responses are not logged By logging every request and response we can understand if a request ever arrives at the service and we can also monitor requests by aggregating information from th requests and errors produced ##Decision Add Middleware log every request and response. Response message should have code and time. ##Consequences * we can see every resquest made and mount monitoring dashboards on top of that Tracking and debuggung options are improved https://github.com/joelparkerhenderson/architecture_decision_record DevOpsPorto 2018
People Skills & Personal Development Writing " Captains Log" Empathy Management & Leadership Skills Team & Communication Skills Learning Organizations DevOpsPorto 2018
Mix Activities read books on your comute listen to podcasts while you drive listen to audio books while you excercise watch a presentation while you cook toilet reading DevOpsPorto 2018
Improving at work Using 1-on-1s and mentoring Logging work and discoveries Learning retrospectives Portmortems to blamelessly learn from failure 20% time projects or hack-a-thons DevOpsPorto 2018