Scott Auge's blog

An inexpensive means of product research

I was watching the Charlie Rose interview with Marc Andreessen and he mentioned an interesting and inexpensive means of product marketing research.

Google Adwords.

Before even laying down a stitch of code, go out and buy some ad words based on the features or industry or demographic for your product. It doesn't have to even go to a real page (of course you probably don't want to screw your domain so use another) - just use the web site to pick up on how much interest there is in that product.

See the interview here:

http://www.charlierose.com/view/interview/10093


Include Unit Code at the bottom of your class files

One of the important things in software development is to do unit testing - that is a set of tests the programmer can do on a piece of code to be assured it is most likely working the way one wants it to.

Surprisingly it is rare to find unit test code as part of a source code file. If it is created at all (horror), it is usually tucked away on some developers disk someplace or simply thrown away!

What I have found helpful for myself as well as others working the same code, is to place a comment at the end of the program with the unit test code.


A simple tool to help generate webspeed code.

There are times when you create a web page with many html inputs. Creating the get-value() and variables for the logic of the program can be tedious and time consuming. This routine can help you generate the code automatically.

Simply feed it the HTML page (javascript and speedscript doesn't mean anything to it) and the output file you want the code to be contained in.

See attached file as code is maligned by the wiki.


Security of the ABL language

Upon reading the blogs at computerworld.com (or infoworld.com - I can't remember) I came across a PDF report on safe coding practices (which can be found here http://www.safecode.org/publications/SAFECode_Dev_Practices1008.pdf ).

While the PDF has some ideas on management oriented safe practices, it does delve a little into safe practices regarding technology. What it doesn't is how it applies to ABL coding.


Syndicate content