Professional Context
With a defect rate of 2.5% and a sprint velocity of 25 story points, the pressure is on to optimize workflows and improve code quality, all while maintaining 99.9% uptime and reducing latency to under 100ms, in order to meet the stringent KPIs set by the organization, which are closely tracked using tools like Jira and Git.
💡 Expert Advice & Considerations
Don't waste time trying to automate everything, focus on using Gemini to augment your existing workflows and improve data interpretation, especially when working with complex systems like CAD and IDE.
Advanced Prompt Library
4 Expert PromptsRoot Cause Analysis of Deployment Failure
Analyze the deployment script and architecture doc for the recent AWS deployment failure, identify the root cause of the error, and provide a step-by-step guide to rectify the issue, including any necessary changes to the code or configuration files, and ensure that the solution is compatible with the existing GCP infrastructure, taking into account the current uptime of 99.5% and the goal of reaching 99.9%.
Code Review and Optimization
Perform a thorough code review of the recent commit to the Git repository, focusing on optimizing the latency and improving the overall performance of the system, provide recommendations for code refactoring, and suggest changes to the IDE settings to improve development efficiency, ensuring that the code quality meets the organization's standards and the defect rate remains below 3%.
Incident Report and Post-Mortem Analysis
Create a detailed incident report for the recent system downtime, including a post-mortem analysis of the root cause, a summary of the actions taken to resolve the issue, and recommendations for preventing similar incidents in the future, using data from the Jira incident tracking system and the CAD design files, and ensure that the report is concise and actionable, with a focus on improving the overall uptime and reducing the mean time to recovery (MTTR).
Deployment Script Refactoring
Refactor the existing deployment script to improve its performance, security, and maintainability, using core standards and design patterns, and ensure that the script is compatible with the organization's GCP and AWS infrastructure, taking into account the current sprint velocity and the goal of reaching 30 story points, and provide a step-by-step guide to deploying the refactored script, including any necessary changes to the architecture doc and code review process.