# Saturday, August 22, 2009

Quite a while ago, I had a fairly bad experience at Stack Overflow and wrote a blog post about it:

StackOverflow Impressions - Too Many Rough Edges

I have now returned to being a contributor at Stack Overflow.  But why?

More and more Google searches are leading me to Stack Overflow for answers.  The answers are often useful.  Stack Overflow has no meaningful direct competition.

I'm a pragmatic person and I appreciate that the service provided by Stack Overflow is useful.

Since I'm gaining value from the site on a regular basis now, it makes sense to try to help out and "give back" to the community by providing answers when possible.

Stack Overflow is "good enough" to support.

Also, while I believe the benefits of putting a Stack Overflow reputation number on a resume are overstated (and include some small amount of risk), I do think asking and answering questions on Stack Overflow is an important indirect marketing opportunity for individuals.  As one example, if a blog post I've written answers a question some one asked, answering the question on Stack Overflow with a pointer to my blog post is helpful and increases the useful life/value of that blog post.  I think blog posts are a great way to expand the programmer knowledge base, but not all blog posts will be easily found through Google searches (Providing links to your blog from Stack Overflow will not increase your blog's page rank, but people will click through none the less).

Saturday, August 22, 2009 1:59:00 PM (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  | 
# Sunday, August 16, 2009

After a number of small releases focused on application infrastructure, this release is a semi-major user focused feature release.

The biggest new feature is treating function parameters as obfuscatable variables.

A user requested that function/variable names not grow in size as part of obfuscation, so function/variable names now stay the same size.  This may continue to be refined over time depending on what people think.

Since this obfuscator was originally written for my own use, it made some assumptions about coding style, especially in regards to whitespace.  A number of those types of assumptions have now been removed based on testing against code submitted by users.

While some substring type issues still remain, it is now possible to have local variables which are substrings of one another like "counter" and "counter1" without the obfuscator missing a beat.

It used to be possible to have a variable named "funct" (which is a substring of the lua reserved word "function"), but this is no longer allowed.  More work is needed in this area (not mangling lua reserved words) going forward.

The latest version of the Capprime Lua Obfuscator is available here:

http://www.capprime.com/CapprimeLuaObfuscator/CapprimeLuaObfuscator.aspx

Sunday, August 16, 2009 12:30:13 PM (GMT Daylight Time, UTC+01:00)  #    Disclaimer  |  Comments [0]  |