Today Apple is supposed to make a big announcement. I don’t know yet what that will be but many people think it’s related to a Tablet PC. Apple’s success in the iPhone and App Store business has reminded me of one of the web’s biggest mistakes and we seem on track to repeat it. I’m stunned because it really hasn’t been that long. How can we be doing it again so soon?
It’s that time where people make their predictions. I’ll chip in my 2 cents worth regarding technology changes in the future. The last decade, I think, can be described as the decade of the web. The next, in a word, will be mobile.
Well, blame it on Twitter. I’ve been blogging much less lately (I’m @newz2000 on twitter and identi.ca). I’m going to resume writing soon and have some great material to start out with.
OK, here’s the problem… you want to test a website by sending custom headers, but the website uses https. Normally you’d just telnet to port 80 like so:
telnet www.somesite 80
GET /index.html HTTP/1.1
(Note you need to press enter twice at the end)
This would be a valid HTTP GET request and you’d see the server’s response headers and response data. But with an SSL website this won’t work at all. What do you do?
I really get irritated with passwords. I want to avoid entering them when possible. However, I want to keep security high.
Using SSH keys, you don’t need to enter passwords to log into systems. However, if you’re wise, you’ve encrypted your SSH key to keep it and your systems secure. So what’s the benefit of removing your password if you just have enter a password to decrypt your key?
If you use ssh-agent and ssh-add you can enter your password one time to decrypt your key and then it will help you log in each time you use SSH. Big benefit.
Jakob’s recent Alertbox discussing the stability of web usability principles ends with a comment how people naively state that web usability concepts are obvious. (yes, that is a major paraphrase, sorry JN)
You may look at my website and say that I need to apply my own principles, and you’d be right. You may look at my work website and say the same, and you’d be right again. However, this only re-enforces Jakob’s point – You can’t just look at your website and say, “this is easy” or “this is hard.”
“If the software isn’t perfect, someone might die.” A paraphrased quote from this excellent article from back in ’96 about how the space shuttle software team has to write 100% bug free code.
Wow, I won again! RedHat Magazine had a contest asking users their favorite tool for managing server performance. My favorite tool is one that I wrote myself. It watches the server load and a few other things that you can configure. It runs automatically every five minutes, and if the values rise above a certain acceptable limit it sends a message to my pager.
I like to code. I like to eat. therefore, I code for money. The people who pay me, sell my code. Because they also need to eat, they sell my code for more than they pay me (they profit). At least, this is how it works in theory. I don’t code for food, because sometimes I like to do things other than eat.