Explore >> Select a destination
|
You are here 
|
adventuresinqa.com | ||
| | | | |
developsense.com
|
|
| | | | | Why do we refer to the real requirements for a product as 'non-functional' requirements? Here's a short video in which I talk about that. https://youtu.be/f | |
| | | | |
mbuffett.com
|
|
| | | | | Abstractions are the best Your code will be safer and more readable. It will prevent entire classes of bugs. It will be easier to add new features. You can inject dependencies at runtime to make testing easy. You can swap out your third party dependencies. You can adapt quicker to business logic changes. You can treat X and Y as the same thing. They're both forms of Z, after all. | |
| | | | |
developsense.com
|
|
| | | | | A recent posting (apparently no longer available) on LinkedIn entitled "Why Is Automated Software Testing A Better Choice?", prompted some discussion. (As usual | |
| | | | |
perlhacks.com
|
|
| | | A series of three articles about CGI programming that I wrote for Linux Format in 2001. Please note that these tutorials are only left here for historical interest. If you are writing new web applications with Perl these days, you should be considering something based on PSGI and Plack or even something using raw PSGI. | ||
