Karora Komics - part 1
Karora Komics
Just stumbled onto these on my old hard drive, thought it might be fun to post, just to show you how whacky Karora's R&D team can be. The next few comic strips are an actual debugging session that took place on 27-11-2002, with comic characters bbg as Gav in the Toronto lab, and IRCMonkey as yours truly, working remotely from home. We kind of took eXtreme Programming to the extreme.
Thinking of the tsunami victims
Well, no matter where you are in the world, unless you've been hibernating off some remote mountains or islands in the last 4 days, you must have heard about the latest tsunami disaster that hit South East Asia last Sunday, causing untold devastation.
It is at times like this that I feel so very fortunate to be living in such peaceful and (relatively) trouble-free country as Canada. I feel so undeservedly blessed in this life, as there are certainly thousands of people who are much more deserving than me. And I thank God for granting me these blessings. At times like this, for a brief moment, it makes me want to give up everything and devote my life to helping the less fortunate. Sadly, the selfish side of me is still winning the struggle against that thought.
But for now, a small contribution, I can do. The Canadian Red Cross has set up a page, South East Asia Tidal wave and Earthquake, that accepts online donation. In the spirit of the season, please help what you can. Be sure to select South East Asia Tidal wave and Earthquake as the Fund Designation if you really want your donation to go to the tsunami relief efforts.
God bless.
It is at times like this that I feel so very fortunate to be living in such peaceful and (relatively) trouble-free country as Canada. I feel so undeservedly blessed in this life, as there are certainly thousands of people who are much more deserving than me. And I thank God for granting me these blessings. At times like this, for a brief moment, it makes me want to give up everything and devote my life to helping the less fortunate. Sadly, the selfish side of me is still winning the struggle against that thought.
But for now, a small contribution, I can do. The Canadian Red Cross has set up a page, South East Asia Tidal wave and Earthquake, that accepts online donation. In the spirit of the season, please help what you can. Be sure to select South East Asia Tidal wave and Earthquake as the Fund Designation if you really want your donation to go to the tsunami relief efforts.
God bless.
Not Designed for Dummies
With the holidays, and being away from home and the office (and still able to do work), I've been using my old Dell Inspiron laptop more extensively than I usually do, and I've come to notice how crappy the keyboard design is on this thing.
The Ctrl key is too hard. I'd do a Ctrl-S to save my code changes in the editor, and sometimes it would simply echo an 's' in the middle of my code (the Ctrl didn't take). I guess I didn't press hard enough.
Bad design point #1: the product encourages people to do the wrong things (pressing hard on the keyboard in the long run is a health hazard, or so I've heard).
The TouchPad mouse is another thing. It's positioned right below where your thumbs would be located if your hands were fully positioned on the keyboard. I'd be typing along and then all of a sudden, the cursor would jump half a page down, and I find myself hypertyping in the middle of another block of code. What happened? Oh, I guess one of my thumbs must have touched the TouchPad by accident, triggering a mouse click that puts the cursor somewhere else.
Bad design point #2: the product encourages people to do the wrong thing without even realizing they were doing it.
May be because it's just an ancient Dell, or may be it's my seating posture. But this experience reminds me of how critically important usability is to any product, computer related or otherwise. To be usable, the user interface needs to be intuitive. If I build a product that does something when my users expect it to do something else, then this is a very bad thing. It's most likely qualified as carnal rule #1 of usability design, because if this happens too often, eventually the annoyance factor kicks in and my users will be cursing me for using my product.
Upon reflection, this is more of a wake-up call for myself than anything, because I at times make this very mistake in designing software user interface. I guess I need to have that "Design for Dummies" logo engrained in my head. But then again, if you're building radically new things out-of-the-box that have never been done before, and especially if you don't have usability experts on staff at your disposal, then the only true test of usability would be to put out beta releases, and get as many users as possible to use it, then make the necessary adjustments based on their feedbacks.
The Ctrl key is too hard. I'd do a Ctrl-S to save my code changes in the editor, and sometimes it would simply echo an 's' in the middle of my code (the Ctrl didn't take). I guess I didn't press hard enough.
Bad design point #1: the product encourages people to do the wrong things (pressing hard on the keyboard in the long run is a health hazard, or so I've heard).
The TouchPad mouse is another thing. It's positioned right below where your thumbs would be located if your hands were fully positioned on the keyboard. I'd be typing along and then all of a sudden, the cursor would jump half a page down, and I find myself hypertyping in the middle of another block of code. What happened? Oh, I guess one of my thumbs must have touched the TouchPad by accident, triggering a mouse click that puts the cursor somewhere else.
Bad design point #2: the product encourages people to do the wrong thing without even realizing they were doing it.
May be because it's just an ancient Dell, or may be it's my seating posture. But this experience reminds me of how critically important usability is to any product, computer related or otherwise. To be usable, the user interface needs to be intuitive. If I build a product that does something when my users expect it to do something else, then this is a very bad thing. It's most likely qualified as carnal rule #1 of usability design, because if this happens too often, eventually the annoyance factor kicks in and my users will be cursing me for using my product.
Upon reflection, this is more of a wake-up call for myself than anything, because I at times make this very mistake in designing software user interface. I guess I need to have that "Design for Dummies" logo engrained in my head. But then again, if you're building radically new things out-of-the-box that have never been done before, and especially if you don't have usability experts on staff at your disposal, then the only true test of usability would be to put out beta releases, and get as many users as possible to use it, then make the necessary adjustments based on their feedbacks.
PuTTY security holes in version < 0.56
A little bit of old news. I just saw this on the PuTTY site:
2004-10-26 ANOTHER SECURITY HOLE, fixed in PuTTY 0.56
PuTTY 0.56, released today, fixes a serious security hole which can allow a server to execute code of its choice on a PuTTY client connecting to it. In SSH2, the attack can be performed before host key verification, meaning that even if you trust the server you think you are connecting to, a different machine could be impersonating it and could launch the attack before you could tell the difference. We recommend everybody upgrade to 0.56 as soon as possible.
That's two really bad holes in three months. I'd like to apologise to all our users for the inconvenience.
This Day in History
On this date:
In 1783, George Washington resigned as commander-in-chief of the Army and retired to his home at Mount Vernon, Va.
In 1893, the Engelbert Humperdinck opera "Haensel und Gretel" was first performed, in Weimar, Germany.
In 1928, the National Broadcasting Company set up a permanent, coast-to-coast network.
In 1941, during World War II, American forces on Wake Island surrendered to the Japanese.
In 1948, former Japanese premier Hideki Tojo and six other Japanese war leaders were executed in Tokyo.
In 1968, 82 crew members of the U.S. intelligence ship "Pueblo" were released by North Korea (news - web sites), 11 months after they had been captured.
In 1972, Thanh Hai Tran was born.
In 1980, a state funeral was held in Moscow for former Premier Alexei N. Kosygin, who had died Dec. 18 at age 76.
In 1986, the experimental airplane "Voyager," piloted by Dick Rutan and Jeana Yeager, completed the first non-stop, non-refueled, round-the-world flight as it landed safely at Edwards Air Force Base in California.
In 1987, Lynette "Squeaky" Fromme, serving a life sentence for the attempted assassination of President Ford in 1975, escaped from the Alderson Federal Prison for Women in West Virginia. (She was recaptured two days later.)
In 1997, a jury in Denver convicted Terry Nichols of involuntary manslaughter and conspiracy for his role in the Oklahoma City bombing, declining to find him guilty of murder.
[Courtesy of Yahoo.com]
In 1783, George Washington resigned as commander-in-chief of the Army and retired to his home at Mount Vernon, Va.
In 1893, the Engelbert Humperdinck opera "Haensel und Gretel" was first performed, in Weimar, Germany.
In 1928, the National Broadcasting Company set up a permanent, coast-to-coast network.
In 1941, during World War II, American forces on Wake Island surrendered to the Japanese.
In 1948, former Japanese premier Hideki Tojo and six other Japanese war leaders were executed in Tokyo.
In 1968, 82 crew members of the U.S. intelligence ship "Pueblo" were released by North Korea (news - web sites), 11 months after they had been captured.
In 1972, Thanh Hai Tran was born.
In 1980, a state funeral was held in Moscow for former Premier Alexei N. Kosygin, who had died Dec. 18 at age 76.
In 1986, the experimental airplane "Voyager," piloted by Dick Rutan and Jeana Yeager, completed the first non-stop, non-refueled, round-the-world flight as it landed safely at Edwards Air Force Base in California.
In 1987, Lynette "Squeaky" Fromme, serving a life sentence for the attempted assassination of President Ford in 1975, escaped from the Alderson Federal Prison for Women in West Virginia. (She was recaptured two days later.)
In 1997, a jury in Denver convicted Terry Nichols of involuntary manslaughter and conspiracy for his role in the Oklahoma City bombing, declining to find him guilty of murder.
[Courtesy of Yahoo.com]
Karora's AppConnector finally ranked #1 by Google!
Up until recently, when you google for AppConnector, the first hit you'd get is one of our reseller's web site instead of Karora's web site. It's embarrassing, considering that we own the trademark for the name. Well, no longer. As of today, we're first in the hitlist. Woohoo!!!
Next mission: getting us to come up #1 for Desktop Application Integration. :-)
Next mission: getting us to come up #1 for Desktop Application Integration. :-)
Oh pardon me, I farted...
This, hot off the Wire:
Wow! That's pretty revolutionary...if it can work, that is.
What's next: smellevision? Not as farfetched as you might think now, is it? Scary!
A Japanese firm pioneers a system to share fragrances over the internet.
...
Users attach a device to their laptops that resembles a crystal ball with a nozzle. The device receives aroma data from the central server and exudes fumes from the nozzle in accordance with that reading.
Wow! That's pretty revolutionary...if it can work, that is.
What's next: smellevision? Not as farfetched as you might think now, is it? Scary!
Developer versus Programmer
What's the difference between a (Software) Developer and a (Computer) Programmer? Joe Spolsky's had a good post this week on his Joel on Software blog discussing at length by comparing the difference between two Hebrew words...which are all Greek to me until he started explaining it in English. Joel also pointed to another good blog entry by Eric Sink, entitled Small ISVs: You need Developers, not Programmers, which makes a similar distinction. In effect, from a responsibilities perspective, they both say that a programmer is someone who does what's sufficient, no more, no less. And a developer is one who does what's necessary.
Although I appreciate and understand the need to make the distinction, I think the distinction is borne from a human resource or management perspective, not one of a technical perspective. The title Software Developer only started appearing in employment ads in recent years. Before that, back in the days where computer programmers are still a rare species, all the relevant titles you would see in a job posting are Programmer/Analyst, Application Programmer, System Programmer, or simply Programmer. And it is not unplausible to see the following responsibilities mentioned in the job description: responsible for writing functional specification, implementing programming logic as per specs, writing test cases to be executed by testers, perform bug fixes, may involve writing of user documentation, etc... My point is that back then a programmer was not necessarily someone who just does the coding, and good programmers didn't just do what they were told.
Back then when I went to my high school guidance counsellor to try to chart my career path, the brochure only had about a couple of career options for computers: Computer Programmer (meant for those interested in software) and Computer Engineer (meant for those interested in hardware).
Now, with the explosion of jobs created by the computer industry in the past few decades, suddenly there's a need to differentiate between a Developer and a Programmer. That's unfortunate, because to me they both mean the same thing. When I explain what I do to someone who's computer challenged, I'd say I'm a computer programmer, eventhough my job title says "Software Developer". They know, albeit acutely, what "computers" are, and I can easily explain away what "programmer" means. Instead, with a fancy term like "Software Developer", I'd have to explain the difference between software and hardware--a much more difficult thing to explain to someone with zero knowledge of computers.
Although I appreciate and understand the need to make the distinction, I think the distinction is borne from a human resource or management perspective, not one of a technical perspective. The title Software Developer only started appearing in employment ads in recent years. Before that, back in the days where computer programmers are still a rare species, all the relevant titles you would see in a job posting are Programmer/Analyst, Application Programmer, System Programmer, or simply Programmer. And it is not unplausible to see the following responsibilities mentioned in the job description: responsible for writing functional specification, implementing programming logic as per specs, writing test cases to be executed by testers, perform bug fixes, may involve writing of user documentation, etc... My point is that back then a programmer was not necessarily someone who just does the coding, and good programmers didn't just do what they were told.
Back then when I went to my high school guidance counsellor to try to chart my career path, the brochure only had about a couple of career options for computers: Computer Programmer (meant for those interested in software) and Computer Engineer (meant for those interested in hardware).
Now, with the explosion of jobs created by the computer industry in the past few decades, suddenly there's a need to differentiate between a Developer and a Programmer. That's unfortunate, because to me they both mean the same thing. When I explain what I do to someone who's computer challenged, I'd say I'm a computer programmer, eventhough my job title says "Software Developer". They know, albeit acutely, what "computers" are, and I can easily explain away what "programmer" means. Instead, with a fancy term like "Software Developer", I'd have to explain the difference between software and hardware--a much more difficult thing to explain to someone with zero knowledge of computers.
The Evolution of a Programmer
Link: The Evolution of a Programmer
This article makes so much sense it's actually funny. I was laughing out loud towards the end of it. Here's my interpretation of it, for those who may be programmatically challenged:
High School/Jr.High
You learn the basic and the simple. BASIC is the first programming language you learn in high school.
First year in College
You learn to add standards and structures to things. Pascal is the language used in first year college classes to teach structured programming.
Senior year in College
You learn to do things the "smart" way. Lisp is the language used in senior year Artificial Intelligence (AI) courses.
New professional
Reality kicks in. You find out what you've been learning in college has nothing to do with what you'll be doing for a living. You're inexperienced and don't necessarily do things in the most efficient ways. C is the programming language used by just about every software development organization in the world, if not in full then at least in part.
Seasoned professional
With some experience, you think you now know alot of tricks. You think you can do things better than anyone else. Consequently, you always like to re-invent the wheel, to build better wheels. You know too much for your own good.
C++ is an object-oriented language preferred by organizations over C because it is easier to maintain. In this code snippet, the programmer is overriding virtually all the standard operators and functions provided by the language with his/her own implementation.
Master Programmer
You've mastered the art doing things in the most complicated way possible.
Hackers
You learn to tinker with things beyond your comprehension.
I dropped the various levels of hackers from the list because these aren't really the next steps in the evolution per se. Most programmers tend to pick up their hacking experience in parallel with their programming experience.
New Manager
Wisdom kicks in and you finally realize what you've learned in school actually makes sense. You've become humbled and now wants to keep things as basic and simple as possible.
Middle Manager
You learn that getting more things done means delegating as much as possible to other people.
Senior Manager
You learn to delegate with less effort. Or in programmer lingo: you've optimized your delegation routine.
Chief Executive
You've lost it! You've gone senile. Time to turn in the badge in exchange for that retirement pen.
Call me naive, but it seems to me that life as a programmmer is very much a parody of life in general.
This article makes so much sense it's actually funny. I was laughing out loud towards the end of it. Here's my interpretation of it, for those who may be programmatically challenged:
High School/Jr.High
You learn the basic and the simple. BASIC is the first programming language you learn in high school.
First year in College
You learn to add standards and structures to things. Pascal is the language used in first year college classes to teach structured programming.
Senior year in College
You learn to do things the "smart" way. Lisp is the language used in senior year Artificial Intelligence (AI) courses.
New professional
Reality kicks in. You find out what you've been learning in college has nothing to do with what you'll be doing for a living. You're inexperienced and don't necessarily do things in the most efficient ways. C is the programming language used by just about every software development organization in the world, if not in full then at least in part.
Seasoned professional
With some experience, you think you now know alot of tricks. You think you can do things better than anyone else. Consequently, you always like to re-invent the wheel, to build better wheels. You know too much for your own good.
C++ is an object-oriented language preferred by organizations over C because it is easier to maintain. In this code snippet, the programmer is overriding virtually all the standard operators and functions provided by the language with his/her own implementation.
Master Programmer
You've mastered the art doing things in the most complicated way possible.
Hackers
You learn to tinker with things beyond your comprehension.
I dropped the various levels of hackers from the list because these aren't really the next steps in the evolution per se. Most programmers tend to pick up their hacking experience in parallel with their programming experience.
New Manager
Wisdom kicks in and you finally realize what you've learned in school actually makes sense. You've become humbled and now wants to keep things as basic and simple as possible.
Middle Manager
You learn that getting more things done means delegating as much as possible to other people.
Senior Manager
You learn to delegate with less effort. Or in programmer lingo: you've optimized your delegation routine.
Chief Executive
You've lost it! You've gone senile. Time to turn in the badge in exchange for that retirement pen.
Call me naive, but it seems to me that life as a programmmer is very much a parody of life in general.
Robosapien
Picked up this hot tip from Steve about Robosapien. Looks like it might be a cool gift for my nephew. The trouble is: I checked virtually all the online shops and they're all sold out! Thanks for the tip, Steve...not! Just wish you had posted it a month or two earlier. Oh well. There's always next year.