– Home


First, welcome to To best express the goal of this site, I'll start with the site's name. The site's name is comprised of two words: tech (short for technical), and pang.

Technical is loosely expressed on this site, as the content does not strictly tie to technical subjects. However, the majority of the content will relate to technical subjects, and/or apply to those in technology.

Pangs. Well, when I was trying to find an available name for the site, I tried several different combinations. My "first choice" names were either taken (and most not in use, or really poorly designed sites), or squatted--a term used for a site name that was purchased by an individual or company, with the sole purpose of selling it to the highest bidder. So, I landed on pangs. As I selected this, however, I felt that I was pretty lucky that the first choice names weren't available. Pang, as defined by Merriam Webster®, is a sudden, strong feeling of physical or emotional pain.

Lumping the two words together, I arrived at a great correlations with the purpose of the site, showing the pain associated with technology subjects, and helping demystify them. This site is for those familiar, or unfamiliar, with technology. I try to write in such a way that people can grasp a relatively good understanding of the subjects.


Enterprise technology topics are relevant to any number of technologies that are leveraged in businesses. Generally a label enterprise is applied to larger businesses, or those that have multiple locations.

fragment  of complicated laboratory laser system with bright yellow light generated inside crystals
Bleeding Edge

Bleeding edge technologies are those that are very new, and do not have the adoption rate necessary to have been leveraged of a large number of businesses. There is a much higher risk with these technologies; those who implement them are generally pioneers.

Woman hands holding blank old book and modern tablet device on wooden planks. Classical and modern reading concept
Fading or Dormant

Fading, or dormant, technologies are those that still serve the purpose for which they were invented. But, as time has passed, newer technologies have surpassed them for lower costs, or augmented functionality. The timing does not correlate directly to time, as a newer technology can replace a prior technology in a rather short period of time.


Project Management – The Unsung Hero

I’ve seen it more times than I can remember; I’ve read it twice as much....
September 2, 2017

Apple – Part II

It has been a good while since I’ve provided any commentary on Apple. The last...
May 1, 2016

Doing the right thing.

Today, I was reading one of the many RSS feeds to which I subscribe. I...
November 22, 2015

Application Development – R…Evolution?

As I was working with the latest release of a software solution (an operating system),...
September 18, 2015


The topics below are those that I have on my list of topics to cover. Some are nearing completion, some are just ideas. Stay tuned!


The Health Insurance Portability and Accountability Act (HIPAA) has, from the onset, brought a good number of challenges to organizations that are required to comply with HIPAA regulations. I’ll dig into some of the nuances with HIPAA, as well as some traps into which companies can easily fall.


Like HIPAA, PCI compliance can easily get ahead of an organization. I’ll explore some of the compliance issues I’ve seen at various organizations, and provide a common sense view of what organizations can do to overcome these. If your business processes credit card transactions, you’ll want to read this!


At some point in time, the majority of businesses need to augment their team with external resources. Consultants are brought in to help move specific objectives forward for a company. This can span from something simple (augment our team’s technology skills) to something more comprehensive (we need to implement an ERP system). We’ll look at the various consulting approaches, and how to best leverage those for an organization’s objectives.


You’ve probably seen it–teams in the same organization that are dependent on each other, but rarely communication. I’ll give insight to the impacts I’ve seen from this “model,” and some recommendations on what can be done to help solve this substantial hidden cost.


Back in the day, the words “development methodologies” would have brought blank stares from most developers working outside of a mainframe environment. Within that mainframe environment, most used a single (albeit somewhat modified by environment) methodology. I’ll explore some methodologies I’ve leveraged, and the pros and cons.


The success and failure of projects can generally be tied back to the way in which they’ve been managed. I’ll explore a few different approaches I’ve seen, inclusive of their outcomes. I’ll provide some insight on what I’ve seen work best across multiple projects, and organizations.