Presented by:
John Ashmead
John Ashmead has been working with relational databases since the 1980's, building & enhancing databases in SQL Server, Oracle, Informix, Ingres, and PostgreSQL.
For the last five years he has been the DBA & database developer at a leading manufacturer of Optical Switches. John is in charge of the care & feeding of the manufacturing database (Javascript/Ruby-On-Rails/PostgreSQL). For the last six months he has been porting the manufacturing database to a factory in Zhuhai, China.
John gives frequent talks at database & other programming users groups. He is working on a book Zen and the Art of Debugging, about one of the most under-appreciated but important aspects of software.
He has also given physics related talks at physics conferences, science fiction conventions, and NASA. His most recent physics paper is “Time dispersion in quantum mechanics”.
Depending on the project, debugging can take 50 to 90% of development time. But it usually gets less than 10% of the press. PostgreSQL has great tools for debugging, but they are most effective when deployed as part of an overall strategy.
We will look at strategies for debugging PostgreSQL: how to find bugs, how to fix them, and how to keep them from happening in the first place.
We’ll look at root causes, technical tricks, and scientific strategies, and why — even if you can’t always write perfect code — it is usually a good idea to try.
We’ll hear from Bjarne Stroustrup, Sherlock Holmes, Kernighan and Ritchie, Pogo, & the experts of the PostgreSQL community.
Goal: less time debugging, more time building great tools and apps that stay up & get the job done.
- Date:
- Duration:
- 50 min
- Room:
- Conference:
- Postgres Conference 2020
- Language:
- Track:
- Development
- Difficulty:
- Easy