Showing posts with label critical thinking. Show all posts
Showing posts with label critical thinking. Show all posts

Friday, October 29, 2010

How to avoid Information Overload

In the daily course of our works, we come across numerous emails from colleagues and clients as well as countless other unsavory emails uncaught by the junk filters. For the most part, it’s quick and easy to spot those unsavory emails and press the DEL key.

We all know the popular sayings of “Knowledge = Power” and what is knowledge if not information? It implies, then, that having too much knowledge is a bad thing. The real problem is that we often get copied on messages that our friends and colleagues think would help us in our daily duties when in reality they hinder us from completing our tasks effectively and timely. Then there’s the problem of people conversing using emails instead of using the more immediate communication tools such as instant messenger, phone or even simply walking-by for a chat(when it seems a walk-by-and-chat is appropriate).

So when we do get in the crossfire of people’s conversation emails—even when we are in the same project team, conversation circle, etc.—it pays to first know at the beginning whether we really want or even needed to participate in the essence of the conversation. Generally speaking, unless specifically addressed and called to answer a specific question, the simplest thing to do is to decide not to read it and any of the subsequent correspondence within the same thread. And thread is the keyword here.

Most modern email clients feature the ability to organize emails so they look like forum message threads. That’s the first and foremost what I personally do. Keeps things easy to quickly eyeball.

Second, we can (single-click) tag or flag emails that at quick glances seem important to revisit later. Forget about creating folders to categorize those emails. It takes more time than we think we have and won’t necessarily work as emails come faster than our ability to move them to the appropriate folder, especially not when today’s email clients have improved search function that can automatically create smart folders to contain the results of our searches. If anything, we’d be better off ignoring emails whose subjects are too generic to be useful as they indicate no forethought about the email itself. If one sender can’t take one minute to write a proper subject line, why must N recipients spend even one minute trying to decide whether it is worth spending more time to read and understand. It simply would be a disservice (not to mention costly in real terms) to our boss and other colleagues who are expecting us to perform our duties timely and productively unhindered by fly-by emails.

Third, also we can a mental note who among our colleagues are frequent offenders so that when email messages come from them, we can make an educated guess the likely importance of those messages and act accordingly.

Lastly, don’t return the favor, i.e., if we don’t like being blindly copied on messages that we think are not important to us then when we do get involved in an email conversation, remove all other recipients names except for the one with whom we are having it. I am a proponent of respecting everyone’s time and summarizing the conclusion of the conversation in a single email and creating a single attachment for the conversation, if we want to inform the team such conversation had taken place only for a matter of historical curiosity.

More often than not, we’ll be appreciated for not being party to exacerbating the condition of everyone else’s information overload. And most importantly, by going through the aforementioned steps regularly and consistently, we build for ourselves a habit to reduce our own being overwhelmed by things we’re unable to decide their importance.

Monday, October 04, 2010

Simple Creative-Interactive Development Approach

Preproduction:

· Brainstorm quick engagement rules.
· Gather and generate content.
· Construct the site map.
· Develop and approve and interface.
· Determine technical needs.

Production:

· Develop and refine content.
· Establish development, staging, and hosting resources.
· Get graphics production underway.
· Produce server-side support.
· Produce interactive materials.

Publication:

· Test cross-platform and cross-browser compatibility.
· Functional code review.
· Feature review.
· Coding style code review.
· Content (copy & graphics) review.
· Sign-off and deploy.

Post-Publication:

· Schedule maintenance periods.
· Schedule updates and fixes.
· Add content regularly.
· Promote site to targeted audience.
· Discuss expansion and re-design.

Organize and interview feedback and focus groups:

· Internal employees to provide management and organization needs.
· Public audience to provide likes, dislikes, and wish list.

Reuse:

· Create inventory of all existing content (brochures, graphics, interactive media, etc.).

Scheduling:

· Adherence to development schedule is a must; only one exception is allowed: unforeseen technical difficulties.

Project management:

· Although many stakeholders, there should only be single-point of authority in order to have:

  1. a final-say decision-maker; or,
  2. a tie-breaker in a round-table project discussion group.

Wednesday, September 08, 2010

Analysis and Specification Principles

More often than not, a project suffers not because of its lack of merit rather from miscommunication of intents causing grave consequences. If only we concentrate more at analyzing the subject area at the onset of a project, its probability for success can increase substantively.

1. Information Domain representation

a. Information Content and Relationships

This refers to the data themselves and their relationships to one another. For example: A “Paycheck” is composed of several pieces of data attributes belonging to different data objects such as: Employee {id, name}, Bank {name, routing number}, Instruction {net amount paid, date}, etc.

b. Information Flow

This refers to the manner in which data and their state are transformed by control objects or functions as they move through different points in the system.

c. Information Structure

This refers to the internal organization of the data and their state. For example: A “Paycheck” data could be organized in a single data table or object or in three different data tables or objects such as Employee, Bank, and Instruction and have their attributes linked to make what will be understood as a Paycheck object.

2. Models

Models are aspects of the information domain. They are abstractions that highlight important system requirements. Typically, several models are developed during requirements analysis and included in a requirements specification using a combination of graphical notations and textual annotations that may be plain natural language, e.g. English and/or a more structured language resembling a pseudo-code.

a. Functional Model

A functional model focuses on the data transformational functions in the system.

b. Behavioral Model

A behavior model focuses on the system state and event handlings (internal and external as well as user-invoked and systemic).

3. Specification partitions

a. Entity-Relationship Diagrams (ERDs) to represent Information Content and Relationships;

b. Data Dictionaries (DDs) to represent some information about Information Structure;

c. Data Flow Diagrams (DFDs) and Process Specifications, as functional models, and State Transition Diagrams as behavioral models representing information about Information Flow.

4. The Analysis and Specification Progress should cover Essential Requirements to Implementation Details in the spectrum

a. Essential Requirements

This refers to information about what needs to be done or to have (not how) with the basic understanding that human beings and other systems that the system with whom the system interacts are imperfect.

b. Implementation Details

This refers to the information about how the what will be addressed by the system.

Friday, March 06, 2009

Essential Windows PowerShell Commandlets

Previously, we learned the basic commands: help and gal. I suppose now it's time to properly refer to these "commands" as commandlets or cmdlets following PowerShell's own set of terminologies. But just to note that whenever both commands and commandlets, I use them interchangeably for the same semantic meaning. Call me stubborn. Call it bad habit. But they really are all just commands to me. In any case, although I think of all of the commandlets simply as commands, we should still mentally note at the back of our mind that for "data-typing" purposes, PowerShell truly types these items or commands as Cmdlet.

Our first essential command after learning the basics is Get-Command

Get-Command

Get-Command outputs all of the available commands in PowerShell in a clean PowerShell installation. These are the commands that we really will use as the building blocks for writing PowerShell scripts. Through a process of trial and errors, let us try to see if we can perform the obligatory, introductory of any programming lesson: print the string "Hello World!" on screen (I promise I'll keep the trial and errors to an abridged version).

  1. Type-in Get-Command at the prompt
  2. Observe the output and see if any of the command contains descriptions that indicates it is a command for printing anything on-screen by using guess-words such as: "Print", "echo", "Write", "Response", or any other words from whatever your other experience may have been.
  3. If nothing on-screen indicates as such, then you'll want to type in help [Cmdlet name] at the prompt to read the details one-by-one. Hey at least that's how I started learning PowerShell, by reading documentation as well as by trial and errors.

But, let's use my experience, shall we? Let's just type in the following simple command, and we'll simply get the result we want just as we'd see in Listing 1.

Listing 1: PS C:\Users\antonius> gcm | where {$_.definition -match ".*print*"} CommandType Name Definition ----------- ---- ---------- Cmdlet Out-Printer Out-Printer [[-Name] <string>] [-InputObject <psobje... ps c:\Users\antonius> gcm | where {$_.definition -match ".*echo*"} CommandType Name Definition ----------- ---- ---------- Cmdlet Set-AuthenticodeSignature Set-AuthenticodeSignature [-FilePath] <string []> [-C... PS C:\Users\antonius> gcm | where {$_.definition -match ".*write*"} CommandType Name Definition ----------- ---- ---------- Cmdlet Write-Debug Write-Debug [-Message] <string> [-Verbose] [-Debug] ... Cmdlet Write-Error Write-Error [-Message] <string> [-Category <errorcat... cmdlet write-host write-host [[-Object] ><object>] [-NoNewline] [-Separ... Cmdlet Write-Output Write-Output [-InputObject] <psobject []> [-Verbose] ... Cmdlet Write-Progress Write-Progress [-Activity] <string> [-Status] <strin... cmdlet write-verbose write-verbose [-Message] ><string> [-Verbose] [-Debug... Cmdlet Write-Warning Write-Warning [-Message] <string> [-Verbose] [-Debug...

From these output we can sort of guess which command we can use, but if in case we're still in doubt we could always do help write-debug, help write-error, etc. Soon after we go through this we'll find the command we want to use is Write-Output.

That's a rather "long" command to type, though. Let's try to see if there's a shorter version of it. For this purpose, let's try what's on Listing 2.

Listing 2: PS C:\Users\antonius> gal | where {$_.definition -match "Write-Output"} CommandType Name Definition ----------- ---- ---------- Alias write Write-Output Alias echo Write-Output

Now that we found what we want, we can try either command aliases just as in Listing 3

Listing 3 PS C:\Users\antonius> write "Hello World!" Hello World! PS C:\Users\antonius> echo "Hello World!" Hello World!

Sure enough, we found both yield the same result

We might wonder, "Why are there two aliases for the same command?" I don't really know the answer to that question other than perhaps the alias write is the built-in alias for Write-Output and perhaps the alias echo is simply a way to help those who are used to writing .BAT scripts to transition a little more easily to Windows PowerShell. Whatever the answer to that question is rather irrelevant; what's more important is that now we've gone through the basic exercises in learning each PowerShell command.

Wait wait wait!!! We're not done here!

What's all that business with the where command and the rest of the strings following it?

No, I didn't cheat :)

I simply wanted to shortcut all the trial and errors I went through in learning PowerShell without filling the content of this notes full of garbage. Trial and errors, after all, are things we each can do individually on our own time. As for the shortcut strung with the where command, I'll note an explanation of it another time.

Tuesday, March 03, 2009

Basic Windows PowerShell Commands

Windows PowerShell is relatively new shell command interpreter in comparison to the venerable CMD, CScript, and Windows Script Host.

Just like any shell script, it isn't really difficult to learn simply by trial and errors as long as we get the few basic commands down so we can drill further to other commands we seek to use.

The most basic command we should know is, of course, help.

Get-Help

As the command name suggests, it is the single command we use to see the details of a particular command we submit as a parameter to the help command. Listing 1 below illustrates the help command execution.

Listing 1: PS C:\Users\antonius> help help NAME Get-Help SYNOPSIS Displays information about Windows PowerShell cmdlets and concepts. SYNTAX Get-Help [[-name] <string>] [-component <string []>] [-functionality <string []>] [-role <string []>] [-category <string []>] [-full] [<commonparameters>] Get-Help [[-name] <string>] [-component <string []>] [-functionality <string []] [-role ><string []>] [-category <string []>] [-detailed] [<commonparameters>] Get-Help [[-name] <string>] [-component <string []>] [-functionality <string []>] [-role <string []>] [-category <string []>] [-examples] [<commonparameters>] Get-Help [[-name] <string>] [-component <string []>] [-functionality <string []>] [-role <string []>] [-category <string []>] [-parameter <string>] [<commonparameters>] DETAILED DESCRIPTION The Get-Help cmdlet displays information about Windows PowerShell cmdlets and concepts. You can also use "Help {<cmdlet nam e> | <topic-name>" or "<cmdlet-name> /?". "Help" displays the help topics one page at a time. The "/?" displays help for cm dlets on a single page. RELATED LINKS Get-Command Get-PSDrive Get-Member REMARKS For more information, type: "get-help Get-Help -detailed". For technical information, type: "get-help Get-Help -full".

It's so helpful that we can simply type help help at the prompt to display the details of the help command itself. As we examine the command output's "Related links" section, we see three other commands related to the help command. All the three new commands we found here: Get-Command, Get-PSDrive, and Get-Member are part of the important basic commands we will discuss more thoroughly a little later.

Get-Aliases

"Shallow Hal wants a gal."

The second basic command that is most useful to expedite our PowerShell command study is Get-Aliases also aliased as gal. First, we're gonna combine gal with the first command we learned earlier: help in Listing 2. Then, we'll try to see if sending the command twice to the shell prompt, one as the command call itself and another as the paramater to the command call gal gal in Listing 3.

Listing 2: PS C:\Users\antonius> help gal NAME Get-Alias SYNOPSIS Gets the aliases for the current session. SYNTAX Get-Alias [[-name] <string []>] [-scope <string>] [-exclude <string []>] [<commonparameters>] DETAILED DESCRIPTION The Get-Alias cmdlet gets the alternate names for cmdlets, functions, and executable files that have been established for the current session. This collection includes built-in aliases, aliases that you have set or imported, and aliases that you have added to your Windows PowerShell profile. If you specify one or more aliases, Get-Alias gets the alias object and displays its properties, including the object that was aliases, such as the full name of a cmdlet. This feature is made available by the Windows PowerShell Alias provider. RELATED LINKS Set-Alias New-Alias Export-Alias Import-Alias REMARKS For more information, type: "get-help Get-Alias -detailed". For technical information, type: "get-help Get-Alias -full".Listing 3: PS C:\Users\antonius> gal gal CommandType Name Definition ----------- ---- ---------- Alias gal Get-Alias

See! It's simple right? From Listing 2, we find the usage details of the command gal, and from Listing 3, we find that gal itself is an alias of the command Get-Aliases.

But, but, but... How did I know in the beginning that help and gal are commands we can execute? The answer is as ordinary as it could be—I guessed the first command: help presuming that a program usually has a variation of help, --help, --h, man or the old-school /? in some sort of form even without reading its documentation. As for the command: gal, after having found out that while the command help could be executed and yields an output indicating the actual command name: Get-Help, I simply sought in MSDN PowerShell site a reference entry pertaining to available command aliases.

Up next... We won't need to go through the details of each command, but will start our PowerShell exercises by using the three new "related" commands we learned earlier from Listing 1.

Friday, April 25, 2008

Information is to knowledge as...

Bit is to Byte.

Byte is to data.

Data is to information.

 

A computer is such a nice tool to collect, prepare / process, and consume knowledge. But nice is different from easy. The level of ease in using computer for the aforementioned activities however are usually inversely proportional to one another. For example, if it could be considered easy to collect data, it can be reasonably said (and observed) that the data processing is relatively more difficult than the its collection; or so the logic dictates, for what it's worth.

Fast forward to preparing cubes for SQL Server Analysis Services, I found myself trying to figure out how to prepare an ease of processing for my work product's audience, starting with its setup. After a little bit of struggle through the various binaries in my machine, I found the following steps helpful for those of you trying to do the same:

Local environment variable path setup:

  1. Add to your local environment path an entry pointing your VS.2005 IDE location (screen Evp1.1 - 1.4).
  2. Add to the same local environment path another entry pointing to the location where you find Microsoft.AnalysisServices.Deployment.exe, if it isn't already there. (Notes local environment path entries are separated by semi-colon).

Screens:

Evp1.1evp11 Evp1.2evp12

Evp1.3 evp13 Evp1.4 evp14

 

The lazy version:

  1. prompt:> devenv [solution filepath and filename] /deploy

Well... sure you might run into a couple of pop-up dialogs, but just a couple of OK clicks without knowing what they mean will put you back on the processing track. No worries though, even when you don't click the buttons until the end the show will go on until completion with the exception that the thread is still be hanging until said clicks are made.

If you're bothered by the only seemingly semi-autonomous run (since you still may be needed for those two manual clicks), here's another way to do it... properly... starting with the same local environment path setup steps above, then followed by these steps:

  1. Build the .asdatabase file from your solution file using prompt:> devenv [solution filepath and filename] /build
  2. The deploy using prompt:> microsoft.analysisservices.deployment [solution filepath]/bin/[project name].asdatabase /s:[deployment log filepath and filename]

A word of caution: Don't be alarmed if your screen seemingly freezes during the deployment; this will likely be the scenario depending on your hardware configuration and the volume of data in your database that Analysis Service engine processes.

Why do we want to go through this when we can just load the solution file in VS.IDE then with just a few clicks to the above easily without having to memorize seemingly arcane and puzzling commands and steps? There are several different answers to this, but my favorite one doesn't have anything to do with it as knowledge that reliable technician needs to have; rather, it has to do with the pursuit of knowledge itself.

If our knowledge is the sum of our experience, and if we postulate that human beings learn more from difficult experience than an easy one, then it follows that by doing the above steps we will retain this knowledge longer that had we just done the usual mouse-clicks. And that my friend is what knowledge is to an application...

Thursday, March 27, 2008

To be gainfully employed is...

A rather challenging act to perform.

It's not just about having a job nor about the money that the job brings.

It is a constant juggle to balance our personal and professional lives.

I've shared with many people I encounter in my careers a personal attitude that may help reduce one's own stress in a work setting and be able to feel secure on and of our own: that work is just a vehicle for us to meet new friends and earn income to support our family.

Professionally, the level of quality of my output and my team's output is much less driven by our individual talents, but more about the principles we go by and use in our teamwork:

  • Kanban: Just-in time (classic production understanding in manufacturing industry of what's now called Agile in the software industry).
  • Kaizen: Continuous improvement; our work is never done, even when the output has shipped. This translates personally to set a goal where we can pace ourselves according to our health and ability and professionally to always understand that the best we deliver today should hopefully be better tomorrow.
  • Gandhi engineering: A combination of irreverence toward established way with a scarcity mentality that spurns superfluities while at the same time maintaining consistency of applying the principles in play.
  • Einstein tolerance: That can't be paraphrased, but simply understood in what Albert Einstein himself said: "Great spirits have always found violent opposition from mediocre minds. The latter cannot understand it when a man does not thoughtlessly submit to hereditary prejudices but honestly and courageously uses his intelligence and fulfills the duty to express the results of his thoughts in clear form", to help us maintain composure in an adversarial environment. This also relates to what I wrote earlier in my post: The 道 of Writing, the sublime of Work Ethics...

Friday, February 01, 2008

Holy chocolate fudge!!! Quick! Show the window pronto!

The first month of 2008 came and went.

We've gone through 31 days of a new year so quickly, we barely had a chance to reflect on the past year due to piles of backlog tasks that seems to increase faster than we can keep up. It's a blessing and a curse.

Speaking of a curse, I was in the middle of debugging an application last night and was unable to find the Immediate Window in my VS2005 IDE. It had been there before; I sought for it in all of the menu and sub-menu items and couldn't find it. I still don't know what caused its disappearance. Perhaps it was a recent VS2008 IDE installation that might've affected the 2005 environment settings; perhaps others unknown reasons.

Suddenly, a simple thought sprang to mind bulb : go to Tools/Customize/Debug and simply add it back-in to the menu bar and my shortcut toolbar. Et voilà! My indispensable Immediate Window returns; and all is well.

Thursday, September 20, 2007

The 道 of Writing, the sublime of Work Ethics...

Be it software, technical documents or emails.

If any man wish to write in clear style, let him be first clear in his thoughts; and if any would write in a noble style, let him first possess a noble soul.
~ Johann Wolfgang von Goethe

Learn as much by writing as by reading.
~ Lord Acton

I too am an apprentice, always—learning as much by failing as by succeeding, as much by following as by leading.
~ antonius

So don't despair that no one agrees with you and point your mistakes, for "... when you're screwing up and nobody's saying anything to you anymore, that means they've given up on you."
~ Randy Pausch

Wednesday, July 25, 2007

Software Entropy

Software entropy refers to the amount of disorder present in a system.

Entropy usually creeps in by way of logical inconsistencies at the thought-level, even before any tangible work begins to implement said system. As the system and its parts are developed, these logical inconsistencies manifest themselves in various forms of errors of all sizes. The smallest ones considered negligible are typically the clichéd primordial stew of chaos in software systems.

When coupled with what's frequently unfortunate timing of most software development schedules, the hacks we are forced to place into the system here and there by necessity of meeting some established deadline further exacerbate the condition.

Now plagued with such level of anomalies any additional issues encountered are prevented from meeting their resolutions simply because it's no longer feasible.

They say, only two things are certain in life: Death and taxes; well... in software Chaos reigns supreme if unchecked and snipped in the bud. Entropy is contagious.

What's the moral of the story kids?

 

冰冻三尺,非一日之寒
Three-feet of ice didn't result from one day of freezing weather.

 

Do the job right the first time or don't do it at all.
Better yet, get out of the way of anyone who's trying to do the job right the first time.

Friday, June 15, 2007

Consistent Efficiency Is Key

Task:

  • Find today's calendar period starting and ending date, where if the starting date is the 1st then the ending date should be the 15th, and if the starting date is the 16th then the ending date should be the last date of the month.

Short of writing the date with a string, which of the two following methods demonstrates a clear logical thought? (Disregarding the conciseness of the code).

Method #1:

method1 

Method #2:

method2 

When seen from the biggest picture, i.e., a total development project cost (and/or tco) of $1, the two methods above demonstrate a difference between:

  • Getting much less value of the $1 payout albeit with a lot of code line count (and a potential debugging and maintenance nightmare); versus,
  • Getting much more value from the $1 payout including clarity of thought, code conciseness, ease-of-debugging and most neglected value of all savings in maintenance cost.