Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
What makes developer reliable? I will tell you about my own fuck-ups that forced me to change myself into a reliable developer. Also, what are the common mistakes and how we can prevent them. At the end of the talk, I want you to raise the bar of software quality.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In this talk, Denys Medynskyi discusses his transformation from a production breaker to a reliable engineer, emphasizing the concept of reliability in software development during his presentation at Pivorak Conf 4.0. Medynskyi shares his personal experiences of making mistakes that led to production failures and reflects on what defines a reliable engineer, which he defines as someone who delivers quality work without errors and on time. Key points from the talk include: - **Understanding Reliability**: Medynskyi emphasizes the importance of reliability and quality in software engineering and shares insights gathered from surveys regarding common mistakes. - **Monitoring Quality**: He suggests metrics to track project health, including team velocity, the number of bugs, and the count of errors during production releases to gauge quality improvement. - **Error Management**: The speaker acknowledges past errors and stresses the importance of not just tracking them but addressing them through practices like updating instead of deleting data, ensuring staging environments match production, and using zero-downtime migrations. - **Post-Mortem Analysis**: Errors are inevitable, and establishing a post-mortem process to conduct root cause analysis helps in understanding issues and preventing future occurrences. - **Deployment Confidence**: Medynskyi describes implementing checks like validating URLs with each deployment to enhance project reliability and prevent broken pages from going live. - **Time Management**: He discusses the challenge of estimating time for tasks in software development and introduces techniques such as Planning Poker and the Pomodoro Technique to improve task management and estimation accuracy. - **Proactive Problem Solving**: He references the 'Chavez Monkey' technique from Netflix, advocating for a proactive culture where engineers search for potential problems to enhance overall quality. In conclusion, Medynskyi encourages continuous improvement and striving for excellence in software quality, emphasizing that through the right practices and mindset, developers can enhance their reliability and the quality of their work significantly.
Suggest modifications
Cancel
