What do you mean by Bullet Proof? Do you want your app more secure? Or better performance? Or more stable? Or something else?
What are the problems with your current apps security/stability/performance that you are trying to solve?
Up until recently, I was only a low level programmer. Well, except back in the dos days or should I say the Novell days. Back then, I went through the keyboard and hit every key to verify it wouldnt crash my program. I wrote custom software back in those days and my products ran for years with no bugs.
Recently, I started doing Web developement. Our company also has a team programming ASP.NET stuff. But their stuff crashes all the time. And sometimes for the craziest reasons. Web went down, lost connection, email was not available, virus software blocked it, Microsoft. They have crashes they can not figure out why it happened. Since I am the Flash Builder person, I dont want that egg in my face. I want my apps to be bomb proof. So I am looking for something where I can learn from others who have already didnt think of that and their program crashed, they found the solution and would like to pass it on to the rest of us. It appears as if being bombproof is not as easy with web developement as it was back in the dos days.
This is only really accomplished through extensive testing and error trapping these days.
Many people make assumptions in the apps they build, though. On an web based app they may assume that an Internet Connectil will always be available and not test for the condition of "lost Internet"
I can't speak to the type of stuff you were developing in the 80s vs the type of stuff you are developing today; but I would expect that if the complexity is equal, you should be able to make it bullet proof with similar amount of effort.
So as far as you know, there are no books or web sites who would assist in the discovery of these kind of issues?
I don't think there are many books on this issue of "bulletproofing". Since Flex/AS3 isn't a low-level language, you generally don't have all the horrors that accompany a low-level language. My most fearsome error is the null pointer error ( #1009 ). If you want to make sure your stuff is tight as far as business logic and application behavior is concerned I would look into incorporating unit testing into my application. That will help smoke out a good percentage of bugs.
I think what you are looking for is Unit Testing.
I do not know of any books that cover this topic, but I'm sure they exist. I personally prefer online (free) resources myself.