Archive for June, 2006

Lack of posts

Sorry, I have tons to write about. But not when I’m on dial-up.

Streamyx, the so-called broadband provider in Malaysia, is down in my area. It’s been 5 days now. Various excuses given including upgrading, and technical difficulties, the reasons vary depending on which day you call.

Yeah, they’re bluffing. What can I do? This is what happens when the whole broadband industry is monopolized by one company.

Broadband Malaysia? Dream on, ok?

P/S: I’m on dial-up.

Linux on a Palm

I’m most certainly impressed. I’m not so certain though, that if this project some how takes off, I’d install a copy on my Palm. As archaic as the OS is, it’s UI is pretty much flawless. Having stuck to just using my E61 for pretty much everything from PIM, web browsing and emails the past few weeks, I’m appreciating the sheer simplicity of the Palm UI more and more. I’m not so sure I want anything else.

But having Linux running on it definitely has it’s benefits. Driver support for hardware for one thing. Community support is another - tens (maybe hundreds?) of enthusiast geeks will most certainly churn out more quality work than a bunch of over-worked programmers ;). Then there’s also other benefits of a modern OS - multitasking, support for real files, etc.

Read more -Linux on the LifeDrive. Can someone go put Linux on a WM5 device?

Management issues in the IT

It seems that managing knowledge workers ain’t that easy. Problem is, managers still don’t see this. They think it’s a stroll in the park when it’s more like jungle tracking in the Amazon. Just after the post about pitfalls of technical leadership, an article titled How NOT to lead geeks came to my attention. Again, issues highlighted really do connect with me, and based on discussions among friends, they are a common problem. Of course, that’s not to say bad management is alien in other fields, but I think geeks are less forgiving when it comes to incompetency (sorry if I ruffle your feathers). Working with computers where precision, speed and correctness is the rule, we just can’t stand bad managers :).

Really.
On a more general note, I just remembered a Harvard Business school article I got from their newsletter, aptly titled Why Your Employees Are Losing Motivation that I’d love to share right now. It does hit all the nails on a more general note, listing out 3 key reasons (yes, just 3!) why people work. I’ll just quote the article:

  • Equity: To be respected and to be treated fairly in areas such as pay, benefits, and job security.
  • Achievement: To be proud of one’s job, accomplishments, and employer.
  • Camaraderie: To have good, productive relationships with fellow employees.

It goes on to elaborate that all 3 must be met. For example,

  • having only good relationship won’t keep your stomach full
  • getting well paid but doing work that does not give a sense of achievement guarantees high turnover
  • challenging work, excellent colleagues but no respect is also a sure way to lose an emplyee

It’s because managers fail to provide or underestimate the importance of these 3 factors that employees lose the drive to work, even quit. I’ll let you read the whole article for more info. Ironic how these problems looks so simple, yet the common manager hasn’t a clue about why the underlings leave.

How To Files from S60 Phone to PC via Bluetooth

This tip assumes a native WindowsXP BT stack is used, as opposed a 3rd party driver e.g., IVT Bluesoleil. What’s important is to make sure to enable BT discovery and then put the computer in a file-receive mode before initiating the transfer from the phone.

Read all about it here - Sending Files from S60 Phone to PC via Bluetooth

How to Take Great Group Photos

This digital photography site has posted tons of info regarding digital photography. This time around, the tip is centered towards taking group photos. I love the site because the advice given are usually very practical and newbie friendly - because not everyone understands digital photography lingo.

Read it here - How to Take Great Group Photos

Technical leadership pitfalls

Here’s a cheat list from InfoQ, which quotes an article from Hacknot, which was passed to me by a colleague a few days back. I’ve been meaning to post it here but it slipped my mind until I read it again today. It details an eerie similarity to real world scenarios I’ve come across.

  • Mistake #0: Assuming the team serves you
  • Mistake #1: Isolating yourself from the team
  • Mistake #2: Employing hokey motivation techniques
  • Mistake #3: Not providing technical direction and context
  • Mistake #4: Fulfilling your own needs via the team
  • Mistake #5: Focusing on your individual contribution
  • Mistake #6: Trying to be technically omniscient
  • Mistake #7: Failing to delegate effectively
  • Mistake #8: Being ignorant of your own shortcomings
  • Mistake #9: Failing to represent the best interests of your team
  • Mistake #10: Failing to anticipate
  • Mistake #11: Repeat mistakes others have already made
  • Mistake #12: Using the project to pursue your own technical interests
  • Mistake #13: Not maintaining technical involvement
  • Mistake #14: Playing the game rather than focusing on the target
  • Mistake #15: Avoiding conflict
  • Mistake #16: Putting the project before the people
  • Mistake #17: Expecting everyone to think and act like you
  • Mistake #18: Failing to demonstrate compassion

If you’re even remotely related to technical leadership, please, do yourself and your team a favour by reading through the article. Be warned, it’s long so make sure you have about 20 minutes to burn (read: do not start if you have work)