Skip to main content

MTBF catches up to development.

Intent on finishing the implementation of the new permission token feature into the framework code I was fully engaged yesterday in getting it done hopefully by the middle of this week. That is until a strange occurrence yesterday. As I was at the computer the mouse became unresponsive, I have a periodically flaky KVM switch that some times does this so I switched to one of my other development pc's to see if the KVM was frozen, it was not. I switched back to the main development server and after a few silent expletives , hit the power button as I had no choice. The computer immediaetly began a reboot but at the point of reaching the BIOS screen simply went dead. I was curious but already had a feeling that my computers power supply was in trouble. I rebooted again after first unplugging the power cable from the pc for a few seconds, the machine indicated it was getting power by blinking the power and hdd light, but the hdd light was solid and the screen didn't receive a signal...uh oh I thought as I reached around to turn off the machine again. This time I noticed the faint smell of burnt circuit board that is a tell tale sign of failing or failed components. After another 10 minutes waiting with the power cable unplugged I came back, plugged it in and pressed power. The computer made a dull beeping sound and the power led blinked for a second and then went quiet. I did this 4 more times with the same result, it appears I experienced the slow death of my power supply. The main development server was rebuilt (mobo + memory + proc) around 2002, a year later the older PS that hadn't been replaced during the 2002 rebuild gave up the ghost just about at the time it reached the standard MTBF (mean time before failure) for power supplies of 5 years. While noticing the behavior I conjectured the Power supply had again reached MTBF and had finally given in, when I upgrade parts in my machines I tend to put a date on them to signal the age of the component. The powersupply was marked with 10-15-2003 as the installation date , which is just under 5 years ago. I turned off the pc, and switched to my other machine to quickly place an order for a new Power Supply from, hopefully the diagnosis is on the mark and after a fast 15 minute replacement I'll be back up and ready to finish the implementation. Murphy's law strikes again, but not so big a deal I'll enjoy a 3 day mini-cation while I wait for delivery of the PS. ;)


Popular posts from this blog

Highly targeted Cpg vaccine immunotherapy for a range of cancer


This will surely go down as a seminal advance in cancer therapy. It reads like magic:

So this new approach looks for the specific proteins that are associated with a given tumors resistance to attack by the body's T cells, it then adjusts those T cells to be hyper sensitive to the specific oncogenic proteins targeted. These cells become essentially The Terminator​ T cells in the specific tumor AND have the multiplied effect of traveling along the immune pathway of spreading that the cancer many have metastasized. This is huge squared because it means you can essentially use targeting one tumor to identify and eliminate distal tumors that you many not even realize exist.

This allows the therapy for treating cancer to, for the first time; end the "wack a mole" problem that has frustrated traditional shot gun methods of treatment involving radiation and chemotherapy ...which by their nature unfortunately damage parts of the body that are not cancer laden but …

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way.

The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created.

Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write.

Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is devo…

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache
The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform certain actions. Also, the…