My Pinned Wiki Post Template

If you use this, please link to this blog post.

This is our Wiki

There are many like it, but this one is ours.

Our wiki is our guide. We support our wiki through comments and additions.

Without updates, our wiki will become outdated. Team members will become frustrated when information is missing or no longer correct. Being a good team member includes being a contributor to the wiki.

That cool reference you found that you will always remember? One day, when you need it most, you will forget it.

That awesome solution to a code or design issue that is perfectly clear and understandable now will look like a foreign language in 2 years (months, weeks, sometimes even hours). Add an explanation to the wiki.

When in doubt if something should be added to the wiki, add it. It can always be deleted later.

This is your wiki. Keep it clean but not too lean.

The Architect
(A serious parody of The Rifleman’s Creed )

(“Obligatory WIki Photo” by cogdogblog is marked with CC0 1.0. To view the terms, visit

© Scott S. Nelson

Provide Document Feedback for Efficiency

When providing document reviews with comments or track changes, most people start writing their comments as they read through. This is perfectly natural and recommended, as capturing your thoughts immediately is the best way to ensure they aren’t forgotten. That said…

As you read through the document, some of your comments made earlier may be addressed later in the document. If you think the content should be moved, this is a good time to point that out, referring back to your earlier comment. If not, take the time to move the comment to the appropriate point, or revise it accordingly.

Short-term memory varies between person to person and even context to context. A comment provide early in the doc is likely to be remembered and reference back when it discovered at the end that it was not necessary if the review is done in a single sitting or as part of a very focused project. Then again, someone stopping by to say “hi” or an IM popping up immediately after writing a comment can pop the memory out of the short term queue and only invoke vague familiarity if the concept is addressed later. Because of this unplanned and unschedulable variation in memory reliability, I suggest re-reading through all comments prior to submitting them. It will (hopefully) catch those forgotten inputs that should be revised in the context of the entire document so that the sent input is concise.

The value of concise input is two fold: It makes it easier for the person receiving the feedback to apply it where needed, and it avoids the frustration of seeing comments from a review that the author knows are not valid because they are addressed later on.

© Scott S. Nelson

Just Like the Good Ole Days

Back when 14.4k baud modems were fast, mice were beige, IBM made PCs, and new software versions were relased annually instead of weekly, software came with useful, intiutive manuals that included tutorials for everything you needed to get up and working.

Other than the ability to take the manual in its binder to the couch to flip through, dog ear and highlight, I was happy to discover a full set of training buried in the doc folder of the Oracle Database install (and many other of  their applications, though location may vary).

Even if you don’t have the full install, the 2 Day DBA and other really useful documents can be found online, too. The 10.2 version is located here:

© Scott S. Nelson

Latest Article

When my articles appear on, they have 120 days exclusive rights. Rather than have readers wait four months,  I post a link to the article here (when I remember to).

The latest is 10 Things You Should Know About WebLogic Server 10.3, handy if you are considering a move to the latest version of WLS.

© Scott S. Nelson