Skip to main content

Why You Need a New Error Handler

Error handling is an integral part of application development. Unless you are like myself and never release code with bugs :) , the need for clients to tell you what's wrong is important.

I've seen a number of error handlers in the past, dating all the way back to Pat Adam's famous FP2ERROR routine (back from 1991).

Most systems log their errors and then pick them up as part of a diagnostic push. Unfortunately, reporting these errors back to the developer require some effort by the client.

Doug Hennig has introduced a new VFPX project for adding easy error handling and reporting. While it does include a few dependencies, it offers a nice support-centric dialog for clients to report errors.

https://doughennig.blogspot.com/2021/07/new-errorhandler-vfpx-project.html

If you AREN'T getting automatic feedback from your clients when they get an error, now there's no excuse.

Comments

Post a Comment

Popular posts from this blog

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...
Post a Comment
Read more

I’m Supposed to Know

https://programmingzen.com/im-supposed-to-know/ Great post for developers who are struggling with unrealistic expectations of what they should know and what they shouldn't. Thirty-forty years ago, it was possible to know a lot about a certain environment - that environment was MS-DOS (for non Mac/UNIX systems). . There was pretty much only a handful of ways to get things going. Enter networking. That added a new wrinkle to how systems worked. Networks back then were finicky. One of my first jobs was working on a 3COM + LAN and it then migrated to LAN Manager. Enter Windows or the graphical user interface. The best depiction of the complexity Windows (OS/2, Windows NT, etc) introduced that I recall was by Charles Petzold (if memory serves) at a local user group meeting. He invited a bunch of people on the stage and then acted as the Windows "Colonel", a nice play on kernel. Each person had a role but to complete their job they always had to pass things back to h...
Post a Comment
Read more