This message will be repeated in english.
Hur får man rättningar och funktionalitet så fort som möjligt genom dörren?
Hur får man så få buggar som möjligt i produktion?
Jag fick en gång kommentaren från en vän "Men du levererar väl aldrig otestad kod?". Det var en komplimang och en kommentar till att jag just då satt i ett projekt som skulle leverera den högsta kvaliteten jag levererat hittills, dessutom rakt ut i fabrik
Mitt svar förvånade honom "Jag testar inte." Jag lät honom hämta andan. "Rättning: jag testar så lite som möjligt och mycket kod går rakt ut i produktion otestad."
Sedan följde en förklaring. En förklaring jag har dragit för alla i projektet:
"Använd kompilatorn för att fånga fel."
Vanligtvis när man talar om system med hög kvalitet pratar man om testning. Massor med manuella tester med speciella konsulter man hyr in som är specialiserade på test. Dyrt. Men det blir dyrt med hög kvalitet.
Bullshit.
Manuella tester är dyrt och tar lång tid.
Modernare utveckling innehåller enhetstester.
Jag förespråkar Fail At Once för att slippa många enhetstester och manuella dito.
Det är viktigt att fånga fel så fort som möjligt. De allra bästa är att inte skriva dem alls.
Där är jag inte ännu.
How do you ship patches and functionality as fast as possible?
How do you get as few bugs as possible in production?
I once got a comment from a friend "But you never deliver untested code?" It was meant as a compliment and comment to my job then; I was working in a project that was delivering the highest quality I have ever delivered; right onto factory floor.
My answer surprised him "I don't test." I let him catch his breath. "Correction: I test as little as possible and as much code as possible goes into production untested."
I had to explain, the same explanation everyone in the project had heard.
"Use the compiler to catch errors."
Normally when one talks about high quality system one also mentions testing. Lots of manual tests with consultants specialised on testing. Expensive. But high quality is expensive.
Bullshit.
Manual tests are expensive and take lots of time.
The more modern unit testing is cheaper.
I recommend Fail At Once to get rid of many unit tests and manual ditto.
It is important to catch errors as fast as possible. The best is to not write them at all.
I am not there yet.
skip to main |
skip to sidebar
http://www.selfelected.com/
Experience about programming and architecture
Musings about delivering and quality
Findings about projects and people
THIS SITE HAS MOVED
COMMENTS ARE DISABLED AND ARTICLES ARE COPIED AND EVERYTHING IN THE PRESENT AND FUTURE WILL HAPPEN ON
http://www.selfelected.com/
Software patents halts innovation.
Please sign the petition for the sake of all of us.
Credits
Go to ms K for keeping me sane.
Go to mr J for the laughs and the truth.
Go to ms B for naming this blog.
Go to mr J for the laughs and the truth.
Go to ms B for naming this blog.
About Me
- LosManos
- Göteborg, Sweden
- Developing solutions mainly on the Windows platform during my working hours. Hoping to make the world a better place the rest.
My other projects
LIUSClasses
Handy dotnet functions, unit tested and proven in production
EarClip
Keep you bookmarks online - 0.6
Kopain
Simple editor with a tree navigator - 0.1
Selfelected ideas
Another blog which just contains ideas.
Handy dotnet functions, unit tested and proven in production
EarClip
Keep you bookmarks online - 0.6
Kopain
Simple editor with a tree navigator - 0.1
Selfelected ideas
Another blog which just contains ideas.
Heroes, in alphabetical order
Tools
Agent Ransack
A good file searcher that is both simple to use and have regular expression for the more advanced user. It of course searches the folders that Micorosft's built-in avoids. Cost free.
Autohotkey
Global hotkeys. A simple scriptable solution to utilise the windows button. Start an application or simulate the keyboard with a simple keystroke. Open source.
DPack
A must-have tool for VSNet2003/5/8. The functionality I use the most is alt-M to list and easily search through methods in the active file and alt-U to open files without having to search for them in the project explorer. Free.
Keepass
This is a password storer. It is open source to make sure the encryption is valid. I use the older 1.x version since it has the same database as the Windows Mobile client. This makes it possible for me to always have my passwords at hand.
Keynote
A simple hierarichal text editor. Bring it up with a keystroke, jot down your notes, let it vanish. Open source.
c# code format
A gratis solution for CSSing source code for use in blogs like this.
Notepad2
An open source text editor. It is not the best but it replaces Notepad in a correct way and hence gets rid of the bugs in Notepad.
Pastebin
A free site for discussing code instead of pasting it back and forth in chat or email. Easier to try than to explain.
PDFCreator
I you want to create PDF documents but don't want to spend money on Adobe's bloated solution do use this open source PDF printer. It installs a printer and when printed to creates a PDF document on your hard disk. Works for any application that can print.
Spamgourmet
A free site for one time email addresses.
Winmerge
A nice diff tool. Compares files and directories. Much better than Windiff/Sourcesafe. Open source.
A good file searcher that is both simple to use and have regular expression for the more advanced user. It of course searches the folders that Micorosft's built-in avoids. Cost free.
Autohotkey
Global hotkeys. A simple scriptable solution to utilise the windows button. Start an application or simulate the keyboard with a simple keystroke. Open source.
DPack
A must-have tool for VSNet2003/5/8. The functionality I use the most is alt-M to list and easily search through methods in the active file and alt-U to open files without having to search for them in the project explorer. Free.
Keepass
This is a password storer. It is open source to make sure the encryption is valid. I use the older 1.x version since it has the same database as the Windows Mobile client. This makes it possible for me to always have my passwords at hand.
Keynote
A simple hierarichal text editor. Bring it up with a keystroke, jot down your notes, let it vanish. Open source.
c# code format
A gratis solution for CSSing source code for use in blogs like this.
Notepad2
An open source text editor. It is not the best but it replaces Notepad in a correct way and hence gets rid of the bugs in Notepad.
Pastebin
A free site for discussing code instead of pasting it back and forth in chat or email. Easier to try than to explain.
PDFCreator
I you want to create PDF documents but don't want to spend money on Adobe's bloated solution do use this open source PDF printer. It installs a printer and when printed to creates a PDF document on your hard disk. Works for any application that can print.
Spamgourmet
A free site for one time email addresses.
Winmerge
A nice diff tool. Compares files and directories. Much better than Windiff/Sourcesafe. Open source.
Labels
- architecture (15)
- code (7)
- database (9)
- documentation (7)
- fail-at-once (6)
- innovation (1)
- misc (36)
- not-yet-fully-invented (16)
- project (25)
- solid code (31)
- strong typing (4)
- tip (22)
- wishlist (4)
2 comments:
// This message in English only
I hear you and I agree up to a point. To let the compiler catch the bugs catches most programming errors but it does not catch the hard to find and often dangerously destructive ones, i.e. the logical errors.
The compiler can never know if you in your comparison used the correct comparison operand, and there is a big difference between >, >=, ==, <=, <, !=, etc. Logical errors are easily found by unit tests that check both normal and extreme value scenarios. Or you could do the same test manually but that would be long and tedious work.
Exactly.
Just like unit tests don't catch all errors, Fail at once does not catch all errors.
Heck, even manual tests don't catch all errors.
The idea is to use Fail at once to write fewer unit tests to write fewer manual tests.
To in the end get the same result with less code to maintain.
Post a Comment