Skip to main content

Change Management: Boon or Curse?



I will be collecting my thoughts on Change Management pretty soon. I'll focus on...
  • Change Activists within an organization
  • Devil's advocate vs Relentless inquisitor
  • Inside the box (Inside Out) vs Out of the box (Outside In)
  • Logic (yawn) vs Learning (yay)
  • Problem Solving Ability vs Solution Identification
Change is just not welcome. Not by the ones who promote is as a boon and talk at great lengths about it. Not by the ones who have to get their jobs done. Face it. What makes it only worse is to put the same people who had been using the adhoc ideologies to run the business (whatever value that it had OR was perceived by the client) and are now the guardians of the newly implemented way of working. So what did not change? Yes you got it! PERCEPTION! More later...

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op