|
...you haven't tested your code enough.
I'm almost ready to post a 6-part article series, and the code still scares me a little...
Did I miss something really huge that I should have caught?
Did I make an invalid assumption about the state of an object?
Could I have done this thing, or that thing, a better way?
Did I not explain something enough in the narrative?
Should I have eaten more bacon to buoy my confidence?
Fourteen assemblies spread across two solutions, and throw SQL Server and multi-threading into the mix...
This is probably gonna leave a mark.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 28-Sep-17 12:36pm.
|
|
|
|
|
John Simmons / outlaw programmer wrote: Should I have eaten more bacon to buoy my confidence?
Yes.
All the others? Probably not. Proof read it, and publish that sucker - we'll spot any problems and you can fix 'em then with the addition of more bacon.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I hope to have it ready by Sunday. I'm still making small code tweaks, and I have to run through and update the screen shots due to a significant late-breaking change.
This has been more than a year in the making, and to be honest, I don't want to disappoint anyone, although there are always a few haters, no matter what I do or how I present it. Ah well...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 28-Sep-17 12:42pm.
|
|
|
|
|
Reason for my vote of 1:
This article is far too long to read! Can't you just skip to the part about more bacon?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I've actually been down-voted because an article was too long.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Richard Deeming wrote: Can't you just skip to the part about more bacon?
I find that many different types of tests work well with bacon. A test for all types of bacon, actually. The good thing is, you have to test the entire bacon for the test to be complete.
|
|
|
|
|
Richard Deeming wrote: This article is far too long to read!
Yeah and where's the code download? Also, I cannot see the images.
You got serious work to do here. I can only give it a 1 also. 
EDIT
Ship It NOW!!!![^]
|
|
|
|
|
OriginalGriff wrote: we'll spot any problems and you can fix 'em then
The fastest way to find bugs is to put the code in production. Omega test is what I call it. I have zero confidence in testers/QA. All they do is verify that what I say the code does, is what it does. Users know if it is right or wrong... QA, not so much.
|
|
|
|
|
That's what MS do ... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
You worry too much. Let the readers critique your articles. You know they will, one way or another.
|
|
|
|
|
CP hamsters, gird thy loins! John's about to drop a big one on us!
Software Zen: delete this;
|
|
|
|
|
It only breaks if someone runs it...
|
|
|
|
|
I have proven that time and again.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
If it's perfect why test it ?
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
Code is meaningless sitting on your desk. If you caught up in "Analysis Paralysis" and don't move past the testing it's all just text files. Sooner or later you've got to publish.
I have confidence in my requirements gathering and coding skills. If I understand the requirements I know the resulting app will reflect what the customer wants and it will be right.
I'm not saying there's never going to be bugs, but I also don'y lay away at night worried that there might be some catastrophic failures that I could have caught with 5 minutes more testing.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
John Simmons / outlaw programmer wrote: Did I...
As dandy72 said. Peer review. 
|
|
|
|
|
Can't wait to see it. You usually do good stuff. I'm sure there are opinions about what could be "better", but they're both wrong and right.
Buckup, me lad!
#SupportHeForShe
Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Well,
You cannot really field test an article. However, you can field test the code in managed sessions.
That is the best way to find the first and most obvious bugs. After 17 years as a sole developer, can tell you, you cannot possibly find the last bug yourself. There are many reasons for this, the main one being, that you as a tester, have the same mindset, as you, the developer. There is no way around it, unless if you develop split personality.
After that you write the Staff training manuals.
And then you employ a Romanian girl who claims to have a degree in Wallpaper hanging, Piano Playing and Computer typing, and considers herself sufficiently educated to not to have to read the manual. She will test your system to destruction if possible.
Then, where is the fault in writing code that is not 100% free of faults. The Big Machine of Microsoft has not managed it so far. Then, you have the severity of the fault. Seriously corrupting a Database would be a serious problem. A user repeatedly having to re-enter settings would be a disaster for the user, but a minor issue to resolve from a program writing point of view. Now, you are also writing an article. I can see that this puts on more pressure. However, do never forget, on this forum you are talking to a community of friends. We are not there to do you down, we are here for each other, to provide mutual help! It is not an Exam, it is a Peer to Peer Assistance.
Well John,
You have given me sterling advice on issues in the past. I also understand your doubts. Let me know how it goes.
Regards
Bram van Kampen
|
|
|
|
|
My HDD dies (switch on machine, only got blinky light, one by one checked the bits, it was the HDD).
Sort of doesn't matter coz it was replaced with a SSD, but it was reassuring to have it still there
- held a immediately bootable image plus other ad-hoc backups. (lazy backups - no plug, just play)
OK, ordering another SSD - so used to that immediate backup, and why not make it a fast one ...
and in that I realise twas only a few years ago SSD's were (1) still somewhat expensive and (2) the failure stories on the net scared me... today I wouldn't go any other way.
Format Success.
Welcome to your new signa&*(gD@@@ ![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif) @@@@@@*@x@@
|
|
|
|
|
I'd suggest an external drive instead - you seriously want an air gap between your backups and your live data. Ransomware doesn't stop at drive C ...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I have external USB drives too,
but the always-in backup is useful too - a full bootable image included (aomei partition wiz) in case boot drive fails (or more likely I mess something up in it)
and for those quick late night backups when know you should back up your work but all you really want to do is hit the sack.
Format Success.
Welcome to your new signa&*(gD@@@ @@@@@@*@x@@
|
|
|
|
|
Lopatir wrote: today I wouldn't go any other way.
Ditto! My server and laptop are now pure SSD...my main rig still uses a HDD for the storage drive. I will probably never buy anything but SSD from here forward. The last one I bought a few months back was a 480GB for $139. (US)
As for reliability, the first SSD I bought for my h/o server over 6 years (64GB for $190) ago is still in use, having outlived a spinner installed at the same time that died a few months ago.
"Go forth into the source" - Neal Morse
|
|
|
|
|
Yoko Shimomura - The Hydrean's Wrath[^]
So I'm still playing Horizon: Zero Dawn as much as I can (which isn't nearly as much as I want).
It got me into this whole soundtrack listening vibe.
And my favorite playlist of all is my Final Fantasy playlist.
I especially like the fight music and The Hydrean's Wrath is my latest favorite FF battle music.
So I've been listening to this one a lot, enjoy!
|
|
|
|
|
Is an afterword the space bar?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
