Professional Context
I still remember the day our team's carefully crafted deployment script failed to account for a critical latency issue, causing our entire system to crash during a demo for a potential client. It was a frustrating moment, but it taught me the importance of thorough testing and real-time monitoring in our line of work as Sales Engineers.
💡 Expert Advice & Considerations
Veterans know to avoid depending on this system to generate fancy architecture docs, actually use it to analyze your defect rate and identify patterns that can inform your code reviews.
Advanced Prompt Library
4 Expert PromptsRoot Cause Analysis of Defect Rate Spike
Given a Git repository with a history of commits and a corresponding Jira project with issue tracking, analyze the defect rate over the past 6 sprints and identify the top 3 contributing factors to the recent spike in defects. Consider the impact of changes to the CAD design and the introduction of new features. Provide a step-by-step guide on how to reproduce the analysis, including any necessary AWS/GCP queries and IDE configurations. Assume a baseline defect rate of 0.05% and a current rate of 0.15%. Output the results in a format suitable for a Root Cause Analysis report.
Real-time Uptime Monitoring Dashboard
Design a real-time dashboard to monitor the uptime of a cloud-based application deployed on AWS, using metrics from AWS CloudWatch and logging data from the application. The dashboard should display the current uptime, average response time, and error rate over the past hour, as well as provide alerts for any dips in uptime below 99.9%. Assume the application is built using a microservices architecture and uses a combination of RESTful APIs and message queues for communication. Output the dashboard design as a JSON object, including any necessary AWS CloudFormation templates and IDE configurations.
Sprint Velocity Forecasting Model
Develop a forecasting model to predict the sprint velocity of a team of developers working on a complex software project, using historical data from Jira and Git. The model should take into account factors such as team size, experience, and workload, as well as the impact of external factors like changes in requirements or unexpected defects. Assume a team size of 10 developers and a average sprint duration of 2 weeks. Output the forecasting model as a Python script, including any necessary libraries and configurations for integration with Jira and Git.
Latency Optimization for Critical API Endpoint
Given a critical API endpoint with a high defect rate and average latency of 500ms, analyze the performance bottlenecks and provide a step-by-step plan to optimize the latency to under 200ms. Assume the endpoint is built using a RESTful API framework and uses a combination of caching, database queries, and external service calls. Use data from AWS X-Ray and AWS CloudWatch to identify the performance bottlenecks and provide recommendations for optimizing the database queries, caching strategy, and external service calls. Output the plan as a markdown document, including any necessary code snippets and AWS CloudFormation templates.