Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
IBM Lotus Domino: Classic Web Application Development Techniques

You're reading from   IBM Lotus Domino: Classic Web Application Development Techniques This tutorial takes Domino developers on a straight path through the jungle of techniques to deploy applications on the web and introduces you to the classic strategies. Why Google it when it‚Äôs all here?

Arrow left icon
Product type Paperback
Published in Mar 2011
Publisher Packt
ISBN-13 9781849682404
Length 344 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Richard G Ellis Richard G Ellis
Author Profile Icon Richard G Ellis
Richard G Ellis
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

IBM Lotus Domino: Classic Web Application Development Techniques
Credits
About the Author
About the Reviewers
www.PacktPub.com
1. Preface
1. Preparation and Habits FREE CHAPTER 2. Design and Development Strategies 3. Forms and Pages 4. Navigation 5. Cascading Style Sheets 6. JavaScript 7. Views 8. Agents 9. Security and Performance 10. Testing and Debugging

Debugging


It is possible to write some code which runs perfectly the first time and does exactly what it is supposed to do. It happened to me once, and I was quite surprised. Without doubt, developers spend a good deal of time debugging and troubleshooting. This aspect of development can be extraordinarily frustrating, especially if you are under deadline or not very good at it. But successfully "shooting a bug" can also be quite satisfying.

Troubleshooting skill is partly technique, partly knowledge, and partly intuition born of experience. I suspect most developers would be hard-pressed to tell you how they do what they do. But you should get better at it the more often you do it.

General guidelines

Like a detective, troubleshooting a problem is first about gathering evidence or clues, and then it's about putting those clues together to point to the source of the problem. When presented with an issue, gather information from log messages, screen shots, output files if you've been a developer...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image