I couldn’t do it. Ctrl, F4 and W individually get to the onkeydown handler just fine. With ctrl+F4 and ctrl+W, the ctrl key is caught, but Google Chrome eats up the F4 and W and closes the tab.
It makes sense, I think. I wouldn’t want an “antivirus” or spam website preventing me from dismissing the tab with prejudice!
These components can run in MTAs and STAs. If instantiated in an MTA, the object will be an MTA component. Likewise if instantiated in an STA, it will be considered an STA component.
Mention NetBIOS in a room full of system admins, and a cold draft seems to spread through the room. It’s as they could sense Darth Vader nearby.
I finally decided to get to the bottom of this discomfort. It turns out that NetBIOS’ null sessions have much to answer for. What follows is a compendium of links that explains the problem.
How to secure a box with NetBIOS enabled: Restrict anonymous enumeration
The NetBIOS component’s security holes have been patched by Microsoft. But the default installation of NetBIOS leaves much to be secured. By default, it’s possible to connect anonymously to the IPC$ share on a machine. Once connected, the NetBIOS Session Service can be queried for a complete list of users. The harddrives are shared by default for administrative purposes as c$ and d$. These shares are hidden, but can be accessed by someone with valid credentials. Armed with a knowledge of all usernames on the machine, it’s possible to guess the password of some user with admin rights by a brute force attack on one of the harddrive shares, and after authenticating successfully proceed to wreak havoc.
Some of the links above describe steps to secure NetBIOS. But most recommend that if it is not needed, it’s best to disable it.
I purchased this phone just a few days ago, so what follows are some young impressions that may change or mature with time. I have not taken the trouble to separate my comments on the android platform from those on the design of the phone.
What works:
What needs improvement:
Not so good, but not too bad:
Update on August 24, 2010: What’s changed since I posted this
Thin slicing and starting with the simplest thing that could possibly work is motivating. I do not have to wait too long for gratification, since I am frequently witnessing useful code getting out the door.
Lack of gratification lends a lack lustre feel to a coding stint.
In a recent incident, I felt that too much time had passed since the last compile. It was taking too much time to make a new test pass. The lack lustre experience kept nagging me, until I realized later that test was too long. The entire test lay insidiously on a single line, but tested too much for me to thin slice the code to make it pass quickly.
In this case, I believe I should have built a thin test, passed it, and iteratively expanded it. It wasn’t a large test in itself. Implementing the code behind it was just more than I could handle at the time, late at night, tired and enthusiastic. Slicing the test would have made it easier to think about the implementation. The exercise would probably have taken less time, and been more gratifying. I see that now.
Recently I’ve been chewing on a small pieces of code, doing tdd just for practice, trying to see what works, what keeps it going. Here are some points that have helped so far.
These two help me take smaller steps. Smaller steps help me watch my design unfold in slower motion, making it easier to spot problems, among other things.
